Closed
Bug 667890
Opened 14 years ago
Closed 14 years ago
Any localized edits made between two ready-for-l10n English revisions are removed
Categories
(support.mozilla.org :: Knowledge Base Software, task, P1)
support.mozilla.org
Knowledge Base Software
Tracking
(Not tracked)
VERIFIED
FIXED
2011-07-19
People
(Reporter: scoobidiver, Assigned: rrosario)
Details
A localized revision is associated to an English revision.
If there are edits based on the localized revision, they are removed when there is a new ready-for-l10n English revision.
See:
https://support.mozilla.com/fr/kb/Les%20modules%20compl%C3%A9mentaires%20sont%20d%C3%A9sactiv%C3%A9s%20apr%C3%A8s%20une%20mise%20%C3%A0%20jour%20de%20Firefox/history
https://support.mozilla.com/fr/kb/Les%20modules%20compl%C3%A9mentaires%20sont%20d%C3%A9sactiv%C3%A9s%20apr%C3%A8s%20une%20mise%20%C3%A0%20jour%20de%20Firefox/revision/15143 : The keywords added in this revision were removed when I tried to translate the new ready-for-l10n English revision.
| Reporter | ||
Comment 1•14 years ago
|
||
To clarify the above example:
* French revision 12157 has been based on French revision 11755 (right editor) and English revision 11844 (left editor).
* French revision 15318 has been based on French revision 12157 (right editor)(instead of 15143) and English revision 15291 (left editor).
As long as this bug is not fixed, any ready-for-localization article approvals should be postponed.
Comment 2•14 years ago
|
||
So, what do you mean with "If there are edits based on the localized revision". Do you mean edits *to* the localized revision?
| Reporter | ||
Comment 3•14 years ago
|
||
(In reply to comment #2)
> Do you mean edits *to* the localized revision?
Yes.
Comment 4•14 years ago
|
||
This is serious, and it looks like Bug 668609 is related indeed.
James, can you make this a priority for 7-19? We are going to ready for l10n Firefox 6 articles in two weeks from now, and this would cause a lot of confusion.
Target Milestone: --- → 2011-07-19
| Assignee | ||
Comment 5•14 years ago
|
||
This may be fixed with the patch for Bug 668609. I will investigate.
Assignee: nobody → rrosario
Updated•14 years ago
|
Priority: -- → P1
| Assignee | ||
Comment 6•14 years ago
|
||
This looks fixed to me. I just did the following on stage and it worked as expected.
1- Create new document (https://support.allizom.org/en-US/kb/test-doc), approve and mark as ready for l10n.
2- Translate to Spanish (https://support.allizom.org/es/kb/doc-prueba) and approve.
3- Create new English revision and approve w/o marking as ready for l10n.
4- Create new Spanish revision (translate page correctly shows the original english revision which was ready for l10n) and approve.
5- Create new English revision and approve as ready for l10n.
6- Go to create new Spanish revision. Verify that it is based on the revision from step 4 and that it shows the English revision from step 5.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 8•14 years ago
|
||
Verified that approved locale revision displays in addition to approved en-US changes. Marked this as eligible for automation.
Status: RESOLVED → VERIFIED
Flags: in-testsuite?
You need to log in
before you can comment on or make changes to this bug.
Description
•