<table cellspacing='0' cellpadding='0' border='0' background='none' style='font-family:arial;font-size:10pt;color:#000000;background-color:#ffffff;width:100%;'><tr><td valign='top' style='font: inherit;'><P>please unsubscribe me fro your email list</P>
<P>Adel<BR><BR>Mechanical Engineering Department<BR>Faculty of Engineering<BR>Sana&#39;a University<BR>Sana&#39;a, Yemen<BR>Tel. +967777275285<BR><BR>--- On <B>Tue, 6/17/08, Vladimir Volovich <I><vvv@vsu.ru></I></B> wrote:<BR></P>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid">From: Vladimir Volovich <vvv@vsu.ru><BR>Subject: Re: [tex-live] language.def<BR>To: "Norbert Preining" <preining@logic.at><BR>Cc: artemio@fis.ucm.es, tex-live@tug.org, tex-hyphen@tug.org, "Karl Berry" <karl@freefriends.org><BR>Date: Tuesday, June 17, 2008, 12:01 AM<BR><BR><PRE>"HO" == Heiko Oberdiek writes:
HO> But it would be easily possible to have a data structure as
HO> superset: % language, patterns file, exceptions file, left- and
HO> right-hyphen minima % dialect
HO> Then both language.def and language.dat could be generated easily.
probably, it would be good to have the target encoding (such as t1, il2,
ly1, eu1) in which to load the patterns, specified in the unified file.
(also, versioning, etc). then the same UTF8-encoded pattern file can be
used to pre-load patterns in any supported target encoding.
Best,
v.</PRE></BLOCKQUOTE></td></tr></table><br>