Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Wed, 26 Jan 2000 14:07:07 +0100 (MET) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id OAA10699 for ; Wed, 26 Jan 2000 14:07:06 +0100 (MET) MIME-Version: 1.0 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id OAA12250 for ; Wed, 26 Jan 2000 14:07:05 +0100 (MET) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF67FE.3F3D4F80" Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <12.0DD3BD47@mail.listserv.gmd.de>; Wed, 26 Jan 2000 14:06:50 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 449159 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 26 Jan 2000 14:05:38 +0100 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id OAA01095 for ; Wed, 26 Jan 2000 14:05:37 +0100 (MET) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id OAA10949 for ; Wed, 26 Jan 2000 14:05:37 +0100 (MET) Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id OAA12246 for ; Wed, 26 Jan 2000 14:07:00 +0100 (MET) Received: from istrati.zdv.uni-mainz.de (root@dialin367.zdv.Uni-Mainz.DE [134.93.175.67]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id OAA10675 for ; Wed, 26 Jan 2000 14:06:59 +0100 (MET) Received: (from design@localhost) by istrati.zdv.uni-mainz.de (8.9.3/8.9.3) id OAA00341; Wed, 26 Jan 2000 14:08:14 +0100 In-Reply-To: References: Return-Path: x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["1149" "Wed" "26" "January" "2000" "14:08:14" "+0100" "Frank Mittelbach" "frank.mittelbach@LATEX-PROJECT.ORG" nil "25" "Re: templates for galley (paragraph) formatting" "^Date:" nil nil "1" nil nil nil nil nil]nil) X-Authentication-Warning: istrati.zdv.uni-mainz.de: design set sender to design@istrati.zdv.uni-mainz.de using -f Content-class: urn:content-classes:message Subject: Re: templates for galley (paragraph) formatting Date: Wed, 26 Jan 2000 14:08:14 +0100 Message-ID: <200001261308.OAA00341@istrati.zdv.uni-mainz.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Frank Mittelbach" Sender: "Mailing list for the LaTeX3 project" To: "Multiple recipients of list LATEX-L" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 3512 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF67FE.3F3D4F80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Achim writes: > o hyphenation template. This template should IMHO be dropped. The = only > important parameters it sets are (ex)hyphenpenalty which can be = moved > to the linebreak template. I agree that the (ex)hyphenpenalty should perhaps be moved to the = linebreak template as they essentially are parameters that guide the linebreaking. = On the other hand Rune Kleveland made the correct remark that there are extensions to TeX that take the hyphenation methods further and do = perhaps warrant to keep those parameters separate for easier replacement. However, whether the template should be fully abandomed seems to me a different question: i guess one has to ask whether allowing/disallowing hyphenation is a layout design question in its own right. That is, is it likely that one wants to change the galley state in this respect without changing other aspects of the galley? If this is the case then = separating it out makes some sense since otherwise one has to provide a lot of = duplicate template instances which only differ in that aspect. I'm not sure what the answer is. Perhaps there is no need for a = separation in the end. frank ------_=_NextPart_001_01BF67FE.3F3D4F80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: templates for galley (paragraph) formatting

Achim writes:

 > o hyphenation template. This template = should IMHO be dropped. The only
 >   important parameters it sets = are (ex)hyphenpenalty which can be moved
 >   to the linebreak = template.

I agree that the (ex)hyphenpenalty should perhaps be = moved to the linebreak
template as they essentially are parameters that = guide the linebreaking. On
the other hand Rune Kleveland made the correct remark = that there are
extensions to TeX that take the hyphenation methods = further and do perhaps
warrant to keep those parameters separate for easier = replacement.

However, whether the template should be fully = abandomed seems to me a
different question: i guess one has to ask whether = allowing/disallowing
hyphenation is a layout design question in its own = right. That is, is it
likely that one wants to change the galley state in = this respect without
changing other aspects of the galley? If this is the = case then separating it
out makes some sense since otherwise one has to = provide a lot of duplicate
template instances which only differ in that = aspect.

I'm not sure what the answer is. Perhaps there is no = need for a separation in
the end.

frank

------_=_NextPart_001_01BF67FE.3F3D4F80--