Closed
Bug 1203057
Opened 11 years ago
Closed 11 years ago
On sync_projects, empty translations are marked as unapproved
Categories
(Webtools Graveyard :: Pontoon, defect)
Webtools Graveyard
Pontoon
Tracking
(firefox43 affected)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox43 | --- | affected |
People
(Reporter: mathjazz, Assigned: osmose)
Details
I noticed that in 3 Firefox OS projects, in this file only:
https://pontoon.mozilla.org/sl/firefox-os-20/apps/clock/clock.properties/
All empty translations were marked as translated but unapproved after sync.
| Reporter | ||
Comment 1•11 years ago
|
||
Even when I approve these FxOS strings, on next sync_projects they get unapproved again.
Also, seems like sometimes even non-empty approved strings get unapproved (those 2 strings were previously approved):
https://pontoon.mozilla.org/sl/mozillaorg/privacy/principles.lang/
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → mkelly
| Assignee | ||
Comment 2•11 years ago
|
||
> Also, seems like sometimes even non-empty approved strings get unapproved (those 2 strings were previously approved):
> https://pontoon.mozilla.org/sl/mozillaorg/privacy/principles.lang/
Sounds like a separate bug to me, and I can't replicate. Can you approve those two strings again and see if sync works properly? If not, then we should file a new bug, but if it does work, then we'll have to watch out for it to happen again so we can better figure out the issue.
Comment 3•11 years ago
|
||
Commits pushed to master at https://github.com/mozilla/pontoon
https://github.com/mozilla/pontoon/commit/fe355f5b56dc513b1e857e44ab56a97c8a9d2fa1
Fix bug 1203057: Allow blank translations in silme.
https://github.com/mozilla/pontoon/commit/ad5902489c1ba10abe355080cd5746e51168f04d
Merge pull request #164 from Osmose/unapproved-blank-strings
Fix bug 1203057: Allow blank translations in silme.
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•