914629 - [marketplace][mk]: localization needed to support multiple platforms

Status: RESOLVED INCOMPLETE

(Mozilla Localizations :: mk / Macedonian, defect)

Description

[Peiying Mo [:CocoMo]]

Hello Damjan,

Macedonian is one of the languages  to be supported in Gaia 1.2 release.  In order to support the launch, a few supporting products need to be ready.

Please check the status here: http://l10n.mozilla-community.org/~flod/mpstats/.

Locations to find the strings for different components: 

* 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 (legacy): https://github.com/mozilla/zamboni/tree/master/locale 

Since you are the team lead, I am assigning this project to you.  If you have a different designated person for the job, please reassign.

Peiying

Comment 1

[Goce Mitevski]

P1 + P2 + P3 = 5.677 strings to be translated.

Comment 2

[Goce Mitevski]

Attachment: gaia-l10n-mk-1.2-translated-goce-mitevski.zip

Here are all Gaia 1.2 strings I managed to translate. The string files in the following folders remain untranslated:

- costcontrol
- dialer
- ftu

Comment 3

[Goce Mitevski]

Sorry Damjan, /apps/settings/settings.properties is not translated entirely. I somehow missed that.

It is translated by # Connectivity :: Internet Sharing

Comment 4

[Peiying Mo [:CocoMo]]

Hi Goce,

Thank you for the translation.  I have relayed your submission request in comment #2.  

Also, to make things easier, you can now commit codes through Verbatim. Here are new locations and more components in the order of priority.  

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/ 

Most importantly, for *categories* - which is the first thing a user sees, the strings can be found here:
https://addons.mozilla.org/en-US/localizers/mk/categories/ 

Do you have access to "addon" site? If not, which email address do you use, I will have you added to the site.

To track your progress, as new strings are added to some components at certain frequency, you can check it out here: http://l10n.mozilla-community.org/~flod/mpstats/

Thank you,
Peiying

Comment 5

[Goce Mitevski]

Thanks Peiying!

I've completed p1 on Mozilla Verbatim, but all strings were submitted as suggestion. I have no idea how to mark them as complete.

Btw, when is the final deadline for Firefox OS 1.2 localization? 25th November 2013?

Regards,
Goce

Comment 6

[Goce Mitevski]

Forgot to mention that I have access to the Add-ons site.

I'm getting a "We're sorry, but we can't find what you're looking for." message for https://addons.mozilla.org/en-US/localizers/mk/categories/

Comment 7

[Goce Mitevski]

P2 is now complete and uploaded on Mozilla Verbatim.

Comment 8

[Peiying Mo [:CocoMo]]

Wil, please add "mk" branch to add-on?

Goce, the marketplace can be updated after the FFOS code is released to partners.  Having said that, you do want to have some time to test your submission. In addition, marketplace is updated every so often, so your on-going support is needed.

Comment 9

[Wil Clouser [:clouserw]]

Goce has been added to the group.  That URL will start working after our push next Tuesday at noon PST.

Comment 10

[Goce Mitevski]

Thanks Wil!

Peiying, the categories of https://addons.mozilla.org/ are now translated.

https://addons.mozilla.org/en-US/localizers/mk/categories/

Comment 11

[Peiying Mo [:CocoMo]]

thank you Goce, please begin testing whenever you have a chance.

Comment 12

[Goce Mitevski]

I've already tested the translated categories and they work nicely. Here are two screenshots:

https://dl.dropboxusercontent.com/u/125611/FFOS/2013-12-01-20-47-01.png
https://dl.dropboxusercontent.com/u/125611/FFOS/2013-12-01-20-47-17.png

What I don't get is how to Review suggestions on Mozilla Verbatim and mark translations as final. Can you please provide further info about this. Also, when is the final deadline for localizing Firefox OS v. 1.2 - maybe we're after 1.3 now?

Thanks!

Comment 13

[Peiying Mo [:CocoMo]]

Hi Goce, 

mk is still part of 1.2 release.  Thanks for working on it and they look good.

Do you know if you have access to Verbatim?  Usually a user has either permission to commit or permission to review.... and it is product specific. If you can commit strings, you don't need others to review your submission. If you have permission to review, you can't make changes directly to the strings.

Let me know who needs access for what tasks, I will make sure you and others have the right setting.

There are a lot of marketplace components to be done, so let's get you the proper permission to do the work.

Thank you,
Peiying

Comment 14

[Goce Mitevski]

Hi Peiying,

Sure, I have an account. I can make direct changes to strings download and upload .po files.
https://localize.mozilla.org/accounts/sepokroce/

The reason I was asking about the reviews is that even after uploading the .po file with the translations, the translated strings are still marked for review.

For example, here: https://localize.mozilla.org/mk/fireplace/ I get a link that says "Review suggestions (178 left)" and that's the total number of translated strings I submitted.

Regards,
Goce

Comment 15

[Peiying Mo [:CocoMo]]

Hi Goce,

Would you like to change your status to admin or is there another person you believe who should review your work?  Let's get this resolved soon.

Also, the product is going to support desktop, Android in addition to FFOS.  Since we last talk, there are a few changes, so to summarize, here are the components in the order of priority:

p1 front end: https://localize.mozilla.org/projects/fireplace/
p2 payment: https://localize.mozilla.org/projects/webpay/
p3 payment processor (Zippy): https://localize.mozilla.org/projects/zippy/ (this is a small new component)
p4 Marketplace (zamboni & categories): https://localize.mozilla.org/projects/marketplace/ (this used to be called AMO)
P5 marketplace stats: https://localize.mozilla.org/projects/marketplace_stats/
p6 communication dashboard: https://localize.mozilla.org/projects/commbadge/
p7 publishing tool for developer: https://localize.mozilla.org/projects/rocketfuel/

Overall status: http://l10n.mozilla-community.org/~flod/mpstats/ 

Thank you,
Peiying

Comment 16

[Goce Mitevski]

Thanks for the update Peiying.

My status is already set to Admin, as I have the privileges to review stings.

Comment 17

[Goce Mitevski]

Here's what has been translated so far: p1, p2, p3 and p6.

Comment 18

[Goce Mitevski]

Hi Peying,

Vanco Stojkov is a new member in our localization community and I would like to request his promotion to Administrator on Mozilla Verbatim. His username is: "van100j" and he is registered with the following email address: [e-mail]".

Is it possible to have more than one administrator per language on Mozilla Verbatim?

Comment 19

[Matjaz Horvat [:mathjazz]]

Permission granted to van100j.

Happy localizing, Macedonians!

Comment 20

[Goce Mitevski]

Thanks Matjaz.

Here is another status update: P5 is completed as well and we're working on p4 in the meantime.

Comment 21

[Goce Mitevski]

Currently working on P4: https://localize.mozilla.org/mk/

Comment 22

[Peiying Mo [:CocoMo]]

Hi Goce,

Thanks for your contribution and making great progress.  The marketplace team has been working on fine tuning the components, especially the "zamboni" part which is more manageable now.  The status is turning green for a lot of components!

Comment 23

[Peiying Mo [:CocoMo]]

Hi Matjaz, 

Could you please add two new users to Verbatim:

user name: itatabitovski
email: [e-mail]

user name: Jovan Kostovski
email: [e-mail]

Comment 24

[Peiying Mo [:CocoMo]]

Hello Jovan and Ilin,

here is the latest list of the marketplace component list (the product has evolved over time):

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/

1-3 are must and once completed and committed by reviewers, I will have them enabled on the production site.
4-6 are designed for app developers. 

test: https://marketplace-dev.allizom.org/?lang=mk

progress status: http://l10n.mozilla-community.org/~flod/mpstats/ 

Thanks,
Peiying

Comment 25

[Matjaz Horvat [:mathjazz]]

I see users are already created:

https://localize.mozilla.org/accounts/itatabitovski
https://localize.mozilla.org/accounts/chombium

I've granted them permission to submit, review and commit translations for mk.

Comment 26

[Jovan Kostovski]

Hi,

Thanks for the assistance Matjaz.

I have one more question before we start translating.

I saw that Verbatim in fact is one Pootle installation.

Can you please tell me what is the easiest way to test the translation after we finish it?
We can always do a "blind translation" in the Verbatim system, but it would be nice if we can somehow download the translation files, switch the locale of the App (Firefox, Tunderbird etc...) to MK and see in which context each translation string is used and if they are appropriate in it.

Thanks,
Jovan

Comment 27

[Matjaz Horvat [:mathjazz]]

Pei, do we have an l10n preview environment for Marketplace projects, like a stage or something?

Comment 28

[Peiying Mo [:CocoMo]]

this is where you test it in context: https://marketplace-dev.allizom.org/?lang=mk.  The payment flow is a bit tricky and you may not see the entire flow unless you finish a paid transaction.  I don't know how many teams did check those.  The good thing is, if anything is identified after it goes on production, you can still fix it.  The production code push is weekly on Tuesdays.