X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2045" "Thu" "4" "April" "1996" "09:59:59" "+0200" "Daniel FLIPO" "Daniel.Flipo@UNIV-LILLE1.FR" nil "36" "Re: Changing \\hyphenchar" "^Date:" nil nil "4" nil nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by trudi.zdv.Uni-Mainz.DE (8.6.12/8.6.12) with ESMTP id KAA02318; Thu, 4 Apr 1996 10:00:50 +0200 Received: from listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <10.114AD1FA@listserv.gmd.de>; Thu, 4 Apr 1996 10:00:50 +0200 Received: from URZINFO.URZ.UNI-HEIDELBERG.DE by URZINFO.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 67235 for LATEX-L@URZINFO.URZ.UNI-HEIDELBERG.DE; Thu, 4 Apr 1996 08:59:48 +0100 Received: from lilserv.univ-lille1.fr (lilserv.univ-lille1.fr [134.206.1.15]) by relay.urz.uni-heidelberg.de (8.7.5/8.7.4) with ESMTP id JAA20753 for ; Thu, 4 Apr 1996 09:59:32 +0200 (MET DST) Received: from alea.univ-lille1.fr (alea.univ-lille1.fr [134.206.85.10]) by lilserv.univ-lille1.fr (8.7.1/jtpda-5.1) with SMTP id JAA04157 for ; Thu, 4 Apr 1996 09:59:35 +0200 (MET DST) Received: from localhost.univ-lille1.fr by alea.univ-lille1.fr (4.1/SMI-4.1) id AA15112; Thu, 4 Apr 96 10:00:03 +0200 X-Mailer: exmh version 1.6.5 12/11/95 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <9604040800.AA15112@alea.univ-lille1.fr> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: Your message of "Wed, 03 Apr 1996 11:50:12 -0000." <9604031050.AA26966@r8h.cs.man.ac.uk> Date: Thu, 4 Apr 1996 09:59:59 +0200 From: Daniel FLIPO Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Changing \hyphenchar Status: R X-Status: X-Keywords: X-UID: 1736 First I would like to thank David for his clear presentation of the issue. What Bernard and I feared, was that the next LaTeX2e release (june 96) would set \hyphenchar='177 for (nearly) all T1-encoded fonts (just as the fd files distributed with the present dc fonts do). If a hook can be added, by the way of a .cfg file for instance, to enable format builders to choose between the two settings (\hyphenchar not defined, or \hyphenchar='177), that would be great (for French at least). A question remains: which one will be the default? As you can imagine, Frenchies would vote for \hyphenchar being not defined in T1 (as in OT1), but it's up to the LaTeX3 team to see what is best for most languages. Now, if a format setting \hyphenchar='177 has to be used with French, as David wrote, as compromise has to be found, and I can think of something acceptable (IMHO anyway): 1) We can add a set of hyphenation patterns for French to cope with '-': I have prepared a list of 111 patterns (=+10% of the present list of patterns for French) which seems to do a reasonable job; 2) << Educated French writers >>, I mean people who really care about exact hyphenation (how many are they apart from Bernard, myself, and a handful of others? ;-), can always type ``anarcho\-syndicaliste'' if they want this word to be hyphenated *only* after the `-'; it is a standard and easy way to achieve the hyphenation you want in TeX, and it will work with \hyphenchar defined or not. Btw, could anyone tell me what languages require \hyphenchar='177; mainly, I'd like to know what is the correct setting for English and German. ============================================================================= Daniel Flipo E-mail : Daniel.Flipo@univ-lille1.fr UFR de Mathématiques -- Bâtiment M2 Tel : (33) 20 43 67 75 Université des Sciences et Technologies Fax : (33) 20 43 67 74 F-59655 Villeneuve d'Ascq Cedex France =============================================================================