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 f5BDBof12307 for ; Mon, 11 Jun 2001 15:11:50 +0200 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f5BDBnp26522 . for ; Mon, 11 Jun 2001 15:11:49 +0200 MIME-Version: 1.0 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f5BDBn029412 for ; Mon, 11 Jun 2001 15:11:49 +0200 (MET DST) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0F278.134A2F00" Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id PAA06673 for ; Mon, 11 Jun 2001 15:11:48 +0200 (MEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f5BDBmU05038 for ; Mon, 11 Jun 2001 15:11:48 +0200 (MET DST) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <3.F6F838FC@mail.listserv.gmd.de>; Mon, 11 Jun 2001 15:09:24 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 497676 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 11 Jun 2001 15:11:44 +0200 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 PAA15909 for ; Mon, 11 Jun 2001 15:09:33 +0200 (MET DST) 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 PAA32980 for ; Mon, 11 Jun 2001 15:09:33 +0200 Received: from algonet.se (franklin.tninet.se [195.100.94.106]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f5BD9P113756 for ; Mon, 11 Jun 2001 15:09:25 +0200 (MET DST) Received: from [195.100.226.135] (du135-226.ppp.su-anst.tninet.se [195.100.226.135]) by franklin.tninet.se (BLUETAIL Mail Robustifier 2.2.2) with ESMTP id 357103.264949.992franklin-s2 for ; Mon, 11 Jun 2001 15:09:09 +0200 In-Reply-To: Return-Path: X-Sender: haberg@pop.matematik.su.se x-mime-autoconverted: from quoted-printable to 8bit by relay.urz.uni-heidelberg.de id PAA15910 Content-class: urn:content-classes:message Subject: Re: \InputTranslation Date: Mon, 11 Jun 2001 12:05:33 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Hans Aberg" 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: 4122 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0F278.134A2F00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 00:10 +0200 2001/06/11, Lars Hellstr=F6m wrote: >At Tue, 5 Jun 2001 13:29:19 +0100, Chris Rowley wrote: >[...] >>Therefore, rather than attempting to categorise the necessary >>information and devise suitable ways to provide it, Frank and I came >>up with the idea of simply supplying a single logical label for every >>ICR string. Since the first, and still the overwhelmingly most >>diverse, >>parts of this information came from the needs of multi-lingual >>documents, we called this label the `language' (maybe not a good >>choice). ... >I suggest that we use the term `context' rather than `language' here. >Quoting Webster's, `context' means: > > The part of a written discourse in which a certain word, phrase > or passage appears, necessary to point the meaning, as, it is > hard to tell the exact meaning of a word out of context. The problem here is that "context" is already heavily used in computer lingo: An is in computer lingo a function that maps a name to a storage location, and every such environment produces a = (lookup) context. Normally, what above is called a ``language'', one is already calling a ``localization'' in computer lingo. (Which is may be hard to accept for mathematicians, as a localization has a different meaning in math.) A localization may involve the choice of a human language, but also the other data, like date and number formats, etc. Hans Aberg ------_=_NextPart_001_01C0F278.134A2F00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: \InputTranslation

At 00:10 +0200 2001/06/11, Lars Hellstr=F6m = wrote:
>At Tue, 5 Jun 2001 13:29:19 +0100, Chris Rowley = wrote:
>[...]
>>Therefore, rather than attempting to = categorise the necessary
>>information and devise suitable ways to = provide it, Frank and I came
>>up with the idea of simply supplying a single = logical label for every
>>ICR string.  Since the first, and still = the overwhelmingly most
>>diverse,
>>parts of this information came from the needs = of multi-lingual
>>documents, we called this label the = `language' (maybe not a good
>>choice).
...
>I suggest that we use the term `context' rather = than `language' here.
>Quoting Webster's, `context' means:
>
>   The part of a written discourse in = which a certain word, phrase
>   or passage appears, necessary to = point the meaning, as, it is
>   hard to tell the exact meaning of a = word out of context.

The problem here is that "context" is = already heavily used in computer
lingo: An <em|environment|> is in computer = lingo a function that maps a
name to a storage location, and every such = environment produces a (lookup)
context.

Normally, what above is called a ``language'', one is = already calling a
``localization'' in computer lingo. (Which is may be = hard to accept for
mathematicians, as a localization has a different = meaning in math.)

A localization may involve the choice of a human = language, but also the
other data, like date and number formats, etc.

  Hans Aberg

------_=_NextPart_001_01C0F278.134A2F00--