Crimean Tatar/Crimean Turkish (crh) .orth
Bug #339396 reported by
Reşat SABIQ
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Translations |
Fix Released
|
Low
|
Unassigned | ||
fontconfig (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: fontconfig
My primary motivation is to make sure that Crimean Tatar (Crimean Turkish) language support is available in jaunty, and no font-related issues occur. As of now, w/ alpha-5 release, absence of crh.orth doesn't appear to affect anything. If you are sure that its presence or absence doesn't affect anything, which is my suspicion, feel free to close this bug, and wait for crh.orth to come from upstream. Otherwise, please add crh.orth for jaunty release (attached).
Changed in ubuntu-translations: | |
status: | New → Fix Released |
importance: | Undecided → Low |
To post a comment you must log in.
To elaborate on what i meant by "doesn't appear to affect anything", if i set LANG and GDM_LANG to crh_UA.UTF-8 on a shell in alpha-5, i can launch a localized app, or vi or gedit a file containing characters of interest, and there are no font-related issues in the app's UI, or vi, or gedit.