Received: by nummer-3.proteosys id <01C19443.4BD26694@nummer-3.proteosys>; Thu, 3 Jan 2002 11:42:09 +0100 In-Reply-To: Don Hosek's message of Tue, 29 Oct 91 12:37:00 PST <9110292039.AA02651@ufer.ZIB-Berlin.DE> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.4BD26694" Organization: Konrad-Zuse-Zentrum fuer Informationstechnik Berlin X-MimeOLE: Produced By Microsoft Exchange V6.5 Return-Path: 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]) Content-class: urn:content-classes:message Subject: LaTeX 2.09 beta-test Date: Wed, 30 Oct 1991 10:30:10 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Rainer Schoepf" To: Cc: Status: R X-Status: X-Keywords: X-UID: 431 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.4BD26694 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Don, Sorry, I'm not a mathematician so I misuse terms all the time. I didn't mean that the mapping was mathematically 1-to-1, but that a single byte must map to a single byte. Check it out. Now, there I agree. So, if one wants to have \^^80 to mean a c with cedilla, he must define a macro. This is only possible (in general if the category code of ^^80 is letter. (see below.) Rainer, I'm not sure what you're getting at. Let me, however, provide a scenario for you. This is what is happening on one of my contracts: The end goal of all our efforts is to produce a variety of documents for chemical products: bottle labels, boxes, safety inserts, etc. These documents generally have six languages appearing on them (English, French, German, Italian, Japanese and Spanish). The text which appears in the documents is typed in on PCs by the translators and then transferred to a VMS system to be stored in a large database. Database queries produce files which when given to TeX can print the various documents involved. Now, in the production environment, the file output by the database is stored in a directory on the VAX which is accessible both as a VMS directory and =7F{through PCSA as a DOS directory. This allows the user to either run the TeX process on the VAX to produce a final printed label or locally on his PC to print draft output on a local laser printer. The same identical file containing 8-bit ASCII must run under both systems without modification. Am I to write a program which goes through and changes every occurence of C-cedilla to ^^80 before doing this? No, I didn't say that. I can see several possibilities for this, like having the same code page on both systems, having the TeX job on the VAX go through a preprocessing step, or even making some characters active that are in different positions in both code pages. Making all characters active is, in my opinion, a bad solution -- for a default. The real problem is this: you *need* to tag the files with the character set used, and the program to work on them must use this information. Unless this problem is addressed and solved, we cannot get any further. By the way, you qdidn't address the issue of why making chars 128-255 active is so horrible. Because characters of catcode 11 are rather special: only they can be used in control sequences. And besides, it's a hell of an overhead. Rainer ------_=_NextPart_001_01C19443.4BD26694 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable LaTeX 2.09 <Oct 91> beta-test

Don,

   Sorry, I'm not a mathematician so I = misuse terms all the time. I
   didn't mean that the mapping was = mathematically 1-to-1, but that
   a single byte must map to a single byte. = Check it out.

Now, there I agree. So, if one wants to have \^^80 to = mean a c with
cedilla, he must define a macro. This is only = possible (in general if
the category code of ^^80 is letter. (see = below.)

   Rainer, I'm not sure what you're getting = at. Let me, however,
    provide a scenario for you. This = is what is happening on one of
    my contracts:

    The end goal of all our efforts is = to produce a variety of
    documents for chemical products: = bottle labels, boxes, safety
    inserts, etc. These documents = generally have six languages
    appearing on them (English, = French, German, Italian, Japanese
    and Spanish). The text which = appears in the documents is typed
    in on PCs by the translators and = then transferred to a VMS
    system to be stored in a large = database. Database queries
    produce files which when given to = TeX can print the various
    documents involved. Now, in the = production environment, the file
    output by the database is stored = in a directory on the VAX which
    is accessible both as a VMS = directory and =7F{through PCSA as a
    DOS directory. This allows the = user to either run the TeX
    process on the VAX to produce a = final printed label or locally
    on his PC to print draft output on = a local laser printer. The
    same identical file containing = 8-bit ASCII must run under both
    systems without modification. Am I = to write a program which goes
    through and changes every = occurence of C-cedilla to ^^80 before
    doing this?

No, I didn't say that. I can see several possibilities = for this, like
having the same code page on both systems, having the = TeX job on the
VAX go through a preprocessing step, or even making = some characters
active that are in different positions in both code = pages. Making all
characters active is, in my opinion, a bad solution = -- for a default.

The real problem is this: you *need* to tag the files = with the
character set used, and the program to work on them = must use this
information. Unless this problem is addressed and = solved, we cannot
get any further.

   By the way, you qdidn't address the issue = of why making chars
   128-255 active is so horrible.

Because characters of catcode 11 are rather special: = only they can be
used in control sequences. And besides, it's a hell = of an overhead.

Rainer

------_=_NextPart_001_01C19443.4BD26694--