Closed
Bug 1605421
Opened 5 years ago
Closed 4 years ago
[project config] Issue when adding an existing locale to a new android-l10n product
Categories
(Webtools Graveyard :: Pontoon, defect, P1)
Webtools Graveyard
Pontoon
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1602896
People
(Reporter: delphine, Assigned: jotes)
References
Details
Attachments
(1 file)
This happened to me with Czech the other day (and happens with all locales in similar STRs, I'll just use Czech as a concrete example).
Czech is an existing locale in android-l10n, that was localizing Fenix and a-c strings.
Michal requested Lockwise for android, so I added Czech to the corresponding l10n.toml file, and then to Pontoon once that had landed.
However Lockwise for Android did not end up available in Czech.
Comment 1•5 years ago
|
||
Currently the only way around this is to force sync for the android-l10n project.
Priority: -- → P1
Updated•5 years ago
|
Summary: Issue when adding an existing locale to a new android-l10n product → [project config] Issue when adding an existing locale to a new android-l10n product
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → poke
Assignee | ||
Updated•5 years ago
|
Status: NEW → ASSIGNED
Comment 2•4 years ago
|
||
Comment 3•4 years ago
|
||
This was actually a side effect of bug 1602896.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
Updated•4 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•