> >>>>> "Lars" == Lars Gullik Bj�nnes <[EMAIL PROTECTED]> writes:
>
> Lars> /** We could have a Uni2T1 filter so that we could ditch the
> Lars> inputenc package. This would give use direct access to all
> Lars> characters in the T1 encoding. That would be nice! */
>
> What do you mean? T1 is a font encoding only relevant for output
> font. You cannot write a LaTeX document in T1 encoding as far as I
> know... I do not think there will be any way to avoid using an input
> encoding package (except of course if we output plain 7bit text).
What encoding is used in a raw LaTeX file without any input encoding
packages involved?
What encoding is used when we do use an encoding package?
--
When I am talking about an encoding, I speak in a general sense:
Accented character constructs can be considered one character, just with
a multi-width encoding.
The plan I have in mind in connection with the Encoding class approach
I suggest, is to implement a hierarchy of LaTeX Encodings, matching each
input encoding package there is (and the one without any).
"EncLaTeX" will produce plain 7 bit text, where all accented characters
are done with the LaTeX commands.
"EncLaTeX_ISO8859_1" (or maybe another name) will do the same, except
that the characters that are supported in ISO8859-1 will be spit out as
raw text. EncLaTeX_ISO8859_1 will probably be derived from EncLaTeX.
Maybe even with multi-inheritance to derive from EncLaTeX and EncLatin1
simultaneously. Whatever is easiest.
Similar for other encodings.
Hope you get the idea.
To implement this, I need help with understanding the different encodings
that apply in LaTeX. Is there a reference somewhere?
Greets,
Asger
