Re: Ada.Locales pseudo-string types

["Randy Brukardt" <randy@rrsoftware.com>]

"Michael Rohan" <michael@zanyblue.com> wrote in message 
news:a6439817-c750-4c5e-a0db-2c37331b474e@googlegroups.com...
...
> It this really the all that's defined for Locales!  At least the language 
> code is
> of the correct length 1 .. 3, however the country code should also be 1 .. 
> 3,

These codes come from other ISO standards, used in many applications 
(including Posix). The lengths and definitions are exactly as those other 
standards (ISO 639-3 and ISO 3166-1) prescribe. You can look up the country 
and language codes on-line (both of those standards are public). See the 
list of other standards referenced by the Ada Standard for details.

...
>Looks like this probably needs to be adjusted Language 1 .. 3 is OK, but 
>Country
> should really be Territory 1 .. 3, e.g., Latin America has the code "419".

Umm, no it doesn't.

> It is also missing a definition for the Script, e.g., Simplified Chinese 
> as
> spoken in China is zh_Hans_CN, and Serbian has two variants for the same 
> territory:

That's part of the language code. Again, see the relevant ISO standards.

...
>There's nothing here to adjust locale, etc.

That's intentional: not all systems allow that.

> I guess this is start on making Ada locale aware but it looks like there's 
> a lot of additional work needed.

Of course, having this information doesn't necessarily allow you to do 
anything with it. There was absolutely no agreement on the value of having 
any such capabilities in the Standard (and capabilities of host OSes vary 
wildly). But just retrieving the current information was easy enough to 
support, and it allows programming in-house solutions on top of it. (For 
instance, the original requirement came from Canada, which needs to support 
both English and French in applications, but doesn't necessarily want to go 
beyond that.)

                                          Randy.


                                   Randy.