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 f5BIjVf13629 for ; Mon, 11 Jun 2001 20:45:31 +0200 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f5BIjTp28212 . for ; Mon, 11 Jun 2001 20:45:30 +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 f5BIjT000419 for ; Mon, 11 Jun 2001 20:45:29 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0F2A6.B0BC5780" 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 UAA26454 for ; Mon, 11 Jun 2001 20:45:28 +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 f5BIjSU18610 for ; Mon, 11 Jun 2001 20:45:28 +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 <9.93C9A9D5@mail.listserv.gmd.de>; Mon, 11 Jun 2001 20:43:04 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 498104 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 11 Jun 2001 20:45:25 +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 UAA20712 for ; Mon, 11 Jun 2001 20:45:01 +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 UAA24474 for ; Mon, 11 Jun 2001 20:45:02 +0200 Received: from algonet.se (sinclair.tninet.se [195.100.94.101]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f5BIj1115438 for ; Mon, 11 Jun 2001 20:45:01 +0200 (MET DST) Received: from [195.100.226.130] (du130-226.ppp.su-anst.tninet.se [195.100.226.130]) by sinclair.tninet.se (BLUETAIL Mail Robustifier 2.2.2) with ESMTP id 428376.285094.992sinclair-s2 for ; Mon, 11 Jun 2001 20:44:54 +0200 In-Reply-To: References: Return-Path: X-Sender: haberg@pop.matematik.su.se x-mime-autoconverted: from quoted-printable to 8bit by relay.urz.uni-heidelberg.de id UAA20714 Content-class: urn:content-classes:message Subject: Re: \InputTranslation Date: Mon, 11 Jun 2001 19:43:41 +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: 4127 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0F2A6.B0BC5780 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 16:40 +0200 2001/06/11, Lars Hellstr=F6m wrote: >>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. There are no such requirements in current usage: For example, C++ = supports localized components within programs. C++ also uses the name "locale", not "localization", which is perhaps a better name (shorter). Another variation is "locality". Or someone come up with a better name that somehow indicates an = indicative property of the defined contexts we are discussing. Hans Aberg ------_=_NextPart_001_01C0F2A6.B0BC5780 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: \InputTranslation

At 16:40 +0200 2001/06/11, Lars Hellstr=F6m = wrote:
>>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.

There are no such requirements in current usage: For = example, C++ supports
localized components within programs.

C++ also uses the name "locale", not = "localization", which is perhaps a
better name (shorter). Another variation is = "locality".

Or someone come up with a better name that somehow = indicates an indicative
property of the defined contexts we are = discussing.

  Hans Aberg

------_=_NextPart_001_01C0F2A6.B0BC5780--