Closed
Bug 562760
Opened 15 years ago
Closed 15 years ago
Language packs do not show up as installed
Categories
(Toolkit :: Add-ons Manager, defect, P2)
Toolkit
Add-ons Manager
Tracking
()
VERIFIED
FIXED
mozilla2.0b1
Tracking | Status | |
---|---|---|
blocking2.0 | --- | beta1+ |
People
(Reporter: whimboo, Assigned: mossop)
References
Details
(Keywords: regression, Whiteboard: [rewrite])
Attachments
(2 files, 1 obsolete file)
1.22 KB,
patch
|
Unfocused
:
review+
|
Details | Diff | Splinter Review |
4.35 KB,
patch
|
mossop
:
review+
|
Details | Diff | Splinter Review |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a5pre) Gecko/20100427 Minefield/3.7a5pre
There is no way to install language packs into Firefox. There is no entry visible inside the Languages pane.
Steps:
1. Go to http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central-l10n/
2. Click on an XPI and start the installation
After the language pack has been installed, no entry in the Language pane is visible, even not after a restart.
Assignee | ||
Updated•15 years ago
|
Priority: -- → P2
Assignee | ||
Comment 1•15 years ago
|
||
Looks like the UI is looking for add-ons of type "language" and the API is calling them "locale", not sure which makes most sense right now.
Reporter | ||
Comment 2•15 years ago
|
||
(In reply to comment #1)
> Looks like the UI is looking for add-ons of type "language" and the API is
> calling them "locale", not sure which makes most sense right now.
CC'ing Axel to see if he has a promptly idea.
Comment 3•15 years ago
|
||
Well, the language pack itself claims to be an "8".
![]() |
||
Comment 4•15 years ago
|
||
(In reply to comment #1)
> Looks like the UI is looking for add-ons of type "language" and the API is
> calling them "locale", not sure which makes most sense right now.
Well, we've been using "locale" internally for ages, and the chrome URL and type for language support is also called "locale", so it would be most consistent to use that here as well, I guess.
Just my 2c.
Assignee | ||
Updated•15 years ago
|
blocking2.0: --- → beta1+
Reporter | ||
Comment 6•15 years ago
|
||
Dave, would it be possible to get this fixed for our next testday mid of June?
Assignee | ||
Comment 7•15 years ago
|
||
Standardises on locale.
Comment 8•15 years ago
|
||
Comment on attachment 449293 [details] [diff] [review]
patch rev 1
I assume we still want to keep it exposed to the user as "Languages", rather than "Locales".
Attachment #449293 -
Flags: review?(bmcbride) → review+
Assignee | ||
Comment 9•15 years ago
|
||
(In reply to comment #8)
> (From update of attachment 449293 [details] [diff] [review])
> I assume we still want to keep it exposed to the user as "Languages", rather
> than "Locales".
Up to Boriss really, and covered by bug 565300, but as Robert says we've been using locale for a long time internally so I think it makes sense to continue to do so.
Comment 10•15 years ago
|
||
My personal take on the naming - the correct technical term is 'locale', and IMHO, we should use that in the code. "Language" should be close enough for the UI, but a localization note on the somewhat ambiguous use would be good. I'll watch bug 565300, too
Assignee | ||
Comment 11•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Flags: in-testsuite-
Flags: in-litmus?
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.3a5
Comment 12•15 years ago
|
||
The patch that landed broke some things causing there to still be no visible entry for language packs:
- language category is never shown even if a language pack is installed
- localized header text of language category is no longer hooked up correctly (looks for "header-locale" instead of "header-language")
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Updated•15 years ago
|
Status: REOPENED → ASSIGNED
Comment 13•15 years ago
|
||
This is a very quick fix for both of the points I mentioned in the previous comment. The fix for the second problem is really just a band-aid for a larger problem: the Add-ons Managers uses "language" through-out the code (theme, localization, etc.). As Axel said, we should probably change the code to use "locale" to avoid stuff like this.
Attachment #450251 -
Flags: review?
Reporter | ||
Updated•15 years ago
|
Attachment #450251 -
Flags: review? → review?(dtownsend)
Assignee | ||
Comment 14•15 years ago
|
||
Comment on attachment 450251 [details] [diff] [review]
Second Patch
Thanks for catching this Ben, however rather than working out headerName let's just rename the string in the localization properties file for clarity.
Attachment #450251 -
Flags: review?(dtownsend) → review-
Comment 15•15 years ago
|
||
Comment on attachment 450251 [details] [diff] [review]
Second Patch
Looks like this patch should also fix bug 571200.
Comment 16•15 years ago
|
||
Also fixes Bug 571200.
Attachment #450251 -
Attachment is obsolete: true
Attachment #450514 -
Flags: review?(dtownsend)
Assignee | ||
Updated•15 years ago
|
Attachment #450514 -
Flags: review?(dtownsend) → review+
Assignee | ||
Comment 17•15 years ago
|
||
Comment on attachment 450514 [details] [diff] [review]
Second Patch v2
Great, thanks
Assignee | ||
Comment 18•15 years ago
|
||
Landed the follow-up as http://hg.mozilla.org/mozilla-central/rev/63f5ac31b8c4
Status: ASSIGNED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 19•15 years ago
|
||
Too late for a5. Moving TM to 1.9.3 until we have an own entry for beta1.
Verified fixed with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a6pre) Gecko/20100610 Minefield/3.7a6pre
Status: RESOLVED → VERIFIED
Target Milestone: mozilla1.9.3a5 → mozilla1.9.3
Reporter | ||
Comment 20•15 years ago
|
||
Given the discussion with Blair for an automated test for bug 553483 we should probably also mark this for in-testsuite inclusion. It would simply be a part of the test for bug 553483. Beside those tests we will also have a manual test which will probably become an FFT test.
Flags: in-testsuite- → in-testsuite?
Comment 21•15 years ago
|
||
Changing summary to reflect what was really going on.
Summary: Language packs cannot be installed → Language packs do not show up as installed
Reporter | ||
Updated•15 years ago
|
Target Milestone: mozilla1.9.3 → mozilla1.9.3a6
Updated•14 years ago
|
Flags: in-litmus? → in-litmus?(vlad.maniac)
Reporter | ||
Comment 22•14 years ago
|
||
Manual test covered by:
https://litmus.mozilla.org/show_test.cgi?id=15220
So the request for an automated test should be declined?
Flags: in-litmus?(vlad.maniac) → in-litmus+
Assignee | ||
Comment 23•14 years ago
|
||
Tests were added as a part of bug 572561
Flags: in-testsuite? → in-testsuite+
Reporter | ||
Comment 24•14 years ago
|
||
(In reply to comment #23)
> Tests were added as a part of bug 572561
Would that make the Litmus test obsolete? If yes, I would favor to remove it.
Assignee | ||
Comment 25•14 years ago
|
||
(In reply to comment #24)
> (In reply to comment #23)
> > Tests were added as a part of bug 572561
>
> Would that make the Litmus test obsolete? If yes, I would favor to remove it.
Yes, I would agree
Reporter | ||
Comment 26•14 years ago
|
||
Litmus test has been disabled. I think it's the right decision because finding the corresponding language pack will always be hard and error prone.
Flags: in-litmus+ → in-litmus-
You need to log in
before you can comment on or make changes to this bug.
Description
•