Received: by nummer-3.proteosys id <01C19443.4D9229AC@nummer-3.proteosys>; Thu, 3 Jan 2002 11:42:12 +0100 Return-Path: <@vm.gmd.de:LATEX-L@DHDURZ1.BITNET> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.4D9229AC" 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: Hyphenation patterns (not additional patterns) Date: Wed, 6 Nov 1991 18:03:11 +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: 451 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.4D9229AC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I don't really want to join in the discussion about \language, etc., but may I register a couple of points that arise out of my own usage? 1/ I use a full 8-bit charset all the time. My use of 33-127, 157 and 224-255 is particularly heavy. 2/ I have defined chars > 127 to be active, and \def'ed them to output characters that match my (home made) screen fonts. 3/ I have typeset a full book using this setup, as well as many papers and lectures. 4/ I got away with the book, largely because it was mostly English and there wasn't too much difficulty with hyphenation. I still had to = do quite a lot of hyphenation by hand. 5/ I consider my arrangements inadequate for serious work in future. First, because I can't define proper multilingual hyphenation. I need a font that matches my character set. (The Cork character set is almost useless for me, unfortunately. I do Indian languages.) Secondly, because I *do* need to be able to use extended chars in macro names. A current situation is that I have a book with *thousands* of footnote references to other texts. These other texts' names are abbreviated to three or four characters, normally including some extended chars. I want to make these abbreviations into macros that will print themselves *and* write an entry to an index file. I can't do that, at present. Dominik ------_=_NextPart_001_01C19443.4D9229AC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Hyphenation patterns (not additional patterns)

I don't really want to join in the discussion about = \language,
etc., but may I register a couple of points that = arise out of my
own usage?

1/  I use a full 8-bit charset all the = time.  My use of
33-127, 157 and 224-255 is particularly heavy.

2/  I have defined chars > 127 to be active, = and \def'ed them
to output characters that match my (home made) screen = fonts.

3/  I have typeset a full book using this setup, = as well as many
papers and lectures.

4/  I got away with the book, largely because it = was mostly English
and there wasn't too much difficulty with = hyphenation.  I still had to do
quite a lot of hyphenation by hand.

5/  I consider my arrangements inadequate for = serious work in
future.  First, because I can't define proper = multilingual
hyphenation.  I need a font that matches my = character set.  (The
Cork character set is almost useless for me, = unfortunately.  I do
Indian languages.)  Secondly, because I *do* = need to be able
to use extended chars in macro names.  A current = situation is that
I have a book with *thousands* of footnote references = to other texts.
These other texts' names are abbreviated to three or = four characters,
normally including some extended chars.  I want = to make these
abbreviations into macros that will print themselves = *and* write
an entry to an index file.  I can't do that, at = present.

Dominik



------_=_NextPart_001_01C19443.4D9229AC--