Closed Bug 412994 Opened 17 years ago Closed 16 years ago

[kk] Kazakh: Firefox

Categories

(Mozilla Localizations :: Registration & Management, defect)

Product:
Mozilla Localizations
Component:
Registration & Management
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: tha_undertaker, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20061201 Firefox/2.0.0.6 (Ubuntu-feisty)
Build Identifier: [kk-KZ] Kazakh: Firefox

I would like to restart bug for Localization of Firefox for Kazakh. The language and
country code are respectively 'kk' and 'KZ'.
I'm working now under 2.0.0.x version, but soon I'll work in 3.0 direction.

Reproducible: Always
We should make some educated decision on the locale code. I somehow don't find the -KZ suffix to be really valuable. Looking at http://en.wikipedia.org/wiki/Kazakh_language, it might make sense to add the script, though, yielding kk-Cyrl.

What do you think?
Assignee: nobody → registration
Status: UNCONFIRMED → NEW
Component: Other → Registration & Management
Ever confirmed: true
QA Contact: registration
Summary: renewal of old 287583 bug → [kk] Kazakh: Firefox
I think there are no important reasons to change it by now, because kk_KZ is used everywhere in other software as locale code, and I have serious doubt about going into Latin letters in Kazakhstan. But my opinion isn't a last instance.
Hi Sergey:

Due to the lack of recent activity on this bug, we are going to resolve it as "incomplete".  If you choose to restart translation activity, then no problem at all.  Please notify the l10n-drivers team using the l10n mailing list (dev-l10n@lists.mozilla.org) and file a new bug in Bugzilla.  That bug should indicate that you are interested in translating the upcoming version of Firefox, which is 3.1 right now.

All the best,
SethB
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.