"Language Pack" text in "Languages" tab of "Add-ons" window is not translatable.
That's part of the language pack name (taken from the install.rdf file) and so can be written in any language the language pack chooses. I believe that localization of this field is supported in the same way as the description field: http://kb.mozillazine.org/Localize_extension_descriptions
Created attachment 233079 [details] About X Language Pack, in Persian The green part is langpack name, and the red part is the untranslatable string.
My quick test with the Polski, English and Magyar language packs all show that the about dialog displays the name directly from the install.rdf for the language pack. Is the language pack you are using available anywhere?
Here are the lone line of l10n/fa/toolkit/defines.inc: #define MOZ_LANG_TITLE Persian (IR) — فارسی (ایران) As you can see, it contains only the green part. BTW, here are my langpack: http://zwnj.org/proj/mozilla/firefox-2.0b1.fa.langpack-06.08.10-18.00.xpi
Right and the install.rdf for it contains the text Language Pack. I guess this is an issue with the language pack build process.
Component: Extension/Theme Manager → Build Config
12 years ago
QA Contact: extension.manager → build.config
This is not going to be fixed for 2.0, and this is not a Firefox build thing, but more a general toolkit intl problem.
Assignee: nobody → js-console
Component: Build Config → Error Console
OS: Linux → All
Product: Firefox → Core
QA Contact: build.config → error-console
Hardware: PC → All
Version: 2.0 Branch → Trunk
Assignee: js-console → smontagu
Component: Error Console → Internationalization
QA Contact: error-console → amyy
Allowing the "Language Pack" text to be translated (at build time) should be done independently of any client-side fixes for localizable extension descriptions (but I agree it's not worth it for 2.0).
Assignee: smontagu → nobody
Component: Internationalization → Build Config
Product: Core → Toolkit
QA Contact: amyy → build-config
I'm guessing this was fixed in the 11 years since this bug was updated.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.