Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f1NG26r07546 for ; Fri, 23 Feb 2001 17:02:06 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1NG26s12784 . for ; Fri, 23 Feb 2001 17:02:06 +0100 MIME-Version: 1.0 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1NG15H01308 for ; Fri, 23 Feb 2001 17:01:05 +0100 (MET) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09DB1.F7E31300" 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 RAA24389 for ; Fri, 23 Feb 2001 17:01:04 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1NG13Q14769 for ; Fri, 23 Feb 2001 17:01:03 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <14.A516AF36@mail.listserv.gmd.de>; Fri, 23 Feb 2001 17:00:53 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 493365 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 23 Feb 2001 17:00:59 +0100 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id RAA19689 for ; Fri, 23 Feb 2001 17:00:58 +0100 (MET) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id RAA38726 for ; Fri, 23 Feb 2001 17:00:50 +0100 Received: from abel.math.umu.se (abel.math.umu.se [130.239.20.139]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1NG0nh04363 for ; Fri, 23 Feb 2001 17:00:49 +0100 (MET) Received: from [130.239.20.144] (mac144.math.umu.se [130.239.20.144]) by abel.math.umu.se (8.9.2/8.9.2) with ESMTP id QAA12041 for ; Fri, 23 Feb 2001 16:58:49 +0100 (CET) In-Reply-To: Return-Path: X-Sender: lars@abel.math.umu.se x-mime-autoconverted: from quoted-printable to 8bit by relay.urz.uni-heidelberg.de id RAA19690 Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary 2.0 Date: Fri, 23 Feb 2001 17:00:48 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: =?iso-8859-1?Q?Lars_Hellstr=F6m?= 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: 4006 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09DB1.F7E31300 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 18.18 +0100 2001-02-19, jbezos wrote: >> Question raised by this: Can OCPs output control sequences, or do = they just >> produce characters? > >They can output any token (IIRC there is a bug >when \input is used, but I'm not sure). In fact, >tokens are necessary when translating Unicode to, >say, OT1. > >>Can one specify what catcode the characters should have? > >Unfortunately not. The catcodes used are the >catcodes when the replacement is done. That means >that "private" names containing @ cannot be >used (in general, or if \csname is used). OK, so in fact the OCPs cannot produce tokens (they just output characters), but that is not really a restriction as long as some = character has catcode 0 and \csname (or some disguise of it) is available. (The former condition could be a problem in \verb-like contexts. One would probably have to have a "private escape" character for the OCPs.) On the other side of things, how does Omega handle "lost character" conditions? The current TeX behaviour of ignoring the character and possibly putting an info message in the log file could certainly be improved ... When one is typesetting normal text the approriate action would be (a) substitution with a character from another font (LaTeX can = do this for characters are represented by encoding-specific commands, but there are no such mechanisms in TeX for explicit character tokens), (b) = an error message, or (c) a combination of the two. When one is typesetting verbatim (or verbatim-like) text however, the priorities are different. = In particular, I would like to have some recourse to (d): Typeset a = suitable representation (e.g. U+0312, in a suitably distinct font) of the Unicode for the character. Lars Hellstr=F6m ------_=_NextPart_001_01C09DB1.F7E31300 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary 2.0

At 18.18 +0100 2001-02-19, jbezos wrote:
>> Question raised by this: Can OCPs output = control sequences, or do they just
>> produce characters?
>
>They can output any token (IIRC there is a = bug
>when \input is used, but I'm not sure). In = fact,
>tokens are necessary when translating Unicode = to,
>say, OT1.
>
>>Can one specify what catcode the characters = should have?
>
>Unfortunately not. The catcodes used are = the
>catcodes when the replacement is done. That = means
>that "private" names containing @ = cannot be
>used (in general, or if \csname is used).

OK, so in fact the OCPs cannot produce tokens (they = just output
characters), but that is not really a restriction as = long as some character
has catcode 0 and \csname (or some disguise of it) is = available. (The
former condition could be a problem in \verb-like = contexts. One would
probably have to have a "private escape" = character for the OCPs.)

On the other side of things, how does Omega handle = "lost character"
conditions? The current TeX behaviour of ignoring the = character and
possibly putting an info message in the log file = could certainly be
improved ...  When one is typesetting normal = text the approriate action
would be (a) substitution with a character from = another font (LaTeX can do
this for characters are represented by = encoding-specific commands, but
there are no such mechanisms in TeX for explicit = character tokens), (b) an
error message, or (c) a combination of the two. When = one is typesetting
verbatim (or verbatim-like) text however, the = priorities are different. In
particular, I would like to have some recourse to = (d): Typeset a suitable
representation (e.g. U+0312, in a suitably distinct = font) of the Unicode
for the character.

Lars Hellstr=F6m

------_=_NextPart_001_01C09DB1.F7E31300--