Closed
Bug 1620608
Opened 5 years ago
Closed 3 years ago
Community Portal Localization
Categories
(Mozilla Localizations :: Other, task)
Mozilla Localizations
Other
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Nukeador, Unassigned)
Details
- Project owner: Rubén Martín
- Description of target audience: Mozillians and new contributors
- Where the source content (will) lives: community.mozilla.org
- Target locales: TBD (de, fr, es, ru, pt, pl, it)
- Reference materials (e.g., style guide):
- Project's roadmap (URL preferred): https://docs.google.com/document/d/1CnHiy_ZxGOVqaFn0B8Ev0mapH_lgH-GgV80LzQSZJ9w/edit#heading=h.gmdczsb1vo87
- Project's target release date: Q2 2020
Comment 1•5 years ago
|
||
Capturing past conversations we've had about this:
This project is split into two content types: UI strings and database content. Each will require the use of distinct file formats (gettext and xliff, respectively). The recommendation from the l10n team has been to set up automation for export/import of strings between BuddyPress (or WPML, or Polyglot) and a Github repository. L10n config can be set up in that repo to direct UI strings to Pontoon, and db content into the vendor pipeline (or split it between locales and send some locales to vendor pipeline, others to Pontoon). As of today, Playground (the dev company) is evaluating options for meeting that recommendation.
Comment 2•3 years ago
|
||
Assuming this is a WONTFIX at this point.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•