L10N Tracking for Firefox Start Page

RESOLVED FIXED

Status

Mozilla Localizations
Other
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: ckoehler, Assigned: pascalc)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Thanks for filing this, Christie. We discussed some of this earlier with Pascal.

Per Pascal's request, we can use the .lang file format. Where should these files live? In a subdirectory of: http://svn.mozilla.org/projects/l10n-misc/trunk/ ?

Are we supposed to extract the strings from the site when it's done? Or are there any translation files from the original Fx3.6 site that were already used?
(Reporter)

Comment 2

6 years ago
(In reply to Fred Wenzel [:wenzel] from comment #1)
> Are we supposed to extract the strings from the site when it's done? Or are
> there any translation files from the original Fx3.6 site that were already
> used?

It's my guess that Google handled that, but I am finding out. Will post an update here as soon as I know.

Comment 3

6 years ago
Unassigning, I won't be the guy driving this on our side.
Assignee: l10n → nobody
(Assignee)

Comment 4

6 years ago
(In reply to Fred Wenzel [:wenzel] from comment #1)
> Thanks for filing this, Christie. We discussed some of this earlier with
> Pascal.
> 
> Per Pascal's request, we can use the .lang file format. Where should these
> files live? In a subdirectory of:
> http://svn.mozilla.org/projects/l10n-misc/trunk/ ?

We will put them there:
viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/locales/

This way, localizers are automatically notified of the need to translate them though the web dashboard, also, this is the place where all Firefox web localizers do their in-product pages so we maximise the chances to reach out to the right localizerts for this task. we can call the file 36eol.lang for example
Assignee: nobody → pascalc
(Assignee)

Comment 5

6 years ago
(In reply to Christie Koehler [:ckoehler] from comment #2)
> (In reply to Fred Wenzel [:wenzel] from comment #1)
> > Are we supposed to extract the strings from the site when it's done? Or are
> > there any translation files from the original Fx3.6 site that were already
> > used?
> 
> It's my guess that Google handled that, but I am finding out. Will post an
> update here as soon as I know.

Yes Google handled that, the only text that was provided by Mozilla were the snippets that were displayed below the search box.

There were not many strings dislayed on the page though, maybe a dozen, we can just add them to the file we will ask localizers to translate.
(In reply to Pascal Chevrel:pascalc from comment #4)
> We will put them there:
> viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/locales/
> 
> This way, localizers are automatically notified of the need to translate
> them though the web dashboard, also, this is the place where all Firefox web
> localizers do their in-product pages so we maximise the chances to reach out
> to the right localizerts for this task. we can call the file 36eol.lang for
> example

I don't think that's a good idea, sorry. This page has nothing at all to do with mozilla.org. Co-mingling the two codebases is really bad for maintainability.
In r103729, I created: <https://svn.mozilla.org/projects/l10n-misc/trunk/fx36start/locale/>

I'll talk to jlongster to get the string extraction working so Jon can extract the strings that he uses.
(Assignee)

Comment 8

6 years ago
we can put them somewhere else, but I will need to (In reply to Fred Wenzel [:wenzel] from comment #6)
> (In reply to Pascal Chevrel:pascalc from comment #4)
> > We will put them there:
> > viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/locales/
> > 
> > This way, localizers are automatically notified of the need to translate
> > them though the web dashboard, also, this is the place where all Firefox web
> > localizers do their in-product pages so we maximise the chances to reach out
> > to the right localizerts for this task. we can call the file 36eol.lang for
> > example
> 
> I don't think that's a good idea, sorry. This page has nothing at all to do
> with mozilla.org. Co-mingling the two codebases is really bad for
> maintainability.

We can put them in the repo you created in comment 7 but note that it won't be tracked automatically on the webdashboard in the short term since it doesn't monitor several repos and I don't think I will have time adding this feature in April. Will that page have string changes after the launch ?
(In reply to Pascal Chevrel:pascalc from comment #8)
> Will that page have string changes after the launch ?

I don't think so, but I'll refer to ckoehler for this.
(Reporter)

Comment 10

6 years ago
(In reply to Pascal Chevrel:pascalc from comment #8)
> feature in April. Will that page have string changes after the launch ?

It depends. We have two versions of the start page. One is more urgent than the first and we'll want to default to that later on. If we can get both done before launch, then no string changes are planned.
All right here are some updates.

The page should be string-complete. Jon's code landed on master, and while I still expect changes to the code, I don't expect string changes. The "more urgent" strings referenced in comment 10 are already in there.

As far as locales go, I took the list you provided, removed the "ignore" ones and made a mapping for the fallback ones (the "at risk" ones commented out). Look at it here:
https://github.com/mozilla/fx36start/blob/master/settings.py#L19

That means, the at-risk ones are extracted like the other ones for now, if we decide to make them fallback languages, we enable the fallback and remove the .lang directory for those langs.

I extracted the strings, and committed them to SVN in r103749:
https://svn.mozilla.org/projects/l10n-misc/trunk/fx36start/locale/

Feel free to get those translated!
(Assignee)

Updated

6 years ago
Depends on: 742648
(Assignee)

Updated

6 years ago
Depends on: 743204
(Assignee)

Updated

6 years ago
Depends on: 743205
(Assignee)

Updated

6 years ago
Depends on: 743206
(Assignee)

Comment 13

6 years ago
Marking fixed, the couple of missing locales redirected to their fallback language is unlikely to be ever fixed since they are also missing in action on Firefox localization.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.