Re: Some open translations for Firefox Home
dynamis
BTW, I have a question about VCS usage.
In Firefox Input l10n project, I was requested to commit to VCS by ourselves.
But in this (Firefox Home l10n) project, we have not required to commit to VCS.
I believe you (Ragavan?) always commit to svn from Verbatim for all locales
before you build new version.
We localizer should not use "commit to VCS"?
Or we can use it whenever we want backup WIP l10n snapshot in the svn?
Is there any rule or guide to use "commit to VCS" (and "update from VCS")?
# rules are different for each project? no common rules for Verbatim l10n?
Same question for "update the files from templates". When should we use it?
Thanks.
Stefan Arentz wrote:
> Hi Everybody,
>
> Maybe you remember that in December I asked you all to translate a couple of strings for Firefox Home outside of Verbatim because we were having some problems with the system.
>
> Those problems have now been resolved and so I have updated the templates on Verbatim.
>
> Would you all mind taking a look at the LC_MESSAGES/Localizable.strings.po strings again?
>
> Specifically for the following three strings:
>
> "Passcode"
> "Not Now"
> "Due to a recent update, you need to log in to Firefox Home again"
>
> (They are all at the very end, page 7, of the file)
>
> I have added all the translations that you previously emailed me as suggestions. So if those are correct you can simply confirm them. If they are not then please correct them.
>
> For some languages the above are completely missing.
>
> We would like to get this done for the next Firefox Home release, which will be 1.1.1. Not sure when the ETA is but I think having this done next week would be awesome.
>
> Thanks!
>
> S.
>
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>
Stefan Arentz
On 2011-01-28, at 12:53 AM, dynamis wrote:
> ja locale updated. ;)
Thank you very much.
> BTW, I have a question about VCS usage.
>
> In Firefox Input l10n project, I was requested to commit to VCS by ourselves.
> But in this (Firefox Home l10n) project, we have not required to commit to VCS.
> I believe you (Ragavan?) always commit to svn from Verbatim for all locales
> before you build new version.
>
> We localizer should not use "commit to VCS"?
> Or we can use it whenever we want backup WIP l10n snapshot in the svn?
>
> Is there any rule or guide to use "commit to VCS" (and "update from VCS")?
> # rules are different for each project? no common rules for Verbatim l10n?
Here is how I deal with this:
* I make changes to files in the FxHome repository and commit those.
* When those changes involve Verbatim template files then I upload those to Verbatim and reload the files for all languages.
* I then ask you guys to go to Verbatim to translate the strings.
* When the translations are complete in Verbatim, I run a script on my workstation that grabs all localized .po files from Verbatim and converts them to .strings file for the FxHome project.
* I then commit those updated .strings files to the FxHome repository and build the app
So you guys only have to focus on translating on Verbatim and I take care of keeping both Verbatim and the App file in sync.
> Same question for "update the files from templates". When should we use it?
Probably never needed because when I make changes to the template files I generally just go through every language and hit the 'update files' button to make them match with the templates.
S.
smo
I am involved in other Verbatim-based projects since some time. It is
the first ever time I see a person responsible for a project set down
traffic rules. Next to kudos for Stefan, two observations:
i. that this kind of rules need to be set down, shows there's an
inherent problem in the way this pipeline is supposed to work. Its
like building up a yet-another RCS system and asking users not to
commit on Fridays.Plus avoid using merge.
ii. that this kind of rules have not been declared elsewhere (and
nobody seems to care) may end up in a lot of unintended and costly
branches. It already did in my case to a tune of 8000 extra words to
be localized.
Caveat localisator
regards
smo
Stefan Arentz
On 2011-01-29, at 2:35 PM, smo wrote:
...
> I am involved in other Verbatim-based projects since some time. It is
> the first ever time I see a person responsible for a project set down
> traffic rules. Next to kudos for Stefan, two observations:
> i. that this kind of rules need to be set down, shows there's an
> inherent problem in the way this pipeline is supposed to work. Its
> like building up a yet-another RCS system and asking users not to
> commit on Fridays.Plus avoid using merge.
I wish Verbatim had a storage backend on top of Mercurial. Then I could simply tag specific releases and more easily follow changes.
Or even keep all the string and template files in the main firefox repository and 'mount' that directory in Verbatim so that people can work on it with the fancy interface.
S.