The Unicode Standard and ISO
Steven R. Loomis via Unicode
unicode at unicode.org
Sat Jun 9 23:21:40 CDT 2018
The idea is not necessarily without merit. However, CLDR does not usually
expand scope just because of a suggestion.
I usually recommend creating a new project first - gathering data, looking
at and talking to projects to ascertain the usefulness of common messages..
one of the barriers to adding new content for CLDR is not just the design,
but collecting initial data. When emoji or sub-territory names were added,
many languages were included before it was added to CLDR.
Also note CLDR does have some typographical terms for use in UI, such as
'bold' and 'italic'
On Sat, Jun 9, 2018 at 3:41 PM Marcel Schneider via Unicode <
unicode at unicode.org> wrote:
> On Sat, 9 Jun 2018 12:56:28 -0700, Asmus Freytag via Unicode wrote:
> > On 6/9/2018 12:01 PM, Marcel Schneider via Unicode wrote:
> > > Still a computer should be understandable off-line, so CLDR providing
> a standard library of error messages could be
> > > appreciated by the industry
> The kind of translations that CLDR accumulates, like day, and month
> names, language and territory names, are a widely
> > applicable subset and one that is commonly required in machine generated
> or machine-assembled text (like displaying
> > the date, providing pick lists for configuration of locale settings,
> > The universe of possible error messages is a completely different beast.
> > If you tried to standardize all error messages even in one language you
> would never arrive at something that would be
> > universally useful. While some simple applications may find that all
> their needs for communicating with their users are
> > covered, most would wish they had some other messages available.
> > However, a high-quality terminology database recommends itself (and
> doesn't need any procurement standards).
> > Ultimately, it was its demonstrated usefulness that drove the adoption
> of CLDR.
> This is why I’m so hopeful that CLDR will go much farther than date and
> time and other locale settings, and emoji names and keywords.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Unicode