Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make native option the "default"/"full" (or a case of two missing shortcodes) #138

Open
eugenesvk opened this issue Nov 3, 2021 · 1 comment

Comments

@eugenesvk
Copy link

I've noticed that there are two shortcodes missing from the ru/shortcodes/cldr-native, while being present in the "regular" ru/shortcodes/cldr

  "1F4BF": "cd",
  "1F4C0": "dvd",

Then I've noticed this in the docs

cldr-native# Like cldr but shortcodes are not transliterated to Latin characters.
Furthermore, this preset will only include shortcodes that do not contain shortcodes that already exist in the cldr preset

and realised that the issue of missing shortcodes is likely due to the fact that Unicode's CLDR ru/annotations.json are not translated but written in English as "CD" and "DVD", so this triggers a match with the non-native cldr data file and as a result of the above-cited rule an exclusion from the cldr-native data file

If that's the case, I'd like to suggest that at least that for non-Latin-based languages the native data file represents the default/full version as it simply makes no sense to use the transliterated version — no user (or even a developer) should ever be exposed to it and be forced to change layouts just to enter an emoji

(for Latin-based languages this might be complicated by the fact that popular apps force English-only shortcodes anyway, though that's also an unnecessary complication and it should be easier for the users of your awesome dataset to use native shortcodes as well instead of checking whether there is an extra shortcode in the non-native file)

@milesj
Copy link
Owner

milesj commented Nov 3, 2021

This makes sense to me. I'll take a look at it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants