Closed
Bug 897237
Opened 12 years ago
Closed 11 years ago
[B2G][l10n][Marketplace] [bg]: localization needed for multiple platforms
Categories
(Mozilla Localizations :: bg / Bulgarian, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: CocoMo, Assigned: chilyashev)
Details
Attachments
(1 file)
|
94.88 KB,
image/png
|
Details |
Hi Mihail,
I am opening this bug to track the progress of localization. Looks like P1 and P2 components are in good shape, there is still quite a bit of work to be done for p3 Zamboni. Please find the locations where you can find the untranslated strings.
* P1: Fireplace - frontend, and consumer pages: https://github.com/mozilla/fireplace/tree/master/locale
* P2: Webpay - payment system: https://github.com/mozilla/webpay/tree/master/locale
* P3: Zamboni - https://github.com/mozilla/zamboni/tree/master/locale.
For testing:
==========
* Overall test site: https://marketplace-dev.allizom.org/?lang=xx; for phones, change settings
* Webpay-paid apps: https://marketplace-dev.allizom.org/?lang=xx/search?q=pricepoint/
Thank you,
Peiying
| Reporter | ||
Updated•12 years ago
|
Assignee: ogi → chilyashev
| Assignee | ||
Comment 1•12 years ago
|
||
Hi Peiying,
I'm working on Zamboni and will send a pull request once it's done.
Should I comment here every time I send a pull request or just close the bug when I'm done with everything?
Status: NEW → ASSIGNED
| Reporter | ||
Comment 2•12 years ago
|
||
Please make a comment when you committed a file. This way the dev can include your submission to the build and you and QA can test it. Every Monday we have a push to the staging.
Could you work on Webpay? It has about 58 strings and finishing up Fireplace (a handful strings left to do). Zamboni has over 3000 strings left so it will take a while to get it done.
Thank you so much,
Peiying
| Assignee | ||
Comment 3•12 years ago
|
||
I sent a pull request for Webpay this morning and it's already merged.
I'll try to submit Fireplace tomorrow.
| Assignee | ||
Comment 4•12 years ago
|
||
I just sent the pull request for Fireplace, sorry for the delay.
| Assignee | ||
Comment 5•12 years ago
|
||
Just sent another pull request for webpay.
| Reporter | ||
Comment 7•12 years ago
|
||
Hi Bogomil and team,
For Marketplace, please continue working on this when you have time. It is not just for FFOS release, but it also gets pushed on the web was well.
Zamboni has tons of strings and it takes a long time to translate. I encourage the team to use this time to localize the content. When the product is ready, you don't have to work on this like many team do.
If bg is to be released, it is unlikely it is in the 1.1 release. Still, Marketplace needs to be done.
I hope I have answered your questions.
Thanks,
Peiying
| Reporter | ||
Comment 8•12 years ago
|
||
Hi Bogomil and team,
it is now official that bg will be offered in 1.2 release. Looks like you have completed Fireplace and Webpay already, but the Zamboni component still has quite a bit of work left to do: http://l10n.mozilla-community.org/~flod/mpstats/.
Please start working this at your earliest convenience.
Thanks,
Peiying
Summary: [B2G][l10n][Marketplace] [bg]: localization needed for v1.1 release → [B2G][l10n][Marketplace] [bg]: localization needed for v1.2 release
Comment 9•12 years ago
|
||
So you wait for us to translate it and then to include it into plans? this is not gonna happen. Tell me, please where I can see the plans for the release and to talk t othe team and to make it happen.
| Reporter | ||
Comment 10•12 years ago
|
||
Bogomil, I don't have concrete info on rollout plan (launch date) but it is requested in this bug: https://bugzilla.mozilla.org/showdependencytree.cgi?id=905292&hide_resolved=1. Marketplace plays a big part in the overall product readiness.
A lot of the uncertainly on when a locale is to be rolled out has to do with partners that want to add a locale on short notice. bg may have been part of the initial discussion but there is no date associated with it. If you think the volume is manageable and you would like to wait, that's ok. Personally it's good to get the two smaller components ready so if it has to roll out soon, at least the most visible part of the marketplace is ready.
This is all I know at the moment, so you can plan (or not plan) accordingly.
Thank you,
Peiying
Flags: needinfo?(pmo)
Comment 11•12 years ago
|
||
Thanks!
| Reporter | ||
Comment 12•12 years ago
|
||
Hello Bogomil,
The marketplace components are moved to a new location that is a lot easier to work with than through github. In the order of priority, here they are. :
p1 front end: https://localize.mozilla.org/projects/fireplace/
p2 payment: https://localize.mozilla.org/projects/webpay/
p3 AMO (this contains some legacy strings): https://localize.mozilla.org/projects/amo/
p4 communication dashboard: https://localize.mozilla.org/projects/commbadge/
p5 publishing tool for developer: https://localize.mozilla.org/projects/rocketfuel/
If you have access issue or if any other contributors can't access it, let me know.
Thanks,
Peiying
| Reporter | ||
Comment 13•12 years ago
|
||
Hello,
For categories, those strings are can be found in https://addons.mozilla.org/en-US/localizers/bg/categories/
The person who works on this needs to have an account on add-on.
You can also check the overall progress here: http://l10n.mozilla-community.org/~flod/mpstats/.
| Assignee | ||
Comment 14•12 years ago
|
||
Hello,
The categories are done.
| Reporter | ||
Comment 15•12 years ago
|
||
Hi Mihail,
Thanks for continuing making progress on this product. There are a lot more strings yet to be worked on and we also added a new component called zippy. https://localize.mozilla.org/bg/zippy/
| Assignee | ||
Comment 16•12 years ago
|
||
Hello Peiying,
I translated the strings for zippy in Verbatim and they are ready for review.
I also have a question regarding localization - should I do all the translations in Verbatim and request reviews or just continue doing it through GitHub and pull requests. If the preferred method is through Verbatim, then I should probably request permissions to review the the translations myself, if that's possible. Maybe this is not the right place to ask? I'm sorry if that's the case.
Thanks.
| Reporter | ||
Comment 17•12 years ago
|
||
Hi Mihail,
Thank you for completing Zippy.
As for what's the best way to completing the task, if you feel comfortable working with Github, please continue doing so.
If you choose Verbatim, you need to register by providing info such as locale you are working on, and the role you want to play (localizer, reviewer or both). The admin will give you permission. Thank you!
| Reporter | ||
Comment 18•12 years ago
|
||
Hi Mihail,
Please let me know if you prefer to have admin permission. Without committing the codes, the status is out of sync, and I know you have completed more than what this page shows http://l10n.mozilla-community.org/~flod/mpstats/.
Let me know how I should proceed.
Thank you,
Peiying
| Assignee | ||
Comment 19•12 years ago
|
||
Hi Peiying,
I don't need admin permissions anymore. Since working directly with GitHub is no problem, I'll continue sending pull requests when I've finished localizing a project.
Thank you for the response!
Comment 20•11 years ago
|
||
Fireplace in now translated.
| Assignee | ||
Comment 21•11 years ago
|
||
Thanks, but I can't set it to FIXED for some reason.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Updated•11 years ago
|
Resolution: WORKSFORME → FIXED
| Reporter | ||
Comment 22•11 years ago
|
||
does this work? thank you Mihail!
| Reporter | ||
Comment 23•11 years ago
|
||
Mihail, marketplace is independent from versions like Gaia. The features are evolving, so check Verbatim often and sign up dev-l10n-web@ email list to get notified. Here is the current completion status: https://l10n.mozilla-community.org/~flod/webstatus/mpstats/.
Summary: [B2G][l10n][Marketplace] [bg]: localization needed for v1.2 release → [B2G][l10n][Marketplace] [bg]: localization needed for multiple platforms
| Reporter | ||
Comment 24•11 years ago
|
||
Make sure to click the VCS to Commit link or the codes won't be pushed to Github. Make sure to go back to each component to do that.
You need to log in
before you can comment on or make changes to this bug.
Description
•