Closed Bug 445562 Opened 17 years ago Closed 16 years ago

en (or some other locale) articles missing from some translation tables

Categories

(support.mozilla.org :: Localization, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: cilias, Assigned: paulc)

Details

Probably a continuation of bug 428998. 1. Go to <http://support.mozilla.com/en-US/kb/Windows+Media+Player>. 2. At the bottom right, use the language selector to switch to Italian. You should be taken to <http://support.mozilla.com/it/kb/Il%20plugin%20Windows%20Media%20Player>. 3. In the Actions box, click "Traduci questa pagina". You should be taken to <http://support.mozilla.com/tiki-edit_translation.php?locale=it&page=Il+plugin+Windows+Media+Player>. Result: The English article does not appear in the list of translations.
It appears always to be n-1 articles in the translation table, rather than the full n number of translations.
Summary: en articles missing from some translation tables → en (or some other locale) articles missing from some translation tables
Target Milestone: --- → 0.7
Another example: This article: http://support.mozilla.com/fr/kb/Modules+incompatibles+avec+Firefox+3 Is a translation of: http://support.mozilla.com/en-US/kb/Add-ons+are+incompatible+with+Firefox+3 But they are not connected, and it's not possible to connect them from any of the two articles.
Target Milestone: 0.7 → 0.8
Target Milestone: 0.8 → 0.9
Target Milestone: 0.9 → 1.0
The fact that they're not connected may have happened long ago. What stops one from creating their own article instead of translating an existing one? Is there a current way to "connect" translations? If not, maybe we should make that into a bug for 1.0. I'll look into the n-1 (one always missing) issue.
(In reply to comment #3) > I'll look into the n-1 (one always missing) issue. Any updates, Paul?
Assignee: nobody → paul.craciunoiu
Target Milestone: 1.0 → Future
Sorry, no. No time...
I don't know if you want each case listed. But here's another: <https://support.mozilla.com/tiki-edit_translation.php?page=ActiveX+%28Polski%2C+pl%29> The English article is listed as nl, and as a result the nl team cannot create a translation of that page.
Tips on reproducing it, such as the history of how it got to be like that would be helpful... I'll play around with it this week and see if I can reproduce it. Those pages should be temporarily fixable by changing their language (edit page for admins allows that). So maybe try to edit the English article and change its language?
(In reply to comment #2) > Another example: > > This article: > http://support.mozilla.com/fr/kb/Modules+incompatibles+avec+Firefox+3 > > Is a translation of: > http://support.mozilla.com/en-US/kb/Add-ons+are+incompatible+with+Firefox+3 > > But they are not connected, and it's not possible to connect them from > any of the two articles. The equivalent translation from the English version seems to be: http://support.mozilla.com/en-US/kb/Des+modules+sont+incompatibles+avec+Firefox+3?bl=n not the one you provided.
(In reply to comment #0) > Probably a continuation of bug 428998. > 1. Go to <http://support.mozilla.com/en-US/kb/Windows+Media+Player>. > 2. At the bottom right, use the language selector to switch to Italian. You > should be taken to > <http://support.mozilla.com/it/kb/Il%20plugin%20Windows%20Media%20Player>. > 3. In the Actions box, click "Traduci questa pagina". You should be taken to > <http://support.mozilla.com/tiki-edit_translation.php?locale=it&page=Il+plugin+Windows+Media+Player>. > > Result: The English article does not appear in the list of translations. I can't see this anymore. On: http://support.mozilla.com/tiki-edit_translation.php?locale=it&page=Il+plugin+Windows+Media+Player I see the English translation listed under "Ingles".
(In reply to comment #6) > I don't know if you want each case listed. But here's another: > <https://support.mozilla.com/tiki-edit_translation.php?page=ActiveX+%28Polski%2C+pl%29> > The English article is listed as nl, and as a result the nl team cannot create > a translation of that page. It seems that https://support.mozilla.com/kb/ActiveX-nl?bl=n is the translation for nl and English is listed correctly.
WORKSFORME until I get some valid examples to test...
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Target Milestone: Future → 1.0.2
(In reply to comment #10) > It seems that > https://support.mozilla.com/kb/ActiveX-nl?bl=n > is the translation for nl and English is listed correctly. For that case, I worked with the locale leader (Tonnes) on working around this bug, and he found that removing the English article from the translation table allowed him to add the nl translation. Sorry I don't have info on how to reproduce.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Well, I'd need that, or I can't really see how to fix it..
It seems that this error happens with that page: https://support.mozilla.com/it/kb/Mozilla+Crash+Reporter?bl=n I'm trying to translate it to Italian, and I always get warned that a page already exists for that language.
Simone: yes, I see the problem now. However, my local environment doesn't seem to reproduce this problem for page you linked to. I may need a copy of the current DB on production to reproduce this.
Paul: contacted Cww in #sumodev in the past days, he told me of errors in the db for that page. Thanks.
Target Milestone: 1.0.2 → Future
Paul: I would like to publish that page about Mozilla Crash Reporter. Is there a way to fix those errors in the db? Thanks in advance.
We recently did a db sync, when pushing newsearch. This bug can now be seen on stage: <https://support-stage.mozilla.org/tiki-edit_translation.php?locale=it&page=Mozilla+Absturz-Melder> "Mozilla Crash Reporter" is listed as "Italiano", even though it's English. Simone, go ahead and fix the Mozilla Crash Reporter assignment on support.mozilla.com. Some more freaky weirdness to this: The English inproduct start page is listed as nl. I noticed it when the l10n dashboard told me that "Firefox Help" "Needs translation". <https://support.mozilla.com/en-US/kb/Localization+Dashboard> AFAIK, no new start pages were created or edit, but I'm not sure.
So this seems to be an inconsistency between the actual article language and the language displayed in the translation table (or somewhere...). Since both of the articles you just linked, Chris, are actually in English. What steps do you currently take to fix these problems (Simone?)? Maybe I can set the bug up locally and trace through. (In reply to comment #16) > Paul: contacted Cww in #sumodev in the past days, he told me of errors in the > db for that page. > Thanks. Cheng, what db tables have the inconsistency? (I imagine a response like "article listed in <locale1> vs <locale2> in tables 1 and 2")
(In reply to comment #18) > Simone, go ahead and fix the Mozilla Crash Reporter assignment on > support.mozilla.com. Ok, had to detach the en-us one from the others, adding the Italian one, and finally adding the en-us one again. It seems to be fixed.
What's the status of this bug? Simone, did you explain a workaround in comment 20, or do you mean that this bug is actually fixed (or, not a bug)?
Status: REOPENED → UNCONFIRMED
Target Milestone: Future → ---
Sorry David, I simply "detached" the en-us page from the rest, assigned it the correct language id and join the page again to the group. The bug - I think - is not solved, but I did not find another page with that problem.
Cheng has investigated translation tables this week, maybe he has some ideas for why this bug may occur.
It's been about a month with nothing on this. I'm marking it WFM for now. Please reopen and comment in the bug when it happens, and try to be detailed.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago16 years ago
Resolution: --- → WORKSFORME
I found a potential source for this: From bug 447903, fix: http://viewvc.svn.mozilla.org/vc/projects/sumo/trunk/webroot/tiki-editpage.php?r1=16566&r2=17379 Likely if timeouts occur between certain lines then articles end up not being connected to their translations. To fix this, really, the best solution is to optimize tiki-editpage so it doesn't time out.
You need to log in before you can comment on or make changes to this bug.