Correct way for reporting CLDR data errors/tweaks?

[Steven R. Loomis]

That’s a good place to start. But you could outline the issues here in email first if you want.
-s


> El mar 10, 2016, a las 1:21 PM, Gregory Huczynski <gh_online at me.com> escribió:
> 
> Hi there,
> 
> What’s the correct way for reporting CLDR data errors/tweaks?
> Should I submit tickets using http://unicode.org/cldr/trac/newticket <http://unicode.org/cldr/trac/newticket>?
> 
> I’ve been programmatically consuming CLDR in JSON form, and have come across some data inconsistencies that may need correcting.
> 
> Many thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20160310/cb79c2e9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://unicode.org/pipermail/cldr-users/attachments/20160310/cb79c2e9/attachment.asc>