Received: by nummer-3.proteosys id <01C19443.4D05918C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:42:11 +0100 Return-Path: <@vm.gmd.de:LATEX-L@DHDURZ1.BITNET> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.4D05918C" x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Re: LaTeX 2.09 beta-test Date: Fri, 1 Nov 1991 11:43:09 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Dominik Wujastyk" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 444 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.4D05918C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable \begin{quotation} > Well, either I'm going mad (or am already mad, as many may think), or > else rendering as active precludes the possibility of its > participating in hyphenation patterns and exceptions; if I am not > mistaken, this totally precludes the possibility of establishing > correct hyphenation patterns for the target language. > > ** Phil. \end{quotation} Having (char 130, say) made \active does not of itself preclude hyphenation. If it is \defined to be two characters for which a ligtable command exists in the font's TFM, then you will get hyphenation. Or better yet, if it is \defined to be a single character in a font, say 233 (E9) in the new extended CM, then again, hyphenation will be fine. But if it is \defined to be a string that includes the \accent primitive, then yes, Phil, as you say, hyphenation is inhibited. Dominik ------_=_NextPart_001_01C19443.4D05918C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: LaTeX 2.09 <Oct 91> beta-test

\begin{quotation}

 > Well, either I'm going mad (or am already = mad, as many may think), or
 > else rendering <e-acute> as active = precludes the possibility of its
 > participating in hyphenation patterns and = exceptions; if I am not
 > mistaken, this totally precludes the = possibility of establishing
 > correct hyphenation patterns for the = target language.
 >
 >      =         =         =         =         ** Phil.

\end{quotation}

Having <e-acute> (char 130, say) made \active = does not of itself
preclude hyphenation.  If it is \defined to be = two characters
for which a ligtable command exists in the font's = TFM, then
you will get hyphenation.  Or better yet, if it = is \defined to be
a single character in a font, say 233 (E9) in the new = extended CM,
then again, hyphenation will be fine.

But if it is \defined to be a string that includes the = \accent
primitive, then yes, Phil, as you say, hyphenation is = inhibited.

Dominik


------_=_NextPart_001_01C19443.4D05918C--