Closed Bug 436668 Opened 16 years ago Closed 15 years ago

Localize name and description for the default theme

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
minor

Tracking

()

RESOLVED FIXED
mozilla1.9.3a1
Tracking Status
status1.9.2 --- beta1-fixed

People

(Reporter: egamonal, Assigned: stef)

References

Details

Attachments

(2 files, 2 obsolete files)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; ca; rv:1.9pre) Gecko/2008053004 Minefield/3.0pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; ca; rv:1.9pre) Gecko/2008053004 Minefield/3.0pre

in «Themes» tab, the default theme is:

«Default   3.0pre
The default theme.»

Same for «Default plugin»

Are name and description to be localized for these elements? If they are hardcoded, maybe we should change it.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Product: Firefox → Toolkit
We should be able to use the regular method for localising an add-ons data for this
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [good first bug]
Trying to figure this out since it's marked 'good first bug'.

The patch will localize the default theme text using the standard rdf localization technique.  The 'Default Plugin' text comes from modules/plugin/default/unix/nullplugin.h -- any pointers about localizing header files?
Altering the install.rdf isn't I think the way to go here. Instead we should use the older method of localizing. This would involve adding localized preferences to firefox.js for the theme's name and description and having them pull their value from a properties file out of the locale. See http://developer.mozilla.org/en/Localizing_extension_descriptions#Localizing_before_Gecko_1.9 for more details.

I'm not sure what we can do with the default plugin for the time being, is it even enabled by default anymore?
(In reply to comment #3)
> I'm not sure what we can do with the default plugin for the time being, is it
> even enabled by default anymore?

Enabled but not registered for all content (*) types?
plugin.default_plugin_disabled is set to true in Firefox 3.5 but the about:plugins page lists it and in Tools → Addons → Plugins it is in enabled state.

Disabled or not, its description is visible in UI by default and it should be possible to localize it. (btw, bug 244477 is about the same)
Yeah lets keep this bug purely for the default theme, localizing the default plugin is a harder prospect.
Summary: can't localize «default theme» and «default plugin» name and description → Localize name and description for the default theme
Target Milestone: --- → mozilla1.9.2
Attached patch patch, v1 (obsolete) — Splinter Review
Attached patch the fix (obsolete) — Splinter Review
I'm not sure who should review this and if the new lines are in the good enough place.
Attachment #386628 - Attachment is obsolete: true
Attachment #386950 - Flags: review?
Attachment #386950 - Flags: review? → review?(dtownsend)
Comment on attachment 386950 [details] [diff] [review]
the fix

Looks good, thanks
Attachment #386950 - Flags: review?(dtownsend) → review+
Pushed to m-c: http://hg.mozilla.org/mozilla-central/rev/4efc65d6447d

Thanks for the patch.
Assignee: nobody → splewako
Status: NEW → RESOLVED
Closed: 15 years ago
OS: Linux → All
Hardware: x86 → All
Resolution: --- → FIXED
Whiteboard: [good first bug]
Target Milestone: mozilla1.9.2 → mozilla1.9.2b1
Bah, more toolkit prefs in firefox.js :-(
(In reply to comment #10)
> Bah, more toolkit prefs in firefox.js :-(

Surely we could have put these in all.js at least until a toolkit.js file is created?
I've backed this out, we need to consider whether this should apply to other applications or not.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: mozilla1.9.2b1 → mozilla1.9.2
Blocks: 509010
Comment on attachment 386950 [details] [diff] [review]
the fix

I think after further consideration this is wrong and the theme name and description should come from the Firefox locale (as currently happens).

Move the strings into browser/locales/en-US/chrome/browser/browser.properties and update the preference values and this will be right.
Attachment #386950 - Flags: review+ → review-
Attached patch updated patchSplinter Review
(In reply to comment #13)
> Move the strings into browser/locales/en-US/chrome/browser/browser.properties
> and update the preference values and this will be right.
Attachment #386950 - Attachment is obsolete: true
Attachment #394267 - Flags: review?(dtownsend)
Attachment #394267 - Flags: review?(dtownsend) → review+
Comment on attachment 394267 [details] [diff] [review]
updated patch

I'll land this when the tree is clear enough
Landed: http://hg.mozilla.org/mozilla-central/rev/432fb39d5655
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
Target Milestone: mozilla1.9.2 → mozilla1.9.3
Target Milestone: mozilla1.9.3 → mozilla1.9.3a1
Attachment #394267 - Flags: approval1.9.2?
Comment on attachment 394267 [details] [diff] [review]
updated patch

No risk patch, this just allows out localisers to customise the default theme name and description
Comment on attachment 394267 [details] [diff] [review]
updated patch

a=me if this lands today
Attachment #394267 - Flags: approval1.9.2? → approval1.9.2+
Blocks: 624405
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: