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 f5BEehf12598 for ; Mon, 11 Jun 2001 16:40:43 +0200 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f5BEegp26979 . for ; Mon, 11 Jun 2001 16:40:43 +0200 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 f5BEef023930 for ; Mon, 11 Jun 2001 16:40:41 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0F284.7E016780" 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 QAA01183 for ; Mon, 11 Jun 2001 16:40:40 +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 f5BEedU21107 for ; Mon, 11 Jun 2001 16:40:40 +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 <15.605CFE03@mail.listserv.gmd.de>; Mon, 11 Jun 2001 16:38:15 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 497903 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 11 Jun 2001 16:40:26 +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 QAA17738 for ; Mon, 11 Jun 2001 16:40:24 +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 QAA42836 for ; Mon, 11 Jun 2001 16:40:25 +0200 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 f5BEeO110397 for ; Mon, 11 Jun 2001 16:40:24 +0200 (MET DST) 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 QAA11986 for ; Mon, 11 Jun 2001 16:36:37 +0200 (CEST) In-Reply-To: References: Return-Path: X-Sender: lars@abel.math.umu.se x-mime-autoconverted: from quoted-printable to 8bit by relay.urz.uni-heidelberg.de id QAA17740 Content-class: urn:content-classes:message Subject: Re: \InputTranslation Date: Mon, 11 Jun 2001 15:40:19 +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: 4125 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0F284.7E016780 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 13.05 +0200 2001-06-11, Hans Aberg wrote: >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. Those circumstances are well separated from LaTeX programming, so I = doubt any confusion could occur. >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. No. A localization refers to a change in the interface between user and program, not a change in how the program processes data (once it has = been interpreted). A localization of LaTeX to e.g. Swedish would rather mean that input could look like \dokumentklass{artikel} \b=F6rja{dokument} \titel{Gnuer} and error messages would be given in Swedish, not that the default = language would be Swedish. Lars Hellstr=F6m ------_=_NextPart_001_01C0F284.7E016780 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: \InputTranslation

At 13.05 +0200 2001-06-11, Hans Aberg wrote:
>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.

Those circumstances are well separated from LaTeX = programming, so I doubt
any confusion could occur.

>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.

No. A localization refers to a change in the interface = between user and
program, not a change in how the program processes = data (once it has been
interpreted). A localization of LaTeX to e.g. Swedish = would rather mean
that input could look like

   \dokumentklass{artikel}
   \b=F6rja{dokument}
   \titel{Gnuer}

and error messages would be given in Swedish, not that = the default language
would be Swedish.

Lars Hellstr=F6m

------_=_NextPart_001_01C0F284.7E016780--