MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C09455.E450B780"
In-Reply-To:  <14982.52715.72492.456142@gargle.gargle.HOWL>
References: <v03110701b6a9aae65099@[195.100.226.129]>            <200102091445.JAA00482@plmsc.psu.edu>            <200102091643.RAA23818@mozart.ujf-grenoble.Fr>            <14980.23750.628032.305093@gargle.gargle.HOWL>            <14982.45082.150652.74719@istrati.zdv.uni-mainz.de>            <20010211161537.A14176@salmon.maths.tcd.ie>            <14982.51803.511929.675006@istrati.zdv.uni-mainz.de>            <14982.52715.72492.456142@gargle.gargle.HOWL>
Content-class: urn:content-classes:message
Subject:      Re: LaTeX's internal char prepresentation (UTF8 or Unicode?)
Date: Sun, 11 Feb 2001 18:57:48 +0100
Message-ID:  <14982.53916.93114.268270@istrati.zdv.uni-mainz.de>
From: "Frank Mittelbach" <frank.mittelbach@LATEX-PROJECT.ORG>
Sender: "Mailing list for the LaTeX3 project" <LATEX-L@URZ.UNI-HEIDELBERG.DE>
To: "Multiple recipients of list LATEX-L" <LATEX-L@URZ.UNI-HEIDELBERG.DE>
Reply-To: "Mailing list for the LaTeX3 project" <LATEX-L@URZ.UNI-HEIDELBERG.DE>
Status: R

This is a multi-part message in MIME format.

------_=_NextPart_001_01C09455.E450B780
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Marcel,

 > LaTeX is what most people use.  TeX just "magically gets installed"
 > when they install LaTeX.  People will use whatever LaTeX uses.

first of all you are unfortunately wrong in that respect. a lot of =
people do
not want to see any change especially if they don't see immediate =
benefits for
themselves and if that happens to be the majority ...

the switch to 2e was a very valuable and sad lession in this respect.

anyway this wouldn't or shouldn't mean you can't change but you have to =
be
careful because if you create a dead product that is not very helpful =
either.

example: i would nevery base (at the current moment) anything on
primitives available in eTeX because it would wipe out the majority of =
users
who wouldn't know how to use etex even if available under their nose (ie
within their distribution).

the main reason for not doing so is that it would only be beneficial for =
me as
a programmer and not beneficial for the user (noticable enough)

but more importantly and that is my second point or the point i tried to =
make:
LaTeX should "work" on TeX as a platform. so if i would build the kernel =
in a
way that this is not possible then people would not go with LaTeX not =
for a
long time.

frank

ps but all this has nothing really to do with how the LICR should or =
could
look like (only with a number of restrictions posed onto the methods =
when
implementing it)

------_=_NextPart_001_01C09455.E450B780
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>     Re: LaTeX's internal char prepresentation (UTF8 or =
Unicode?)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Marcel,</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&gt; LaTeX is what most people use.&nbsp; TeX =
just &quot;magically gets installed&quot;</FONT>

<BR><FONT SIZE=3D2>&nbsp;&gt; when they install LaTeX.&nbsp; People will =
use whatever LaTeX uses.</FONT>
</P>

<P><FONT SIZE=3D2>first of all you are unfortunately wrong in that =
respect. a lot of people do</FONT>

<BR><FONT SIZE=3D2>not want to see any change especially if they don't =
see immediate benefits for</FONT>

<BR><FONT SIZE=3D2>themselves and if that happens to be the majority =
...</FONT>
</P>

<P><FONT SIZE=3D2>the switch to 2e was a very valuable and sad lession =
in this respect.</FONT>
</P>

<P><FONT SIZE=3D2>anyway this wouldn't or shouldn't mean you can't =
change but you have to be</FONT>

<BR><FONT SIZE=3D2>careful because if you create a dead product that is =
not very helpful either.</FONT>
</P>

<P><FONT SIZE=3D2>example: i would nevery base (at the current moment) =
anything on</FONT>

<BR><FONT SIZE=3D2>primitives available in eTeX because it would wipe =
out the majority of users</FONT>

<BR><FONT SIZE=3D2>who wouldn't know how to use etex even if available =
under their nose (ie</FONT>

<BR><FONT SIZE=3D2>within their distribution).</FONT>
</P>

<P><FONT SIZE=3D2>the main reason for not doing so is that it would only =
be beneficial for me as</FONT>

<BR><FONT SIZE=3D2>a programmer and not beneficial for the user =
(noticable enough)</FONT>
</P>

<P><FONT SIZE=3D2>but more importantly and that is my second point or =
the point i tried to make:</FONT>

<BR><FONT SIZE=3D2>LaTeX should &quot;work&quot; on TeX as a platform. =
so if i would build the kernel in a</FONT>

<BR><FONT SIZE=3D2>way that this is not possible then people would not =
go with LaTeX not for a</FONT>

<BR><FONT SIZE=3D2>long time.</FONT>
</P>

<P><FONT SIZE=3D2>frank</FONT>
</P>

<P><FONT SIZE=3D2>ps but all this has nothing really to do with how the =
LICR should or could</FONT>

<BR><FONT SIZE=3D2>look like (only with a number of restrictions posed =
onto the methods when</FONT>

<BR><FONT SIZE=3D2>implementing it)</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C09455.E450B780--