LISTSERV mailing list manager LISTSERV 16.0

Help for LATEX-L Archives


LATEX-L Archives

LATEX-L Archives


LATEX-L@LISTSERV.UNI-HEIDELBERG.DE


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

LATEX-L Home

LATEX-L Home

LATEX-L  June 1997

LATEX-L June 1997

Subject:

Re: [Bug Report] Problem with INPUTENC package and TOC files.

From:

Frank Mittelbach <[log in to unmask]>

Reply-To:

Mailing list for the LaTeX3 project <[log in to unmask]>

Date:

Mon, 16 Jun 1997 23:10:21 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (84 lines)

Werner Lemberg writes:
 > But this is the wrong list for such bug reports. You should address it to
 > [log in to unmask] .

well not really :-) or not in this form anyway. for latex-bugs we ask
for a short but complete test file with full log. that would mean some
constructing.

anyway, i think this is more on the level of concepts and thus could
well be within this list (even if it is boring for one or the other).

as for the use of inputenc a few words on the concepts:

latex has the concept of font-encoding specific commands, which are
those that are defined via \DeclareText<something> usually in font
encoding files, eg T1enc.def

those commands + (more or less :-) the visible portion of ascii forms
what i call "latex's internal representation of glyphs"

it has the caracteristic that it is all represented by 7bit ascii, ie
either something like a, b or command names or combination thereof and
that all of it is invariant to writing out to files and reading in.

so if \foo is an encoding specific command that appears in some \write
to the aux file it will end up as \foo (more exactly it will end up
with one additional space after it but that is not relevant for the
input reading mechanism)


so the model is something like

        inputenc T<something>
hex ?? ---------> internal ------> some glyph slot number
                    | | | T<somethingelse>
                    V A ------------> or some fake construction
                    | |
                    ------
                invarient to .aux etc processing


this model abstracts from the input encoding by allowing the user to
use any input encoding that translates into the internal
representation and it abstracts from the output encoding, ie the font
encoding which means that even if i have fonts which are differently
encoded (but contain the appropriate glyphs) i can the document and if
characters in my fonts are missing i do get proper warning.


now what goes wrong in your first approach is that you have an
inputenc file that doesn't use this model, ie it translates one hex
into some other hex directly, ie \CYRA is most likely something along
\char ... probably just ^^xy

in other words you pass as internal an slot position in a particular
font rather than an abstract object that only at the last stage
(before shipping out to the dvi file basically) gets translated. thus
when coming to process the toc file your font encoding slot is now
interpreted as an input encoding slot and probably ^^8f is not defined
in the inputencoding (it would not make it better only differnt :-)

your second example does work because it mainly uses a passthrough
concept making the font encoding the internal representation. but that
works only if in all places you do have the same font encoding.
therefore reading it back in the font encoding form does not do any
harm, it would do if at that point you have a different font encoding


the inputenc/fontenc model allows you to typeset the toc in a
different font that does have a different font encoding


that is conceptionally the case. things get a bit muddled as babel is
older software and currently restricts some of that potential power
(which is why we do need a new language interface).

really good night
frank

ps Werner, for the reason giving above your advice given (to use \char
... is not correct either) it is true that the particular examplethen
will probably work but only just ---- the internal representation is
not a slot position it should be a encoding specific command of some
sort

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

September 2019
July 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
June 2018
May 2018
April 2018
February 2018
January 2018
December 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
July 2016
April 2016
March 2016
February 2016
January 2016
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
September 2012
August 2012
July 2012
June 2012
May 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
September 2007
August 2007
June 2007
May 2007
March 2007
December 2006
November 2006
October 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
November 2005
October 2005
September 2005
August 2005
May 2005
April 2005
March 2005
November 2004
October 2004
August 2004
July 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
October 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
October 2002
September 2002
August 2002
July 2002
June 2002
March 2002
December 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996

ATOM RSS1 RSS2



LISTSERV.UNI-HEIDELBERG.DE

Universität Heidelberg | Impressum | Datenschutzerklärung

CataList Email List Search Powered by the LISTSERV Email List Manager