X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["994" "Wed" "3" "April" "1996" "14:04:32" "+0200" "Bernard GAULLE" "gaulle@IDRIS.FR" nil "26" "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.7.5/8.6.12) with ESMTP id OAA12460; Wed, 3 Apr 1996 14:06:24 +0200 (MET DST) Received: from listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <7.31E46D77@listserv.gmd.de>; Wed, 3 Apr 1996 14:06:19 +0200 Received: from URZINFO.URZ.UNI-HEIDELBERG.DE by URZINFO.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 66244 for LATEX-L@URZINFO.URZ.UNI-HEIDELBERG.DE; Wed, 3 Apr 1996 13:04:54 +0100 Received: from lumiere.idris.fr (root@lumiere.idris.fr [130.84.8.14]) by relay.urz.uni-heidelberg.de (8.7.5/8.7.4) with ESMTP id OAA02520 for ; Wed, 3 Apr 1996 14:04:45 +0200 (MET DST) Received: from murnau.idris.fr (murnau.idris.fr [130.84.8.20]) by lumiere.idris.fr (8.7.5/8.7.3) with ESMTP id OAA26831 for ; Wed, 3 Apr 1996 14:04:34 +0200 Received: (from gaulle@localhost) by murnau.idris.fr (8.7.5/8.7.1) id OAA04515; Wed, 3 Apr 1996 14:04:32 +0200 Message-ID: <199604031204.OAA04515@murnau.idris.fr> Reply-To: Mailing list for the LaTeX3 project Date: Wed, 3 Apr 1996 14:04:32 +0200 From: Bernard GAULLE 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: 1735 >>>>> On Wed, 3 Apr 1996 11:50:12 BST, >>>>> David Carlisle write about "Re: Changing \hyphenchar": DC> So in the present circumstances having the two sets of fd files is DC> quite useful [...] ok but a little bit messy... DC> Well I agree that anyway typing ^^7f is not a possibility, [...] DC> It has to come at the end of a line it may not DC> be used mid-line as it sticks out on the right. right. DC> However all this discussion is clarifying what the *current* position DC> is. Probably a more useful discusion is to discuss what functionality DC> people need for various languages, and how that might be declared... One cs like \DefaultHyphenchar per (text) fontencoding could be the first tool to allow font loading with a chosen \hyphenchar. By default, no hyphenchar will be given. The second tool, here for the installation, is needed for seting \DefaultHyphenchar. fonttext.cfg could be a place where to do this. --bg