Closed
Bug 1008352
Opened 12 years ago
Closed 11 years ago
[marketplace][ne-NP]: localization needed for multiple platforms
Categories
(Mozilla Localizations :: ne-NP / Nepali (Nepal), defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: CocoMo, Assigned: avashmulmi)
References
Details
Hi Avash,
Nepali is one of the high priority locales on our roadmap. Marketplace is now supporting both desktop, Android and FFOS. Opening the bug to start planning on resources. I am assigning it to you help lead the effort.
Do reach out to other community members as some components are big
*Repos and priorities*:
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/
p4 Marketplace (zamboni & categories): https://localize.mozilla.org/projects/marketplace/
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/
*Access to Verbatim*:
If anyone doesn't have an account, please click on the Contact Us link, indicate name, locale, and email address and level of authority (translation, review, admin for the locale) used to access the site.
*Daily Status*:
http://l10n.mozilla-community.org/~flod/mpstats/ - this gets updated twice a day.
*Content Staging*:
Code Push to dev is on Tuesdays. To test the localized strings, https://marketplace-dev.allizom.org/?lang=ne-NP (right now it is in English because the status is 0%).
Let me know if you have any questions.
Thank you,
Peiying
| Reporter | ||
Updated•12 years ago
|
Assignee: nobody → avashmulmi
| Reporter | ||
Comment 1•11 years ago
|
||
mark this bug as won't fix as the launch plan is no longer true. When the community has the bandwidth to work on it, it can start any time.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•