Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
[Marketplace] Important L10n updates
32 views
Skip to first unread message
Wil Clouser
Apr 30, 2013, 5:01:41 PM4/30/13
to dev-l1...@lists.mozilla.org, Milos Dinic, Axel Hecht
Hi Localizers,
As discussed for years, the Marketplace developers are working on
breaking up the gigantic .po files we have today into smaller chunks.
The first two chunks are available today in the following locations:
> 1) Our payments system. This is what the user will see when they
> purchase an app: https://github.com/mozilla/webpay/tree/master/locale
> 2) Our Marketplace consumer pages. This is the new front end for the
> marketplace: https://github.com/mozilla/fireplace/tree/master/locale
#1 will be difficult to test, I think, because it involves spending
money. If I can help with any of this let me know, otherwise use your
intuition.
#2 These are the main marketplace pages (home, detail, reviews, etc).
These are only for consumers, no admin pages, no reviewer tools. These
are also not live yet - we're working on getting them on marketplace-dev
shortly but for now we still have the old pages there. Some of these
strings may be dupes of the current .po files. While the current pages
are still existing we'll need the strings in both places, but the plan
is to replace the current pages with the new ones as soon as we can so
these new .po files will be where we localize these pages in the future.
I was hoping to announce the ability to localize these pages through
Verbatim, however, Verbatim's git support is still being deployed and I
didn't want to delay this email further. So, we're working on getting
Verbatim talking to git. In the mean time, these strings are not
available in Verbatim. There are some options to localize:
1) Ideally, if you are familiar with github, you can fork our
repository, make changes, and send a pull request. This will be easy
for us to pull in and will give you direct credit for the localizations.
Don't worry if none of that made sense, keep reading. :)
2) If you're used to SVN, github does support SVN
(https://github.com/blog/1178-collaborating-on-github-with-subversion).
I haven't used it and couldn't offer much help I think, but if you're
comfortable with SVN that is an option.
3) You can email me .po files. Not a very scalable or timely option but
I'll do what I can.
4) You can wait for Verbatim. If Verbatim is critical for your work
flow, this option is here.
We will try to get this in Verbatim as fast as possible, but I wanted to
let you know about the new strings and where they are located. Let me
know if you have questions.
As always, thanks for your help.
Wil
As discussed for years, the Marketplace developers are working on
breaking up the gigantic .po files we have today into smaller chunks.
The first two chunks are available today in the following locations:
> 1) Our payments system. This is what the user will see when they
> purchase an app: https://github.com/mozilla/webpay/tree/master/locale
> 2) Our Marketplace consumer pages. This is the new front end for the
> marketplace: https://github.com/mozilla/fireplace/tree/master/locale
#1 will be difficult to test, I think, because it involves spending
money. If I can help with any of this let me know, otherwise use your
intuition.
#2 These are the main marketplace pages (home, detail, reviews, etc).
These are only for consumers, no admin pages, no reviewer tools. These
are also not live yet - we're working on getting them on marketplace-dev
shortly but for now we still have the old pages there. Some of these
strings may be dupes of the current .po files. While the current pages
are still existing we'll need the strings in both places, but the plan
is to replace the current pages with the new ones as soon as we can so
these new .po files will be where we localize these pages in the future.
I was hoping to announce the ability to localize these pages through
Verbatim, however, Verbatim's git support is still being deployed and I
didn't want to delay this email further. So, we're working on getting
Verbatim talking to git. In the mean time, these strings are not
available in Verbatim. There are some options to localize:
1) Ideally, if you are familiar with github, you can fork our
repository, make changes, and send a pull request. This will be easy
for us to pull in and will give you direct credit for the localizations.
Don't worry if none of that made sense, keep reading. :)
2) If you're used to SVN, github does support SVN
(https://github.com/blog/1178-collaborating-on-github-with-subversion).
I haven't used it and couldn't offer much help I think, but if you're
comfortable with SVN that is an option.
3) You can email me .po files. Not a very scalable or timely option but
I'll do what I can.
4) You can wait for Verbatim. If Verbatim is critical for your work
flow, this option is here.
We will try to get this in Verbatim as fast as possible, but I wanted to
let you know about the new strings and where they are located. Let me
know if you have questions.
As always, thanks for your help.
Wil
gialloporpora
May 3, 2013, 9:22:17 AM5/3/13
to
Risposta al messaggio di Wil Clouser :
> > 2) Our Marketplace consumer pages. This is the new front end for the
> > marketplace:https://github.com/mozilla/fireplace/tree/master/locale
O, I have forked the repository.
Despite of 1, I don't see a it/ subdirectory.
I must create it/LC_messages/messages.po using the en-US po file. Is it
correct?
> #1 will be difficult to test, I think, because it involves spending
> money. If I can help with any of this let me know, otherwise use your immagination
I have only a question, these strings:
active
disactive
revoked
what is the subject? I think payment, is it true?
JWT means an JWT token?
http://self-issued.info/docs/draft-ietf-oauth-json-web-token.html
> > 2) Our Marketplace consumer pages. This is the new front end for the
> > marketplace:https://github.com/mozilla/fireplace/tree/master/locale
Despite of 1, I don't see a it/ subdirectory.
I must create it/LC_messages/messages.po using the en-US po file. Is it
correct?
> #1 will be difficult to test, I think, because it involves spending
I have only a question, these strings:
active
disactive
revoked
what is the subject? I think payment, is it true?
JWT means an JWT token?
http://self-issued.info/docs/draft-ietf-oauth-json-web-token.html
Wil Clouser
May 3, 2013, 11:23:31 AM5/3/13
to dev-l1...@lists.mozilla.org
On 05/03/2013 06:22 AM, gialloporpora wrote:
> Risposta al messaggio di Wil Clouser :
>
>> > 2) Our Marketplace consumer pages. This is the new front end for the
>> > marketplace:https://github.com/mozilla/fireplace/tree/master/locale
>
>
> O, I have forked the repository.
> Despite of 1, I don't see a it/ subdirectory.
> I must create it/LC_messages/messages.po using the en-US po file. Is it
> correct?
Yes, that would be best. Don't forget to adjust the plural-forms in the
> Risposta al messaggio di Wil Clouser :
>
>> > 2) Our Marketplace consumer pages. This is the new front end for the
>> > marketplace:https://github.com/mozilla/fireplace/tree/master/locale
>
>
> O, I have forked the repository.
> Despite of 1, I don't see a it/ subdirectory.
> I must create it/LC_messages/messages.po using the en-US po file. Is it
> correct?
.po header. If you need help with any of that I can help.
>> #1 will be difficult to test, I think, because it involves spending
>> money. If I can help with any of this let me know, otherwise use
>> your immagination
>
> I have only a question, these strings:
> active
> disactive
> revoked
>
> what is the subject? I think payment, is it true?
order to use payments a developer gets a key and can use it in their
apps. It can either be active or inactive, or, if they lose it and it
gets published, they can mark it as revoked.
Yes
Wil
gialloporpora
May 3, 2013, 11:35:00 AM5/3/13
to
Risposta al messaggio di Wil Clouser :
> These three words are specifically talking about a key for an app. In
> order to use payments a developer gets a key and can use it in their
> apps. It can either be active or inactive, or, if they lose it and it
> gets published, they can mark it as revoked
Ok, thanks again Will. Now I'll fix my translation.
> order to use payments a developer gets a key and can use it in their
> apps. It can either be active or inactive, or, if they lose it and it
> gets published, they can mark it as revoked
gialloporpora
May 4, 2013, 10:33:43 AM5/4/13
to
Risposta al messaggio di Wil Clouser :
> Yes, that would be best. Don't forget to adjust the plural-forms in the
> .po header. If you need help with any of that I can help.
i have asked to @flod that have said me that we have the same plural
> .po header. If you need help with any of that I can help.
form of english.
The pull request are here:
https://github.com/mozilla/webpay/pull/106
https://github.com/mozilla/fireplace/pull/95
https://github.com/mozilla/webpay/pull/106
i hope it works, it's the first time that I make a pull request on Github.
Sandro
Wil Clouser
May 5, 2013, 10:29:51 PM5/5/13
to dev-l1...@lists.mozilla.org
Wil
Julen Ruiz Aizpuru
May 6, 2013, 3:21:56 AM5/6/13
to Mozilla projects web content localization
Wil,
ar., 2013.eko apiren 30a 23:01(e)an, Wil Clouser(e)k idatzi zuen:
We have a person interested in working on this, but obviously she'll
need a way to see the results in order to test the work (and to keep
herself motivated) � any ETA on getting marketplace-dev updated from there?
I can point her to the old files, of course, but it's a mess and
difficult for someone who's trying to get involved for the first time.
I know it's not easy decoupling a large app, so a big thanks goes to the
team behind the great work on this.
Julen.
ar., 2013.eko apiren 30a 23:01(e)an, Wil Clouser(e)k idatzi zuen:
> Hi Localizers,
>
> As discussed for years, the Marketplace developers are working on
> breaking up the gigantic .po files we have today into smaller chunks.
> The first two chunks are available today in the following locations:
>
> > 1) Our payments system. This is what the user will see when they
> > purchase an app: https://github.com/mozilla/webpay/tree/master/locale
>
>
> As discussed for years, the Marketplace developers are working on
> breaking up the gigantic .po files we have today into smaller chunks.
> The first two chunks are available today in the following locations:
>
> > 1) Our payments system. This is what the user will see when they
> > purchase an app: https://github.com/mozilla/webpay/tree/master/locale
>
> > 2) Our Marketplace consumer pages. This is the new front end for the
> > marketplace: https://github.com/mozilla/fireplace/tree/master/locale
>
> > marketplace: https://github.com/mozilla/fireplace/tree/master/locale
>
> #1 will be difficult to test, I think, because it involves spending
> money. If I can help with any of this let me know, otherwise use your
> money. If I can help with any of this let me know, otherwise use your
> intuition.
>
> #2 These are the main marketplace pages (home, detail, reviews, etc).
> These are only for consumers, no admin pages, no reviewer tools. These
> are also not live yet - we're working on getting them on marketplace-dev
> shortly but for now we still have the old pages there. Some of these
> strings may be dupes of the current .po files. While the current pages
> are still existing we'll need the strings in both places, but the plan
> is to replace the current pages with the new ones as soon as we can so
> these new .po files will be where we localize these pages in the future.
This is awesome news :)
>
> #2 These are the main marketplace pages (home, detail, reviews, etc).
> These are only for consumers, no admin pages, no reviewer tools. These
> are also not live yet - we're working on getting them on marketplace-dev
> shortly but for now we still have the old pages there. Some of these
> strings may be dupes of the current .po files. While the current pages
> are still existing we'll need the strings in both places, but the plan
> is to replace the current pages with the new ones as soon as we can so
> these new .po files will be where we localize these pages in the future.
We have a person interested in working on this, but obviously she'll
need a way to see the results in order to test the work (and to keep
herself motivated) � any ETA on getting marketplace-dev updated from there?
I can point her to the old files, of course, but it's a mess and
difficult for someone who's trying to get involved for the first time.
I know it's not easy decoupling a large app, so a big thanks goes to the
team behind the great work on this.
Julen.
Wil Clouser
May 6, 2013, 12:15:33 PM5/6/13
to dev-l1...@lists.mozilla.org
We've got the code deployed on https://marketplace-altdev.allizom.org/
and I hope to see it on marketplace-dev.allizom.org soon. The front end
code should update automatically and you'll be able to see your changes.
The webpay/payments code needs to be compiled to .mo so if you don't
include that in your pull request it'll have to be done later and I'm
not sure if those projects auto-compile yet.
Still working on it, once the new design is on the regular dev site
(marketplace-dev.allizom.org) it'll be more stable and have a lot more
testing done.
Cheers,
Wil
Julen Ruiz Aizpuru
Jun 23, 2013, 6:48:10 AM6/23/13
to Mozilla projects web content localization
al., 2013.eko mairen 06a 18:15(e)an, Wil Clouser(e)k idatzi zuen:
the results live but it seems that l10n is broken in the Fireplace —
I'm not able to switch to any language neither in both of the mentioned
sites nor in the production site that is live at firefox.com.
I even built the Fireplace and the translations (`node damper.js
--compile` and `make langpacks`) and tried it locally, but no luck so far.
OTOH, according to the `hearth/media/js/l10n.js` source file[1], the
`?locale=<code>` query string is only honored when AMD's `define()` is
not available, otherwise the built langpacks are used. I'm not sure
what's the purpose of this differentiation, or in which context
`define()` is not available.
So, mind clarifying what's the status l10n in the Marketplace? How can
we test localizations?
TIA,
Julen.
[1] https://github.com/mozilla/fireplace/blob/master/hearth/media/js/l10n.js
>
> We've got the code deployed on https://marketplace-altdev.allizom.org/
> and I hope to see it on marketplace-dev.allizom.org soon. The front end
> code should update automatically and you'll be able to see your changes.
> The webpay/payments code needs to be compiled to .mo so if you don't
> include that in your pull request it'll have to be done later and I'm
> not sure if those projects auto-compile yet.
>
> Still working on it, once the new design is on the regular dev site
> (marketplace-dev.allizom.org) it'll be more stable and have a lot more
> testing done.
I sent my translations the other day through a PR and I wanted to see
> We've got the code deployed on https://marketplace-altdev.allizom.org/
> and I hope to see it on marketplace-dev.allizom.org soon. The front end
> code should update automatically and you'll be able to see your changes.
> The webpay/payments code needs to be compiled to .mo so if you don't
> include that in your pull request it'll have to be done later and I'm
> not sure if those projects auto-compile yet.
>
> Still working on it, once the new design is on the regular dev site
> (marketplace-dev.allizom.org) it'll be more stable and have a lot more
> testing done.
the results live but it seems that l10n is broken in the Fireplace —
I'm not able to switch to any language neither in both of the mentioned
sites nor in the production site that is live at firefox.com.
I even built the Fireplace and the translations (`node damper.js
--compile` and `make langpacks`) and tried it locally, but no luck so far.
OTOH, according to the `hearth/media/js/l10n.js` source file[1], the
`?locale=<code>` query string is only honored when AMD's `define()` is
not available, otherwise the built langpacks are used. I'm not sure
what's the purpose of this differentiation, or in which context
`define()` is not available.
So, mind clarifying what's the status l10n in the Marketplace? How can
we test localizations?
TIA,
Julen.
[1] https://github.com/mozilla/fireplace/blob/master/hearth/media/js/l10n.js
Wil Clouser
Jun 23, 2013, 3:45:03 PM6/23/13
to dev-l1...@lists.mozilla.org
Localizations are available on marketplace-dev.allizom.org shortly after
you commit them and on marketplace.firefox.com once a week on Thursday
afternoons (PST). Languages are chosen based on your accept-lang
headers. I'm not sure I answered your question - did that help?
Thanks,
Wil
Julen Ruiz Aizpuru
Jun 23, 2013, 5:27:11 PM6/23/13
to Mozilla projects web content localization
Wil,
>
> Localizations are available on marketplace-dev.allizom.org shortly after
you commit them and on marketplace.firefox.com once a week on Thursday
afternoons (PST). Languages are chosen based on your accept-lang headers.
I'm not sure I answered your question - did that help?
Not really, that doesn't work on my end. I tried both in desktop and
tablet, changed accept-languages settings to some other major languages but
still everything gets displayed in English.
At this point I'm not sure if it's me or something else is broken.
Julen.
>
> Localizations are available on marketplace-dev.allizom.org shortly after
you commit them and on marketplace.firefox.com once a week on Thursday
afternoons (PST). Languages are chosen based on your accept-lang headers.
I'm not sure I answered your question - did that help?
tablet, changed accept-languages settings to some other major languages but
still everything gets displayed in English.
At this point I'm not sure if it's me or something else is broken.
Julen.
Sasa Tekovic
Jun 23, 2013, 5:29:47 PM6/23/13
to Mozilla projects web content localization
On Sun, Jun 23, 2013 at 11:27 PM, Julen Ruiz Aizpuru <jul...@gmail.com> wrote:
> Not really, that doesn't work on my end. I tried both in desktop and
> tablet, changed accept-languages settings to some other major languages but
> still everything gets displayed in English.
>
> At this point I'm not sure if it's me or something else is broken.
>
> Julen.
The same is with Croatian (hr).
> Not really, that doesn't work on my end. I tried both in desktop and
> tablet, changed accept-languages settings to some other major languages but
> still everything gets displayed in English.
>
> At this point I'm not sure if it's me or something else is broken.
>
> Julen.
https://marketplace-dev.allizom.org/?lang=hr is still displayed in
English.
Cheers!
--
Sasa
Wil Clouser
Jun 23, 2013, 6:17:55 PM6/23/13
to Mozilla projects web content localization, Sasa Tekovic
https://github.com/mozilla/zamboni/blob/1f3a179bf59e0ad27dae162203f6f486fe25a008/mkt/settings.py#L236
. If Croatian is at 100% I can add it to the list soon but I'm in an
airport right now so I'll have to do it after I land.
Wil
Sasa Tekovic
Jun 24, 2013, 5:37:05 AM6/24/13
to Wil Clouser, Mozilla projects web content localization
On Mon, Jun 24, 2013 at 12:17 AM, Wil Clouser <wclo...@mozilla.com> wrote:
> The full list of locales is not available on the Marketplace, see
> https://github.com/mozilla/zamboni/blob/1f3a179bf59e0ad27dae162203f6f486fe25a008/mkt/settings.py#L236
> . If Croatian is at 100% I can add it to the list soon but I'm in an
> airport right now so I'll have to do it after I land.
>
> Wil
Hi,
> The full list of locales is not available on the Marketplace, see
> https://github.com/mozilla/zamboni/blob/1f3a179bf59e0ad27dae162203f6f486fe25a008/mkt/settings.py#L236
> . If Croatian is at 100% I can add it to the list soon but I'm in an
> airport right now so I'll have to do it after I land.
>
> Wil
yes, Croatian translation is complete.
Thanks!
--
Sasa
Mark Heijl
Jun 24, 2013, 5:41:56 AM6/24/13
to Mozilla projects web content localization, Sasa Tekovic
Why is that? I am pretty sure the Dutch locale (nl) is well maintained and
is usually at 100% for all projects in Verbatim, and has been so for quite
a while now, and this includes the AMO/Marketplace project. I would expect
a locale to be pushed to active once the completeness has reached 100% at
least once. Perhaps it can drop off again if completeness falls below a
certain percentage.
Mark
> On 6/23/13 2:29 PM, Sasa Tekovic wrote:
>> On Sun, Jun 23, 2013 at 11:27 PM, Julen Ruiz Aizpuru <jul...@gmail.com>
>> wrote:
>>> Not really, that doesn't work on my end. I tried both in desktop and
>>> tablet, changed accept-languages settings to some other major languages
>>> but
>>> still everything gets displayed in English.
>>>
>>> At this point I'm not sure if it's me or something else is broken.
>>>
>>> Julen.
>>
>> The same is with Croatian (hr).
>> https://marketplace-dev.allizom.org/?lang=hr is still displayed in
>> English.
>>
>
> dev-l10n-web mailing list
> dev-l1...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n-web
>
is usually at 100% for all projects in Verbatim, and has been so for quite
a while now, and this includes the AMO/Marketplace project. I would expect
a locale to be pushed to active once the completeness has reached 100% at
least once. Perhaps it can drop off again if completeness falls below a
certain percentage.
Mark
> On 6/23/13 2:29 PM, Sasa Tekovic wrote:
>> On Sun, Jun 23, 2013 at 11:27 PM, Julen Ruiz Aizpuru <jul...@gmail.com>
>> wrote:
>>> Not really, that doesn't work on my end. I tried both in desktop and
>>> tablet, changed accept-languages settings to some other major languages
>>> but
>>> still everything gets displayed in English.
>>>
>>> At this point I'm not sure if it's me or something else is broken.
>>>
>>> Julen.
>>
>> The same is with Croatian (hr).
>> https://marketplace-dev.allizom.org/?lang=hr is still displayed in
>> English.
>>
>
> The full list of locales is not available on the Marketplace, see
> https://github.com/mozilla/zamboni/blob/1f3a179bf59e0ad27dae162203f6f486fe25a008/mkt/settings.py#L236
> . If Croatian is at 100% I can add it to the list soon but I'm in an
> airport right now so I'll have to do it after I land.
>
> Wil
> _______________________________________________
> https://github.com/mozilla/zamboni/blob/1f3a179bf59e0ad27dae162203f6f486fe25a008/mkt/settings.py#L236
> . If Croatian is at 100% I can add it to the list soon but I'm in an
> airport right now so I'll have to do it after I land.
>
> Wil
> dev-l10n-web mailing list
> dev-l1...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n-web
>
Kohei Yoshino
Jun 26, 2013, 3:26:34 AM6/26/13
to Mozilla projects web content localization
I have translated the Marketplace into Japanese a few days ago.
https://github.com/mozilla/fireplace/pull/196/files
But I also had to update l10n.js to reflect our localization to the dev site.
https://github.com/mozilla/fireplace/pull/197/files
https://marketplace-dev.allizom.org/?lang=ja
Hope this helps,
-Kohei
https://github.com/mozilla/fireplace/pull/196/files
But I also had to update l10n.js to reflect our localization to the dev site.
https://github.com/mozilla/fireplace/pull/197/files
https://marketplace-dev.allizom.org/?lang=ja
Hope this helps,
-Kohei
0 new messages