MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0946B.D6A62C80"
In-Reply-To:  <Pine.GSO.4.05.10102112159310.25887-100000@obelix.ee.duth.gr>
References: <14982.54413.876872.204368@istrati.zdv.uni-mainz.de>            <Pine.GSO.4.05.10102112159310.25887-100000@obelix.ee.duth.gr>
Content-class: urn:content-classes:message
Subject:      Re: hyphenation morass
Date: Sun, 11 Feb 2001 21:44:59 +0100
Message-ID:  <14982.63947.413495.813392@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_01C0946B.D6A62C80
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Apostolos,

 > Unicode M$Word.) Omega clearly solves this problem the "expected" =
way.
 > And yes there more "exotic" cases where TeX can't be of any help at =
all.

i don't deny you that, and yet Omega hasn't taken over the world. what =
i'm
trying to convey is that there are a lot of factors that you have to =
take into
account to make something successful; one of it is that you have to =
package
your product in the right way.

and as far as a successor of 2e is concerned it needs the (in my =
opinion) to
be a have a substancial acceptance from the start to survive. you might =
sell a
lot with it underneath but it's success will not be really depending on
whether or not it solves the problems for your language in fact that =
will be,
honnestly, sad as it is, probably the least factor.

so yes, i'm very much interested in getting structures right that can be
deployed successfully on Omega, say, to solve problems like you have =
with your
language and others have with other languages, but that in itself =
doesn't make
others switch to use an Omega based format which doesn't run on their =
site
environment or for which they need to work to make it run.

eventually they might, perhaps without noticing, but initially the =
majority of
the product will have to work suitably on existing environments (most of =
which
are TeX) and still offers a lot of extras that people feel it is worth
switching to it (switching to just the new kernel that is).


frank

------_=_NextPart_001_01C0946B.D6A62C80
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: hyphenation morass</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

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

<P><FONT SIZE=3D2>&nbsp;&gt; Unicode M$Word.) Omega clearly solves this =
problem the &quot;expected&quot; way.</FONT>

<BR><FONT SIZE=3D2>&nbsp;&gt; And yes there more &quot;exotic&quot; =
cases where TeX can't be of any help at all.</FONT>
</P>

<P><FONT SIZE=3D2>i don't deny you that, and yet Omega hasn't taken over =
the world. what i'm</FONT>

<BR><FONT SIZE=3D2>trying to convey is that there are a lot of factors =
that you have to take into</FONT>

<BR><FONT SIZE=3D2>account to make something successful; one of it is =
that you have to package</FONT>

<BR><FONT SIZE=3D2>your product in the right way.</FONT>
</P>

<P><FONT SIZE=3D2>and as far as a successor of 2e is concerned it needs =
the (in my opinion) to</FONT>

<BR><FONT SIZE=3D2>be a have a substancial acceptance from the start to =
survive. you might sell a</FONT>

<BR><FONT SIZE=3D2>lot with it underneath but it's success will not be =
really depending on</FONT>

<BR><FONT SIZE=3D2>whether or not it solves the problems for your =
language in fact that will be,</FONT>

<BR><FONT SIZE=3D2>honnestly, sad as it is, probably the least =
factor.</FONT>
</P>

<P><FONT SIZE=3D2>so yes, i'm very much interested in getting structures =
right that can be</FONT>

<BR><FONT SIZE=3D2>deployed successfully on Omega, say, to solve =
problems like you have with your</FONT>

<BR><FONT SIZE=3D2>language and others have with other languages, but =
that in itself doesn't make</FONT>

<BR><FONT SIZE=3D2>others switch to use an Omega based format which =
doesn't run on their site</FONT>

<BR><FONT SIZE=3D2>environment or for which they need to work to make it =
run.</FONT>
</P>

<P><FONT SIZE=3D2>eventually they might, perhaps without noticing, but =
initially the majority of</FONT>

<BR><FONT SIZE=3D2>the product will have to work suitably on existing =
environments (most of which</FONT>

<BR><FONT SIZE=3D2>are TeX) and still offers a lot of extras that people =
feel it is worth</FONT>

<BR><FONT SIZE=3D2>switching to it (switching to just the new kernel =
that is).</FONT>
</P>
<BR>

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

</BODY>
</HTML>
------_=_NextPart_001_01C0946B.D6A62C80--