Marketplace is a critical part of the overall FFOS offering. In addition, the product also appears on the desktop and Android. I am listing all the components here so you can work with the community to share the workload and prioritize among other localization tasks. There is a lot of content, but they are divided in smaller components with the exception of of #4. Share with other team members to get this done. Source files in the order or priority: 1) Front End: https://localize.mozilla.org/projects/fireplace/ 2) Payments Front End: https://localize.mozilla.org/projects/spartacus/ 3) Zippy: https://localize.mozilla.org/projects/zippy/ 4) Zamboni: https://localize.mozilla.org/projects/marketplace/ 5) Stat: https://localize.mozilla.org/projects/marketplace_stats/ 6) Communication dashboard: https://localize.mozilla.org/projects/commbadge/ - The progress dashboard: https://l10n.mozilla-community.org/~flod/webstatus/mpstats/ - Testing: http://marketplace-dev.allizom.org/?lang=ar Make sure you have access to Verbatim. If not, please submit a bug or send an email in the "Contact Us" page. Be sure you have admin right so you can grant permission to other community members. I am assigning the bug to you, but do delegate the work to others. Let me know what else I can do help get this started. Thank you, Peiying
Hi Rami, Ahmed and Yoghourta, I am copying the bug to you, but do delegate the task and share among yourselves. I know you are busy with many other requests. Thanks you!
Assignee: nobody → rami223
Hello team, Could each of you localize a few strings here and there in each component, so we can test how the RTL behavior works in each feature? We anticipate issues but would like to identify them ASAP, and find a timely fix. Shall we have a week or two to get this delivered? Of course, Verbatim access needs to be resolved. I see several team members are on the cc list. I would like to help you get access. I need to know the following: who is (or are) - - admin - translator - reviewer We need to assign this role to each applicant. Thank you very much! Peiying
Hello Rami and Ahmed, I understand that there is a change of scope of work with UI strings but it also means you have new and different tasks to tackle. I wonder if there is any chance you can start working on the Marketplace or get a few people from the community to help. We only need these two components localized for the time being: 1) Front End: https://localize.mozilla.org/projects/fireplace/ 2) Payments Front End: https://localize.mozilla.org/projects/spartacus/ Thank you, Peiying
Let's focus on finishing #1 for now since the payment product is not RTL ready.
(In reply to Peiying Mo [:CocoMo] from comment #3) > Hello Rami and Ahmed, > > I understand that there is a change of scope of work with UI strings but it > also means you have new and different tasks to tackle. > > I wonder if there is any chance you can start working on the Marketplace or > get a few people from the community to help. We only need these two > components localized for the time being: > 1) Front End: https://localize.mozilla.org/projects/fireplace/ > 2) Payments Front End: https://localize.mozilla.org/projects/spartacus/ > > Thank you, > Peiying Done :)
Yay!! Blazing fast!! The strings are instantly pushed to the testing site: http://marketplace-dev.allizom.org/?lang=ar. See if it all makes sense and the layout, especially strings with links are properly connected.
After finishing L10N for all strings in the fireplace: https://localize.mozilla.org/ar/fireplace/ we still find some strings not translate to Arabic in the like this: http://www.awesomescreenshot.com/0ff4xq0lfa Is there some strings missing? all language contain Total string:1290 only Arabic language contain 1263: http://www.awesomescreenshot.com/0074xq0295
Hi Mohamed, Thank you for reporting the issues you observed. 1). Different string/word count: the difference is caused by downloading files and working offline when an update takes place. When you merge the files back, the newly added strings are gone. However, this can be resolved by clicking on a link called "Update against templates", two lines below the "Commit to VCS" link (the one you use to commit translations). The admin did it on your behalf, now Arabic has the same word count as the rest. 2). This is a test server, so some of the features are fake. Arabic is not live yet, but when it is, it looks like this: https://marketplace.firefox.com/. If you speak French, you can use this page as a reference page for localizable content: https://marketplace.firefox.com/?lang=fr. 3). While you are checking the translations on the test server, please also check the Right to Left flow of text and the correct behavior when mixed with English text. Report any bugs you find: https://bugzilla.mozilla.org/enter_bug.cgi?product=Marketplace (chose Consumer Page as Component) and cc me on the bug. Thank you, Peiying
Oky Peiying, what is the next step to publish the Arabic language Marketplace to the master Server?
Hi Mohamed, Thank you for completing the remainder strings after the update. I can ask for a push. The markeplace team probably wants to ensure that the product is thoroughly tested and if any serious engineering bugs, they want to fix it before pushing to production. Have you had a chance to play with it there?
Yes, let's do this :)
is it in good enough shape to push to production? Or would you do more testing? The push to production takes place on Tuesdays.
As we see a lot of features are missing in the a test server and i think it's more stable, So we can push it and if we found any more bugs we can submit it.
Hey there - I hear this work is completed. Are we ready to close out this bug? Thank you so much...!
Yes, we can close the bug as the needed components for the immediate launch are done. Thanks everyone. Testing will start once it is pushed on production.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.