Locale bringup and barriers for entry

[Steven R. Loomis via CLDR-Users]

The numbering system is defined in TR 35 in
https://unicode.org/reports/tr35/tr35-numbers.html#Numbering_Systems in
terms of either '*numeric*' (which are decimal systems, just substituting
different digits for "0123456789", such as “꘠꘡꘢꘣꘤꘥꘦꘧꘨꘩”  for the Vai
language, or else *algorithmic* which are more complex rule based. I
suppose octal and tonal (hexadecimal?!) could be supported by the
algorithmic approach.





On Tue, Sep 25, 2018 at 2:27 PM Luke Dashjr <luke at dashjr.org> wrote:

> It's been a while since I tried, but I didn't see any possible way to
> define a
> locale's number system (eg, octal or tonal instead of decimal).
>
> On Saturday 22 September 2018 00:34:27 Steven R. Loomis via CLDR-Users
> wrote:
> > Hello, and welcome to the new cldr-users members.
> >
> > For discussion:
> >
> > At the IUC conference last week, a few of us discussed around lunch some
> > issues around getting new locales into CLDR, and barriers to entry.
> >
> > Barriers:
> > - we discussed that it could be confusing or difficult to collect all of
> > the data needed for a minimal locale:
> > http://cldr.unicode.org/index/cldr-spec/minimaldata - especially
> > pluralization data
> > - what about fonts? keyboards?
> > - what are the best ways to coordinate efforts between the language users
> > and different technical experts?
> >
> > Ideas:
> > - a web app to take in new locale data?
> > - a web app to debug/explore plurals?
> > - allowing some locales to 'get started' without plural rules?
> >
> > Links for discussion:
> > - Elnaz and Steven's prez from (last) Monday: https://goo.gl/sN7biw
> > - My "full stack" blog post:
> > https://srl295.github.io/2017/06/06/full-stack-enablement/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20180925/7c4ebabd/attachment.html>