LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
From:
Hans Aberg <[log in to unmask]>
Date:
Mon, 11 Jun 2001 15:07:44 +0200
In-Reply-To:
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments:
text/plain (21 lines)
At 23:27 +0200 2001/06/10, Marcel Oliver wrote:
>I don't think this means we have to support arbitrary encodings of
>auxiliary files.  Editing such files is, after all, undocumented
>practice, and using an UTF8 editor will (rather elegantly) provide
>full access to these files.  Do we need more?

As you say, it is the formats that editors can handle that is controlling
the formats that one wants to be able to have in the files.

But what says that UTF8 is the preferred format of editors; what says that
they will not simply use Unicode? -- I do not know the editor market, but I
think one should check if UTF8 will be a format that every editor will be
able to handle, before excluding all other formats.

Also, if the TeX successor has an input/output encoding mechanism which is
external to the TeX engine, then it can easily handle different encodings
in any type of text file. The question becomes fairly redundant as far as
LaTeX and TeX programming is concerned.

  Hans Aberg

ATOM RSS1 RSS2