Crimean Tatar/Crimean Turkish (crh) .orth

Bug #339396 reported by Reşat SABIQ on 2009-03-08
2
Affects Status Importance Assigned to Milestone
Ubuntu Translations
Low
Unassigned
fontconfig (Ubuntu)
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).

Reşat SABIQ (tilde-birlik) wrote :

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.

Victor Vargas (kamus) wrote :

Since this report have a long time without activity, please could you check (if is possible) in latest version included in Ubuntu Lucid if this issue is still happening? Thanks in advance.

Changed in fontconfig (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Victor Vargas (kamus) wrote :

Checking in latest release under Lucid this change is pushed at least in fontconfig-2.8.0-2ubuntu1, so I will mark this report as Fix Released. Thanks!

Changed in fontconfig (Ubuntu):
status: Incomplete → Fix Released
David Planella (dpm) on 2010-08-23
Changed in ubuntu-translations:
status: New → Fix Released
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers