#102 Locale issues

[Steve Jenson]

At
http://www.eros-os.org/pipermail/e-lang/2004-March/009629.html
Kevin Reid writes:

Dan Bornstein <danfuzz@milk.com> wrote:

> Kevin Reid wrote:
> > Against dot-props: [...], involves a transformation of
> > identifiers ("foo" => "getFoo") (which complicates
textual
> > searching of unexpanded source code) [...]
>
> Another thing to be aware of in the territory of name
transformation
> is that capitalization rules depend on your locale.
The easy case to
> point out is that in Turkish, the letter "i" when
capitalized
> doesn't turn into "I" but rather to U+0130 ("LATIN
CAPITAL LETTER I
> WITH DOT ABOVE").

Hm.

Consider the string/twine methods to*Case and *IgnoreCase.

If they work only for English capitalization, then they
will cause (as
the easiest path for the programmer, even if there are
more correct
mechanisms) unnecessarily
broken-with-regard-to-capitalization programs.

If they use the current locale, they break determinism
and confinement.

Perhaps they should be moved to locale objects (of
which the current
locale should then be made readily accessible, perhaps
in the
privilegedScope).

[Mark Samuel Miller]

Logged In: YES
user_id=54168

E follows Java here. Java defines both locale-independent
and locale-dependent APIs for case handling, presumably
based on Unicode. The above issues in E are mapped to Java's
semantics for locale-independent case handling.