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:

Proportional Font

LISTSERV Archives

LISTSERV Archives

LATEX-L Home

LATEX-L Home

LATEX-L  February 2001

LATEX-L February 2001

Subject:

Re: Multilingual Encodings Summary

From:

Frank Mittelbach <[log in to unmask]>

Reply-To:

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

Date:

Thu, 15 Feb 2001 08:44:11 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (118 lines)

Donald,

 > >  > - Hyphenation patterns are specified in terms of the output encoding.
 > >  >   This means that every character appearing in the hyphenation rules
 > >  >   must have a physical slot in the selected font.
 > >
 > > only in the internal storage format for patterns used within TeX. On the
 > > abstract level this is not at all true even though the source format of
 > > existing patterns tend to be written in this form as well.
 >
 > Frank also made an earlier comment in this regard, which, while true,
 > is of marginal relevance to the discussion of multi-lingual/-encoded
 > documents.

Marcel's summary was trying to put forward technical points to be able to
weight them against each other. I was simply trying to put them technicaly
right where i considered them wrong. but i disagree with you when you say that
it has nothing to do with it.

 > Yes, it is nice if hyphenation pattern input files use symbolic
 > representaions of characters (\ss) rather than hex code values
 > so they can be used for different font encodings.  But the font
 > encoding must be selected when the format is generated!  This
 > doesn't help the user who wants to use various font encodings,
 > and it certainly does not facilitate multi-encoded documents.

you are right that the hyphenation patterns have to be selected at format
generation time so that you are unable to actually extend that set for a
single document. however, with "these days" TeX implementations  there is
typically enough room to actually store mutiple patterns and that means that
for typical usages at a site you can combine all the patterns needed (for
several languages and several font encodings)

don't forget that in many cases the largest pattern set can in fact serve for
several font encodings if they (for the character set of the corresponding
language) actually have the same slot positions  in the font encoding.


 > For hyphenation purposes, multiple encodings must be treated as
 > multiple languages.

technically you are right but you are in fact pointing with your statement at
the basic error Don made with TeX3x: calling something \newlanguage and
\language when in fact it should have been called something very different.
(eg pointer-to-hyphenation-patterns-related-to-some-output-encoding)
a lot of the problems result from using the TeXnical) term.

so no: not multiple encodings have to be treated as multiple languages but
within one language you need to store for each font encoding used which of the
pointer-to-hyphenation-patterns-related-to-some-output-encoding's you have to
apply when typesetting in this encoding.

and given that you (these days) can store a suitable number of such
pointer-to-hyphenation-patterns-related-to-some-output-encoding's you can with
a single format typeset multiscript documents for a number of combinations of
scripts. Clearly you have a limit so if you want to be able to typeset in too
many combinations you need a number of formats but thats in practice not a
real issue.

However, to be able to automatically generate those internal
pointer-to-hyphenation-patterns-related-to-some-output-encoding's you need the
hyphenation patterns externally stored in something which is independed of the
output encoding.

 > This again points to the need for babel to
 > specify the desired/required font (encoding) when it selects
 > a language.

yes. if we take the approach outlined with my xnfss code enabling the the
specification and use of multiple encodings per language then such a list
should be attached to each language. you would then associate with each such
encoding per language a suitable
pointer-to-hyphenation-patterns-related-to-some-output-encoding (in a number
of cases it could be the same one, eg OT1 and T1 for German would share the
same) and if you don't have an appropriate
pointer-to-hyphenation-patterns-related-to-some-output-encoding you could
select the "no-hypenation" one (or raise an error and ask for a different
format)

 >
 > >  >   However, logically
 > >  >   hyphenation should not depend on output encoding, and one should be
 > >  >   able to mix fonts with different output encodings without losing
 > >  >   correct hyphenation.
 > >
 > > yes, and it is possible without technical problems (in theory)
 >
 > Possible in TeX as it stands???  Only by loading the patterns
 > resolved for each encoding.

of course, but the resolvement process you be happening abslutely
automatically in the background which why i say possible without technical
problems. and i said "in theory" because that requires hyphenation patterns
externally stored in a way that i can (for any font encoding) generate from
them the appropriate internal
pointer-to-hyphenation-patterns-related-to-some-output-encoding form without
problems.

 > Or does "in theory" really mean
 > what it says -- not in practice.

no

 >
 > >  > - It is rather hard to make a new font available under LaTeX.
 > >  >   Essentially one must create a virtual font which has all the
 > >  >   character slots in the places where hyphenation expects them to be.
 > >
 > > wrong.
 >
 > Wrong...I guess.   Maybe Frank runs LaTeX on initex and has patched
 > fontenc.sty to load patterns for whatever font encoding is requested.

unfortunately that isn't any longer possible with TeX as the hyphenation tree
is compacted and doesn't allow addition after the first use (ie after a
paragraph started.

frank

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