Closed Bug 1125898 Opened 10 years ago Closed 10 years ago

L10N for Mozorg /firefox/os redesign

Categories

(www.mozilla.org :: L10N, defect)

Product:
www.mozilla.org
Component:
L10N
Version:
Development/Staging
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: malexis, Assigned: flod)

References

Details

Attachments

(1 file)

FFxOS_ConsumerPage-Redesign-dev.png
655.53 KB, image/png
Details
Consumer page redesign Project Brief https://docs.google.com/a/mozilla.com/document/d/1O6UXNpirEDk2mYYlh8wKQz13FtnmDPtok3Df28wfotY/edit existing page https://www.mozilla.org/en-US/firefox/os/ Schedule https://app.smartsheet.com/b/publish?EQBCT=818173bf2daa4682bca75efdf3aa7f0c Pascal and Flod, please take a look at the schedule and I will set up some time to discuss this week. Hand-off to l10n: 2015-02-16 Go live: 2015-02-27
I can't really estimate the amount of text that will be added or changed based on the project brief, but the available time seems to be extremely short. It's 11 days, including only one week-end. Might be 10 days if the template is available late in US timezone, or there are other issues in the schedule. And lately we're getting complaints for the amount of content that localizers are asked to localize (this would be the 4th big request since the beginning of the year).
(In reply to Francesco Lodolo [:flod] from comment #1) > I can't really estimate the amount of text that will be added or changed > based on the project brief, but the available time seems to be extremely > short. > > It's 11 days, including only one week-end. Might be 10 days if the template > is available late in US timezone, or there are other issues in the schedule. > And lately we're getting complaints for the amount of content that > localizers are asked to localize (this would be the 4th big request since > the beginning of the year). Flod, I believe Jen mentioned in another bug that l10n isn't a blocker for launch, but something that can roll out when ready. We need the en-US page live on February 27 for MWC. I should have mentioned this in the original comment. Let's discuss Wednesday which locales we can feasibly get translated in time for the MWC launch date.
Hi Flod and Pascal- Just a heads up, in the top section of this page, we want to build the phone image using live text with the names of the 3 visible apps (Dialer, Messages, Marketplace) exported from the Fx OS string database in an attempt to make localization of this image easier (see attached image). I also wanted to let you know that :espressive (Schalk) will be coding this page for us since he has joined our team in the last couple of weeks :) Thx, Jen
Assignee: nobody → francesco.lodolo
Hi, any update on this one? We received strings in bug 1125900 (/partners), but I don't want to make multiple changes to .lang files unless this is going to be several days behind the schedule.
Flags: needinfo?(malexis)
(In reply to Francesco Lodolo [:flod] from comment #5) > Hi, any update on this one? We received strings in bug 1125900 (/partners), > but I don't want to make multiple changes to .lang files unless this is > going to be several days behind the schedule. Hi Flod- Mike is on PTO today. I understand that you and Schalk spoke in IRC and he's going to get it to you today. Thx, Jen
Hey all, I worked through all the content in the doc and have a couple of questions. 1) The doc does not specify any content for the in the news section so, is the text in Ty’s design the correct text to use i.e. In the news See all the press 2) For the need help section, the doc only shows: Firefox OS support Find My Device But in Ty’s design, there is also: For Developers Mozilla Developer Network Mozilla Appmaker Firefox OS device Where is Firefox OS available? Other Firefox OS versions For Partners Partnership opportunities Is the above additional links correct and should they be included? 3) For the links, the doc does not specify where exactly any of these should link
Flags: needinfo?(jbertsch)
Oh, then also, for the strings are we focusing on those for the 2.0 version or for all the versions we need to support? I am not sure where the differences are going to be exactly and whether we are going to have one template, with conditional content, or multiple templates. I am thinking the second, multiple templates, based on the discussion re: server side geo location and redirects.
(In reply to Schalk Neethling [:espressive] from comment #8) > Oh, then also, for the strings are we focusing on those for the 2.0 version > or for all the versions we need to support? I am not sure where the > differences are going to be exactly and whether we are going to have one > template, with conditional content, or multiple templates. > > I am thinking the second, multiple templates, based on the discussion re: > server side geo location and redirects. Hi Schalk- Those are the stings for v2.0. I'm hoping we can just hide/delete strings and not add new ones to support the other versions, that shouldn't impact getting the 2.0 page out the door for March 1. And yes, I'm hoping we can do it with the server side geolocation and redirects. Thx, Jen
Flags: needinfo?(jbertsch)
Thanks, Schalk! Answers below: (In reply to Schalk Neethling [:espressive] from comment #7) > Hey all, > > I worked through all the content in the doc and have a couple of questions. > > 1) The doc does not specify any content for the in the news section so, is > the text in Ty’s design the correct text to use i.e. > > In the news > See all the press This content will come from the wordpress feed that Josh is working on here: https://bugzilla.mozilla.org/show_bug.cgi?id=1128587 List of locales where it will appear in comments 2 and 3. > > 2) For the need help section, the doc only shows: > > Firefox OS support > Find My Device > > But in Ty’s design, there is also: > > For Developers > > Mozilla Developer Network > Mozilla Appmaker > Firefox OS device > Where is Firefox OS available? > Other Firefox OS versions > > For Partners > > Partnership opportunities > > Is the above additional links correct and should they be included? Yes please. > > 3) For the links, the doc does not specify where exactly any of these should > link I'll file a new comment with the urls later today. We don't need the links for L10N to start.
https://bug1120700.bugzilla.mozilla.org/attachment.cgi?id=8559424 That document talks about "localized UI" for the main phone image. I honestly though we were going to create a base image and apply strings to it (I definitely remember talking about it). Isn't that the case? Because I'm starting to look at the code and I don't see anything like that, only an image with hard-coded English strings.
Flags: needinfo?(jbertsch)
One more question: should I look at this image? https://bug1125898.bugzilla.mozilla.org/attachment.cgi?id=8563718 Some remaining notes on the current template, assuming the image above is correct. Alternative text for icons: I think they should use the correct Gaia name (uppercase, and radiofm->FM Radio). There's no dialer, so I guess "Dialer" is OK. http://transvision.mozfr.org/?recherche=manifest.properties%3Aname&repo=gaia&sourcelocale=en-US&locale=en-US&search_type=entities Missing string in the template > Go to the Marketplace Doubts: > Smart Has Never Been So Simple Image and copy have different capitalization (sentence case). > Default apps may vary by region Image says "by manufacturer", copy says "region", I guess it's OK "by region". > See all the press Image: "See all press" > Firefox OS device Image: devices Since we're localizing the page, should we add also the string about non -2.0 OS (even if currently unused)?
(In reply to Francesco Lodolo [:flod] from comment #12) > One more question: should I look at this image? > https://bug1125898.bugzilla.mozilla.org/attachment.cgi?id=8563718 > Yes
(In reply to Francesco Lodolo [:flod] from comment #12) > Alternative text for icons: I think they should use the correct Gaia name > (uppercase, and radiofm->FM Radio). There's no dialer, so I guess "Dialer" > is OK. > http://transvision.mozfr.org/?recherche=manifest. > properties%3Aname&repo=gaia&sourcelocale=en-US&locale=en- > US&search_type=entities > Let me change these. Missing string in the template > Go to the Marketplace This should not be missing, it is the link text for the button just below the Facebook, Youttube and Line icons.
(In reply to Schalk Neethling [:espressive] from comment #14) > This should not be missing, it is the link text for the button just below > the Facebook, Youttube and Line icons. Missing the wrapping https://github.com/mozilla/bedrock/blob/bug1120700-implement-fxos-consumer-page-redesign/bedrock/firefox/templates/firefox/os/index-new.html#L110
(In reply to Francesco Lodolo [:flod] from comment #11) > https://bug1120700.bugzilla.mozilla.org/attachment.cgi?id=8559424 > > That document talks about "localized UI" for the main phone image. I > honestly though we were going to create a base image and apply strings to it > (I definitely remember talking about it). Isn't that the case? Because I'm > starting to look at the code and I don't see anything like that, only an > image with hard-coded English strings. That was the plan. I'll chat today with Schalk about it.
Flags: needinfo?(jbertsch)
(In reply to Jennifer Bertsch [:jbertsch] from comment #16) > (In reply to Francesco Lodolo [:flod] from comment #11) > > https://bug1120700.bugzilla.mozilla.org/attachment.cgi?id=8559424 > > > > That document talks about "localized UI" for the main phone image. I > > honestly though we were going to create a base image and apply strings to it > > (I definitely remember talking about it). Isn't that the case? Because I'm > > starting to look at the code and I don't see anything like that, only an > > image with hard-coded English strings. > > That was the plan. I'll chat today with Schalk about it. I have spoken to Ty and he will provide me with the relevant images so we can do the icons with live text and not have it as a single image. On another topic. The hero space area is not useful a all to some folks using assistive technologies. One way to change this is to wrap the hero-section in a figure tag and then use a figcaption, accessibly hidden, to describe the interactions that are demonstrated by the animation. I know this will add overhead to the l10n effort though but, it is an important consideration to take into account. Thoughts?
Flags: needinfo?(jbertsch)
Flags: needinfo?(francesco.lodolo)
(In reply to Schalk Neethling [:espressive] from comment #17) > I have spoken to Ty and he will provide me with the relevant images so we > can do the icons with live text and not have it as a single image. Great. > On another topic. The hero space area is not useful a all to some folks > using assistive technologies. One way to change this is to wrap the > hero-section in a figure tag and then use a figcaption, accessibly hidden, > to describe the interactions that are demonstrated by the animation. A lot depends on the amount of text requested, and how long it takes to create it (e.g. I don't know how the animation works). Do you think there are chances to have all the strings in the template by tomorrow? I was really hoping to give locales at least a chance to work on this page before launch, but slipping into next week makes it almost impossible. P.S. I also need an answer for the strings in comment 12, image vs template vs copy
Flags: needinfo?(francesco.lodolo)
(In reply to Francesco Lodolo [:flod] from comment #18) > Do you think there are chances to have all the strings in the template by > tomorrow? I was really hoping to give locales at least a chance to work on > this page before launch, but slipping into next week makes it almost > impossible. I am guessing the live text that will go along with the icons is not a problem. I believe there was mention made that we can pull these from FirefoxOS (Gaia). In terms of other content, not sure what else is missing, or if there is anything that needs changed. I guess for the questions in comment 12, Jen is the best person to answer those questions.
(In reply to Schalk Neethling [:espressive] from comment #19) > I am guessing the live text that will go along with the icons is not a > problem. It's true that I'm going to import App names from Gaia to the .lang file, but I still need a template that makes sense to generate the correct lang file and import translations. For example, would we still need all those "XXX icon" labels? If we plan to add text for the animation, we need it before starting to localize the page.
(In reply to Francesco Lodolo [:flod] from comment #20) > (In reply to Schalk Neethling [:espressive] from comment #19) > > I am guessing the live text that will go along with the icons is not a > > problem. > > It's true that I'm going to import App names from Gaia to the .lang file, > but I still need a template that makes sense to generate the correct lang > file and import translations. For example, would we still need all those > "XXX icon" labels? I assume you mean the alt text, I changed those to just be app name so, Dialer, Video, Camera etc. and removed to appended icon text.
(In reply to Francesco Lodolo [:flod] from comment #20) > I assume you mean the alt text, I changed those to just be app name so, > Dialer, Video, Camera etc. and removed to appended icon text. Yes. Adding also that, having no idea of what the animation is supposed to do or show, I'd need in the template the full list of strings that will be displayed. Looking at the image, for example, there's the placeholder for the searchbar, and if possible the time (to simulate a localized time format).
(In reply to Francesco Lodolo [:flod] from comment #22) > (In reply to Francesco Lodolo [:flod] from comment #20) > > I assume you mean the alt text, I changed those to just be app name so, > > Dialer, Video, Camera etc. and removed to appended icon text. > > Yes. Adding also that, having no idea of what the animation is supposed to > do or show, I'd need in the template the full list of strings that will be > displayed. > > Looking at the image, for example, there's the placeholder for the > searchbar, and if possible the time (to simulate a localized time format). Yeah, I asked for the image to also not have the text filled into the search bar so, that will be live text. Did not think of the time though.
(In reply to Schalk Neethling [:espressive] from comment #17) > (In reply to Jennifer Bertsch [:jbertsch] from comment #16) > > (In reply to Francesco Lodolo [:flod] from comment #11) > > > https://bug1120700.bugzilla.mozilla.org/attachment.cgi?id=8559424 > > > > > > That document talks about "localized UI" for the main phone image. I > > > honestly though we were going to create a base image and apply strings to it > > > (I definitely remember talking about it). Isn't that the case? Because I'm > > > starting to look at the code and I don't see anything like that, only an > > > image with hard-coded English strings. > > > > That was the plan. I'll chat today with Schalk about it. > > I have spoken to Ty and he will provide me with the relevant images so we > can do the icons with live text and not have it as a single image. > > On another topic. The hero space area is not useful a all to some folks > using assistive technologies. One way to change this is to wrap the > hero-section in a figure tag and then use a figcaption, accessibly hidden, > to describe the interactions that are demonstrated by the animation. > > I know this will add overhead to the l10n effort though but, it is an > important consideration to take into account. Thoughts? Hi Schalk- Good catch on the accessibility issue. Could we fix that, and add the additional copy, post-launch in March? I know it is less than ideal, but it would decrease the risk to L10N for now. Thx, Jen
Flags: needinfo?(jbertsch)
(In reply to Jennifer Bertsch [:jbertsch] from comment #24) > (In reply to Schalk Neethling [:espressive] from comment #17) > > (In reply to Jennifer Bertsch [:jbertsch] from comment #16) > > > (In reply to Francesco Lodolo [:flod] from comment #11) > > > > https://bug1120700.bugzilla.mozilla.org/attachment.cgi?id=8559424 > > > > > > > > That document talks about "localized UI" for the main phone image. I > > > > honestly though we were going to create a base image and apply strings to it > > > > (I definitely remember talking about it). Isn't that the case? Because I'm > > > > starting to look at the code and I don't see anything like that, only an > > > > image with hard-coded English strings. > > > > > > That was the plan. I'll chat today with Schalk about it. > > > > I have spoken to Ty and he will provide me with the relevant images so we > > can do the icons with live text and not have it as a single image. > > > > On another topic. The hero space area is not useful a all to some folks > > using assistive technologies. One way to change this is to wrap the > > hero-section in a figure tag and then use a figcaption, accessibly hidden, > > to describe the interactions that are demonstrated by the animation. > > > > I know this will add overhead to the l10n effort though but, it is an > > important consideration to take into account. Thoughts? > > Hi Schalk- > > Good catch on the accessibility issue. Could we fix that, and add the > additional copy, post-launch in March? I know it is less than ideal, but it > would decrease the risk to L10N for now. > > Thx, > Jen Yeah, we are in a tight spot with that so, I am willing to bend ;) I will open a bug to add that in so we make sure we do not forget.
(In reply to Schalk Neethling [:espressive] from comment #25) > (In reply to Jennifer Bertsch [:jbertsch] from comment #24) > > (In reply to Schalk Neethling [:espressive] from comment #17) > > > (In reply to Jennifer Bertsch [:jbertsch] from comment #16) > > > > (In reply to Francesco Lodolo [:flod] from comment #11) > > > > > https://bug1120700.bugzilla.mozilla.org/attachment.cgi?id=8559424 > > > > > > > > > > That document talks about "localized UI" for the main phone image. I > > > > > honestly though we were going to create a base image and apply strings to it > > > > > (I definitely remember talking about it). Isn't that the case? Because I'm > > > > > starting to look at the code and I don't see anything like that, only an > > > > > image with hard-coded English strings. > > > > > > > > That was the plan. I'll chat today with Schalk about it. > > > > > > I have spoken to Ty and he will provide me with the relevant images so we > > > can do the icons with live text and not have it as a single image. > > > > > > On another topic. The hero space area is not useful a all to some folks > > > using assistive technologies. One way to change this is to wrap the > > > hero-section in a figure tag and then use a figcaption, accessibly hidden, > > > to describe the interactions that are demonstrated by the animation. > > > > > > I know this will add overhead to the l10n effort though but, it is an > > > important consideration to take into account. Thoughts? > > > > Hi Schalk- > > > > Good catch on the accessibility issue. Could we fix that, and add the > > additional copy, post-launch in March? I know it is less than ideal, but it > > would decrease the risk to L10N for now. > > > > Thx, > > Jen > > Yeah, we are in a tight spot with that so, I am willing to bend ;) I will > open a bug to add that in so we make sure we do not forget. Thanks, we can combine it with the work to support v1.1-1.4.
(In reply to Francesco Lodolo [:flod] from comment #12) > One more question: should I look at this image? > https://bug1125898.bugzilla.mozilla.org/attachment.cgi?id=8563718 > > Some remaining notes on the current template, assuming the image above is > correct. > > Alternative text for icons: I think they should use the correct Gaia name > (uppercase, and radiofm->FM Radio). There's no dialer, so I guess "Dialer" > is OK. > http://transvision.mozfr.org/?recherche=manifest. > properties%3Aname&repo=gaia&sourcelocale=en-US&locale=en- > US&search_type=entities > > Missing string in the template > > Go to the Marketplace > > Doubts: > > Smart Has Never Been So Simple > Image and copy have different capitalization (sentence case). Should be sentence case. > > > Default apps may vary by region > Image says "by manufacturer", copy says "region", I guess it's OK "by > region". Final language is: Pre-installed apps may vary by manufacturers and operators. > > > See all the press > Image: "See all press" Final copy: See more > > > Firefox OS device > Image: devices Final copy: devices > > Since we're localizing the page, should we add also the string about non > -2.0 OS (even if currently unused)?
All the above changes made, pushing to demo3
I've just committed the strings to SVN, and added a couple more that should be used in the animation (search bar placeholder, time). From this point we should try to push back string changes and deal with them after March 1st. I'm not sure we can have proper RTL support in the short time available. Dashboard to track localization https://l10n.mozilla-community.org/~pascalc/langchecker/?locale=all&website=0&file=firefox/os/index-new.lang
Flags: needinfo?(malexis)
One more issue: the redirect to the old template is not working properly when Bedrock is DEV=False mode We're using l10n_utils.template_is_active to check if the template is marked as active https://github.com/mozilla/bedrock/blob/1d3e943fe473a53de047aadac01a8e1cb0110b94/bedrock/firefox/views.py#L513 But this template includes /os/devices.lang and the active status is read from this file https://github.com/mozilla/bedrock/blob/master/lib/l10n_utils/gettext.py#L223-L233 Not completely sure how we can work around this. The only solution I can think of is to add a tag to the .lang file for the new template (e.g. consumer_update), and use check for this tag instead of the active status. Paul, any other idea?
Flags: needinfo?(pmac)
That would work. We'd just use lang_file_has_tag instead of template_is_active. You could even use lang_file_is_active if you only cared about a specific lang file's active state and didn't need to create a new tag name.
Flags: needinfo?(pmac)
(In reply to Paul McLanahan [:pmac] from comment #31) > You could even use lang_file_is_active if you only cared about a specific > lang file's active state and didn't need to create a new tag name. Right, this works perfectly. > if lang_file_is_active(new_home, locale):
Thanks, Flod. We can continue to show the old version of the page for locales that don't update (until they do), correct?
(In reply to Jennifer Bertsch [:jbertsch] from comment #33) > We can continue to show the old version of the page for locales that don't > update (until they do), correct? Exactly. The problem is that the current code doesn't work as expected (the page is displayed if /devices is enabled, which is the case for most locales).
I think I have another thing to add to the list of things to fix after March 1st: "Swipe between apps" is used both as a button and a title (Different contexts). That's forcing localizers to translate the 5 strings the same way (2 buttons + 3 titles). We can't for instance use "App swipping" as title and "Swippe between apps" as button. Maybe we could use a different capitalization in en-US so that we have 2 different strings? (We used to do that a couple times to fix similar issues)
Didn't notice the two string used in two different places. We could also some markup to the ones used for buttons. For sure there's an alignment issue with the 3 columns scroll/search/swipe https://www-demo3.allizom.org/it/firefox/os/ https://www-demo3.allizom.org/de/firefox/os/
Ah right, I forgot about the markup hack. Also, I could have missed the discussion about it (sorry if it's the case), but will the strings "Give these a try" and "Close demo" be removed? Because they are not being localized right now. Just trying to make sure we won't have to translate them at the very last minute :)
I have a doubt that the wireframe could be obsolete at this point, looking at https://bug1125898.bugzilla.mozilla.org/attachment.cgi?id=8563718
After discovering with Théo that clicking the image opens the animation (d'oh!), so far we found these issues with the strings: * missing "Give these a try", "Close this demo". We can probably fix the latter by replacing it with "Close" (available in main.lang) * reused "Swipe between apps"
(In reply to Francesco Lodolo [:flod] from comment #36) > Didn't notice the two string used in two different places. We could also > some markup to the ones used for buttons. > > For sure there's an alignment issue with the 3 columns scroll/search/swipe > https://www-demo3.allizom.org/it/firefox/os/ > https://www-demo3.allizom.org/de/firefox/os/ Added a fix for the layout problem.
(In reply to Francesco Lodolo [:flod] from comment #32) > (In reply to Paul McLanahan [:pmac] from comment #31) > > You could even use lang_file_is_active if you only cared about a specific > > lang file's active state and didn't need to create a new tag name. > > Right, this works perfectly. > > > if lang_file_is_active(new_home, locale): So it looks like I should switch to use lang_file_is_active correct?
Flags: needinfo?(francesco.lodolo)
(In reply to Schalk Neethling [:espressive] from comment #41) > So it looks like I should switch to use lang_file_is_active correct? Yes. About comment 39: * Can we have a separate string for the button label (we can also replace a space with  ), and use "Close" instead of "Close demo"? * Is the template missing other strings besides "Give these a try"?
Flags: needinfo?(francesco.lodolo)
(In reply to Francesco Lodolo [:flod] from comment #42) > (In reply to Schalk Neethling [:espressive] from comment #41) > > So it looks like I should switch to use lang_file_is_active correct? > Yes. Done > > About comment 39: > * Can we have a separate string for the button label (we can also replace a > space with  ), and use "Close" instead of "Close demo"? I changed this to just 'Close'. Is this the button label you are referring to? > * Is the template missing other strings besides "Give these a try"? I don't believe so :flod
(In reply to Schalk Neethling [:espressive] from comment #43) > > * Can we have a separate string for the button label (we can also replace a > > space with  ), and use "Close" instead of "Close demo"? > > I changed this to just 'Close'. Is this the button label you are referring > to? No. "Swipe between apps" is currently used both as a title and as a button. Since in our l10n system the English string is the ID, we can't have two different translations, so we need to differentiate them. One way to do it is to introduce some minor markup into one of the two strings. The alternative is to use a slightly different string for one of the two.
Found those links at the bottom of https://www-demo3.allizom.org/fr/firefox/os/ //www.mozilla.org/en-US/firefox/os/devices/ //www.mozilla.org/en-US/firefox/os/devices/tv/ Please never use "/en-US" in links, it will force redirect all users to English pages, even when localized pages are available ;)
(In reply to Théo Chevalier [:tchevalier] from comment #45) > Found those links at the bottom of > https://www-demo3.allizom.org/fr/firefox/os/ > //www.mozilla.org/en-US/firefox/os/devices/ > //www.mozilla.org/en-US/firefox/os/devices/tv/ > > Please never use "/en-US" in links, it will force redirect all users to > English pages, even when localized pages are available ;) Copy and pasted from a doc #fail :/
Broken link in "Mozilla AppMaker" https://webmaker.or/appmaker or(g)
(In reply to Francesco Lodolo [:flod] from comment #47) > Broken link in "Mozilla AppMaker" > https://webmaker.or/appmaker > > or(g) Good catch, fixed. Thx
Schalk are there any strings left to deliver to l10n or do they have everything they need?
Flags: needinfo?(schalk.neethling.bugs)
:flod would probably be the best person to answer this. With that said, for the current /os page I believe all strings are in. The strings needed for the app icons and the main phone are already used as alt text so, they already exist and were pulled from Gaia. There is continued work on the go now to support the other versions of the OS but, Alex is running with that. There may very well be additional strings that come to the fore there.
Flags: needinfo?(schalk.neethling.bugs)
(In reply to Schalk Neethling [:espressive] from comment #50) > :flod would probably be the best person to answer this. With that said, for > the current /os page I believe all strings are in. The strings needed for > the app icons and the main phone are already used as alt text so, they > already exist and were pulled from Gaia. I'm not aware of any missing string at this point. I pre-landed all the strings needed for a phone animation (app names, time format, search bar placeholder), so we're also covered if we go there.
I'd say we're good here. Page is live, and already had a small update. http://192.168.133.115/langchecker/?locale=all&website=0&file=firefox/os/index-new.lang
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: