From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,699cc914522aa7c4
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail
NNTP-Posting-Date: Tue, 23 Jan 2007 18:08:41 -0600
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
References: <eog0g5$2bn$1@cernne03.cern.ch> <u7ivnp09z.fsf@stephe-leake.org>
  <eoinoh$855$1@cernne03.cern.ch> <ud55drgzz.fsf@stephe-leake.org>
  <eolaen$b4h$1@cernne03.cern.ch> <ur6trwdov.fsf@stephe-leake.org>
  <eoqhhm$fjp$1@cernne03.cern.ch> <uac0dyap7.fsf@stephe-leake.org>
  <ep203u$o6s$1@cernne03.cern.ch> <u3b62dqj5.fsf@stephe-leake.org>
Subject: Re: Structured exception information
Date: Tue, 23 Jan 2007 18:10:05 -0600
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
Message-ID: <bsmdndeExq8UPivYnZ2dnUVZ_riknZ2d@megapath.net>
NNTP-Posting-Host: 64.32.209.38
X-Trace: 
 sv3-kMavHvypgYec5SxSW741+gax4Uuodnxk0WkjvploW6KIW4oh4reQs9uKqS4eatVjBtrZIeC8Qo99hGC!kFF6ty/dHTG4opUgsbTfHfL/6TVh/BlNROiX5Oyq4aY2l7kPb3nVqzVMtvcXl09lQocwQ3kSUNbA!oN98LDylPCeoBQ==
X-Complaints-To: abuse@megapath.net
X-DMCA-Complaints-To: abuse@megapath.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.3.32
Xref: g2news2.google.com comp.lang.ada:8453
Date: 2007-01-23T18:10:05-06:00
List-Id: <comp.lang.ada>

"Stephen Leake" <stephen_leake@stephe-leake.org> wrote in message
news:u3b62dqj5.fsf@stephe-leake.org...
...
> > The HTTP network component should not be aware about the
> > multilanguage abilities of the browser.
>
> Ah, internationalization of error messages. Again, I think the HTTP
> component itself needs to be internationalized to make that work
> properly, so it is simpler for the HTTP component to put the error
> message string in the exception. That way, it can be used in a program
> that is not otherwize internationalized.

Umm, even I (who think internationalization is a total waste of effort)
realize that's completely impossible. Who could possibility write an HTTP
component that could put its error messages into the literally hundreds of
different languages that are in use out there. It would be, at best,
unnecessary coupling: I surely don't want the overhead of Italian and
Russian support, for example in my programs that are likely to only be used
by English-speaking people.

If Internationalization is a requirement, you pretty much have to remove all
natural language from your lower-level components. Then at least you can let
the UI be filled in by people with the appropriate local skills.

                 Randy.