Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool2.mu.edu!uunet!mcsun!ukc!slxsys!jclark!jjc From: jjc@jclark.UUCP (James Clark) Newsgroups: comp.text Subject: Re: International (8 bit clean) troff proposal Message-ID: Date: 3 Jan 91 22:49:27 GMT References: <1990Dec27.155046.14520@cbnewsl.att.com> <1991Jan2.231520.21468@mtxinu.COM> Sender: jjc@jclark.uucp (James Clark) Organization: None, London, England Lines: 28 In-Reply-To: jaap@mtxinu.COM's message of 2 Jan 91 23:15:20 GMT In article <1991Jan2.231520.21468@mtxinu.COM> jaap@mtxinu.COM (Jaap Akkerhuis) writes: In article jjc@jclark.UUCP (James Clark) writes: > > would give `\(^a' (the name for `a' with a circumflex accent) a > hyphenation code of `a'. Groff uses the same hyphenation algorithm > that TeX does (invented by Frank Liang): the hyphenation process is > controlled by a set of hyphenation patterns; letters in the patterns > are interpreted as hyphenation codes. By supplying an appropriate > file of patterns and set of `hcode' requests, it should be possible to > make groff correctly hyphenate languages other than English. Not necessarily. This depends on the rules of the language. The hyphenation rules might threat the ``a^'' completely different then an ``a'' for a given language. In that case, mapping is not good enough. There is nothing in the groff scheme that constrains `a^' to have the same hyphenation code as `a'. A hyphenation code can be any single input character that isn't a digit or white space. For example, you could make the hyphenation code of `a^' (and `A^') the character which is `a^' in ISO 8859-1. You just have to make sure that the `hcode' requests match the conventions that were used in the generation of the hyphenation patterns. James Clark jjc@jclark.uucp jjc@ai.mit.edu