Closed Bug 932989 Opened 11 years ago Closed 11 years ago

[B2G][l10n][Marketplace] [sk]: localization needed for v1.2 release

Categories

(Mozilla Localizations :: sk / Slovak, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: CocoMo, Assigned: rozbora)

References

Details

Hello,

sk is part of the 1.2 release and marketplace is a major component as part of  the product readiness.  

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 once called Zamboni): 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/

For "categories", the strings 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 Marketplace progress here: http://l10n.mozilla-community.org/~flod/mpstats/.

Prior to product launch, P1, P2 and categories must be complete and tested.  

Thank you,
Peiying
you can test the localization on a device or here: https://marketplace-dev.allizom.org/
Blocks: 914708
Completed for Slovak except for the Publishing tool, which will stay in English.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Hi Vlado,

According to http://l10n.mozilla-community.org/~flod/mpstats/, AMO is half way through.  Also the publishing tool seems to have some text localized already.  Is this the team's decision to leave it in English>
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
AMO frontend is fully translated. What is left untranslated is a DevHub and Editor pages. This is intentional. Also Publishing tool as is a Devpage and left untranslated intentionally.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.