LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Frank Mittelbach <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Wed, 31 Jan 2001 22:36:06 +0100
text/plain (31 lines)
 > http://www.Uni-Mainz.DE/cgi-bin/ltxbugs2html?pr=babel/3046

Johannes talkes about the difficulties in providing this, but is it really
something one wants?

 - except when using mule (or emacs) one doesn't (automatically) change input
   encodings when
   changing a language in the middle of the document.

 - beside, even if, for the same language many different input encodings would
   be in use so you can't even pick a default without making a lot of people
   unhappy. you can write german using cp437de or latin1 or ansinew or
   ... depending the OS used or the keyboard or ...

 - same is true for font encodings: my question about OT1 T1 showed that
   clearly, some people never use OT1 these days others only (and both writing
   in the same language)

i guess the only way to tie something like this to the language is as an
offering, ie by default nothing is tied to a language but you have a mechanism
to say that all switches to language X result in switching the inputenc to Y
and give the user a chance to specify this in the preamble.

and something similar for font encodings

the problem with current babel is that for some language you have to do
something and so it happens behind the scene but essentially it is not
customiable (yet) and restoring state is not always as one would expect.