You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
I've noticed that there are two shortcodes missing from the ru/shortcodes/cldr-native, while being present in the "regular" ru/shortcodes/cldr
Then I've noticed this in the docs
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-nativecldr
data file and as a result of the above-cited rule an exclusion from thecldr-native
data fileIf 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)
The text was updated successfully, but these errors were encountered: