# Re: localization

Masataka Ohta (mohta@necom830.cc.titech.ac.jp)
Wed, 7 Feb 96 12:32:21 JST

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Masataka Ohta: "Re: http charset labelling"
- Previous message: Masataka Ohta: "Re: http charset labelling"
- In reply to: Hamilton,Dennis: "Re: localization"

    From: Masataka Ohta <mohta@necom830.cc.titech.ac.jp>

    Message-Id: <199602070332.MAA18697@necom830.cc.titech.ac.jp>

    Subject: Re: localization

    To: Dennis_Hamilton@pa.xerox.com (Hamilton Dennis)

    Date: Wed, 7 Feb 96 12:32:21 JST

    In-Reply-To: <"<FB5F173181CF617C>FB5F173181CF617C@X-PA-PAHV-XS-MS1.xerox"@-SMF->; from "Hamilton,Dennis" at Feb 6, 96 6:40 am

> In an earlier exchange on the the URI distribution list, you made the
> comment "that's why localization doesn't work" or something like that.
>
> I thought that was interesting.
>
> On reflection, I'm not clear what you saw.
>
> Are you saying that there is an inherent defect in localization?

In this case, yes.

> Do
> you mean in principle or in a particular way of doing it?
> I want to understand this better.

Sometimes, like with full ISO 2022, multiple localizations can be
freely mixed, in which case, localization can be a step toward
internationalization.

But, having mutually exclusive localizations and switch between them
is just a pain, which is why EUC nor UNICODE is not internationalization.

As for URLs, localized people can not be compatible with
localized URLs unless they share the same locale.

Masataka Ohta

- Next message: Masataka Ohta: "Re: http charset labelling"
- Previous message: Masataka Ohta: "Re: http charset labelling"
- In reply to: Hamilton,Dennis: "Re: localization"