Last modified: 2014-07-21 13:11:35 UTC
Intention: Whenever a new VE feature is launched it seems as though existing translations are not included. Steps to Reproduce: 1. Go to https://sv.wikipedia.org/wiki/Bonsai?uselang=de&veaction=edit 2. Click on media settings for the first image 3. Click advanced settings (Erweiterte Einstellungen) Actual Results: 2. Alt_text dialogue reads "Alternative text" 3. Position dialogues read "Position: Left, right, center, none " Expected Results: 2. Alt_text dialogue reads "Alternativtext" (per https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media-alttext-section/de) 3. Should also be all in german (per e.g. https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media-position-left/de) Reproducible: Always This is not just an issue with the above features (or with uselang=de) but rather happens at every launched VE feature. Since the translations have normally been done before there is no reason why they should not be included as part of the pushing of any new feature. The VE translations also seem to take longer to go live then translations in other parts of the interface (seems to happen only when there are other VE updates).
(In reply to Lokal_Profil from comment #0) > Intention: > Whenever a new VE feature is launched it seems as though existing > translations are not included. > > Steps to Reproduce: > 1. Go to https://sv.wikipedia.org/wiki/Bonsai?uselang=de&veaction=edit > 2. Click on media settings for the first image > 3. Click advanced settings (Erweiterte Einstellungen) > > Actual Results: > 2. Alt_text dialogue reads "Alternative text" > 3. Position dialogues read "Position: Left, right, center, none " > > Expected Results: > 2. Alt_text dialogue reads "Alternativtext" (per > https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media- > alttext-section/de) > 3. Should also be all in german (per e.g. > https://translatewiki.net/w/i.php?title=MediaWiki:Visualeditor-dialog-media- > position-left/de) > > Reproducible: Always > > This is not just an issue with the above features (or with uselang=de) but > rather happens at every launched VE feature. Since the translations have > normally been done before there is no reason why they should not be included > as part of the pushing of any new feature. > > The VE translations also seem to take longer to go live then translations in > other parts of the interface (seems to happen only when there are other VE > updates). Translations of VE items should go live at the same time as non-VE items (as they are done by the same process) – if not, this sounds like a localisation update bug. Moving there to see if anyone has any ideas.
Anybody having an idea how to investigate this?
Time difference between VE and non-VE items I've got no source for rather than a general impression (thus "seems" in my statement). In general though we are talking about weeks before the translations appear. The main issue for me would be why existing translations are not included with the launch of new features? For the above case both de and sv translations existed before the features went live, yet they were not included until 1+ week later. Surely the point of making the messages translatable before they go live is to avoid users having to encounter untranslated strings.
I am not sure if this counts as an example or not. A French Wikipedian reported he spotted a few untranslated messages in the interface. I checked, and the French equivalent for both of them did exist on TranslateWiki. While https://translatewiki.net/wiki/MediaWiki:Visualeditor-dialog-transclusion-multiple-mode/fr is quite recent, https://translatewiki.net/wiki/MediaWiki:Visualeditor-dialogbutton-template-tooltip/fr was created last year. The interface tells me these are the correct messages, but they still won't show up. So I just created the related MediaWiki message locally, but I don't think this should be the solution.
James: As this is assigned to you, do you plan to investigate?
I wonder if bug 64230 is related?
(In reply to Elitre from comment #7) > I wonder if bug 64230 is related? Seems possible; adding as a see-also. (In reply to Andre Klapper from comment #6) > James: As this is assigned to you, do you plan to investigate? No; unassigning.
We'd need to check if the fix for bug 67805 fixed this as well.
