## LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

 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 >>]

 Subject: Re: LaTeX's internal char prepresentation (UTF8 or Unicode?) From: Hans Aberg <[log in to unmask]> Reply To: Mailing list for the LaTeX3 project <[log in to unmask]> Date: Sat, 17 Feb 2001 20:27:17 +0100 Content-Type: text/plain Parts/Attachments: text/plain (38 lines)
At 12:54 -0500 2001/02/17, Barbara Beeton wrote:
>while this would obviously work for text in natural languages,
>unicode will never contain all the possible "embellished" letters
>and symbols used in math.  (and this may include instances with two
>or even more diacritics on a single letter or symbol.)  this set,
>while not infinite, is much too large to want to address even using
>the unicode private area.  but for latex (or any successor) to be
>useful for the particular content for which tex was first developed,
>this has to be taken into account.

I do not think about math in particular, but the other combining symbols:

Whereas Unicode in some case have single symbols for math combined
characters, such as the negation of <=> may have its own symbol, in other
cases there might not, so that one still has to write \not\myrelation. (I
do not know if Unicode has changed lately and now has a lot of math
combining characters.)

Actually, even though one can spend some interesting thinking on how to do
with Unicode combining characters if they happen to math, I do not think
that the final solution will make much difference, because the
mathematicians will find out how to handle it.

(Or you will have to explain better what you have in your mind.)

-- I can add that a simple method to allow different input encodings when
reading from a file <filename> could be to have it to be treated by default
as say Unicode unless there is an ASCII file with say name <filename>.e
with information about the encoding. (One could also allow change the
default encoding for different files by means of startup arguments.) This
file <filename>.e could have very simple information, or as complex as you
bother to write the preprocessor, if you say want mixed encodings or be
able to switch between encodings in the very same file. -- In effect, one
is creating a mini-language for reading encodings in a way that TeX does
not have to bother about it.

Hans Aberg