John,
As we do in other areas of internationalization, there can be an
algorithm that anticipates the variety and make customization for
locales very easy. As there is no concept of GetNextGrapheme
that incorporates "ch", and no set of properties defined for
such an object, I feel that is lacking in the standard.
There are allowances throughout the standard certainly, but the tactics
I think could be more clearly defined.
tex
John Cowan wrote:
>
> Tex Texin scripsit:
>
> > I suddenly feel thrown back into the multi-codepage
> > quagmire of researching researching, researching, and probably
> > continually revamping and re-generalizing my software to accomodate
> > new character types as I uncover them.
>
> There's no getting away from this. Some users of Latin treat "ch" as
> unitary, and others don't. Some users of Cyrillic treat various
> 2, 3, or 4-letter strings as unitary, and others don't. Localization
> has to take this behavior into account.
>
> --
> John Cowan cowan@ccil.org
> I am a member of a civilization. --David Brin
--
Progress Software: The #1 Embedded Database
-------------------------------------------------------------------------------------------------------
Tex Texin Director, International Products
Progress Software Corp. Voice: +1-781-280-4271
14 Oak Park Fax: +1-781-280-4949
Bedford, MA 01730 USA texin@bedford.progress.com
http://www.progress.com http://apptivity.progress.com
-------------------------------------------------------------------------------------------------------
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:54 EDT