Help talk:Extension:Translate
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| mass-mark for translation | 5 | 11:36, 12 April 2014 |
| Can't find outdated text | 0 | 16:57, 25 March 2014 |
| Special page Special:SupportedLanguages php error | 8 | 22:13, 3 March 2014 |
| Link from translation pages to other pages in same page content language | 0 | 21:03, 26 February 2014 |
| Outdated/Fuzzy | 2 | 09:56, 18 February 2014 |
| See Help talk:Extension:Translate/Page translation administration | 0 | 14:46, 24 January 2014 |
| Translate Linktext of a Wikilink transcluded from a template | 2 | 09:27, 12 December 2013 |
| Possibility to chose the language to translate from | 6 | 04:10, 24 May 2013 |
| Mistype with image caption | 1 | 22:08, 8 November 2012 |
| Redirections | 1 | 21:57, 14 September 2012 |
| Admin? | 2 | 01:23, 30 August 2012 |
| Why is it only one way? | 2 | 06:02, 29 August 2012 |
| Already has translations | 5 | 13:13, 16 February 2012 |
| Error Report | 1 | 08:53, 5 February 2012 |
Can I somehow mark many pages at once for translation?
I tried exporting them to xml, adding translate Tags to the text and importing again. But Translate didn't even notice the translate tags; only after manually editing the page does the "mark for translation" option appear. Is there a a recommended way to do this?
XML import is still the fastest; we have added about 300 translatable pages in Meta-Wiki in that way, in a couple days. The only alternative I know of is being worked on at Extension:Translate/Mass migration tools.
... meaning that you imported them and then marked them for translation manually? Or was there some other kind of trick involved?
Yes, dummy edited and marked manually. It's four clicks and a keystroke for each page and all of them very repetitive, I estimate 30 seconds per page. :)
Last time I tried, null edit was not enough.
I was asked to help with translation of Commons:Commons:Senate of Poland. Everything went well except that once everything was translated the polish and french pages claims to be 89% translated instead of 100%. See [1]. It seems like something is 11% outdated but I can not find what and how to fix it. Also there is a problem with categorization. On Commons we never categorize language subtemplates, but this extension seems to do it, see Commons:Category:Wikimedia Polska is there a way to fix it, or is this something I should file a bug report about?
Hi
I'm scratching my head on this php error being thrown on Special:SupportedLanguages. The page works fine on my local. Using the same extension configurations setup on production server. MW 1.21.5, latest same language bundle on local and production server.
Warning: array_merge() expects at least 1 parameter, 0 given in /home/server/public_html/extensions/Translate/specials/SpecialSupportedLanguages.php on line 96 Warning: array_keys() expects parameter 1 to be array, null given in /home/server/public_html/extensions/Translate/specials/SpecialSupportedLanguages.php on line 96 Warning: Invalid argument supplied for foreach() in /home/server/public_html/extensions/Translate/specials/SpecialSupportedLanguages.php on line 364 Notice: Undefined variable: keys in /home/server/public_html/extensions/Translate/specials/SpecialSupportedLanguages.php on line 368 Catchable fatal error: Argument 1 passed to SqlBagOStuff::getMulti() must be of the type array, null given, called in /home/server/public_html/extensions/Translate/specials/SpecialSupportedLanguages.php on line 368 and defined in /home/server/public_html/includes/objectcache/SqlBagOStuff.php on line 212
A hint at what to look at or for greatly appreciated. Obviously I have something different, but what? Running same exact extensions on both local and production server. Everything else is working great. Thanks!
There is condition just before line 96 in the code, so I don't know.
Yes, pulling in user information. RC's from looking at the code? User contribs? I wonder if I rebuild the RC table if that would fix it? I did do a rebuildall when I upgraded after I ran update.php. Thoughts? Thanks
Hi Nikerabbit, still no joy, the page still has a fatal error. I rebuilt RC's, checked the User table, still failing array_merge and array_keys. Debugging log turned on and it shows nothing for this Special Page. Do you have any suggestions on how to debug this? Thanks.
In these cases I start adding manual debugging statements in the code until I understand what is going on.
Thanks Nikerabbit, on a live site so I don't usually like "live debugging" but did it anyway. Seems as if this statement is the issue.
if ( !defined( 'NS_PORTAL' ) ) {
$users = $this->fetchTranslatorsAuto();
} else {
$users = $this->fetchTranslatorsPortal( $natives );
}
We have NS_PORTAL defined. Funny thing is, I comment out the if statement and use either or to define $users.
$users = $this->fetchTranslatorsAuto();
or
$users = $this->fetchTranslatorsPortal( $natives );
The page works, but the heading of languages is doubled at the top.
dansk български español Bahasa Indonesia français English فارسی Nederlands then español Bahasa Indonesia فارسی dansk English български français Nederlands
Even though the languages are in a different order, any of them link to the page's anchors for the language headings.
Also, all users are wrapped in a <del> tag so they look like this, username. Not sure why they are doing that either.
Thanks for your help.
That makes sense. We were supposed to get rid of the NS_PORTAL strategy, which would fix the error for you as well. The double list of languages can be just a byproduct of the heavy caching of the page with your debugging output.
Link from translation pages to other pages in same page content language
Is there a way of manually marking a translation as outdated/Fuzzy. Previously this was done with !!FUZZY!! but this no longer seems to work (at least for my initial test on Commons). Specifically the message should afterwards not be marked as translated which is what Fuzzy now does.
!!FUZZY!! does still work as far as I know.
You are right. I must have written !!Fuzzy!! by mistake and the progressbars do not detect the tag until after reloading.
There are a few missing things that wuld simplify things in managing translated templates. See Help talk:Extension:Translate/Page translation administration for details.
Note that the "TNT" template has been updated on Meta-Wiki, and is still being worked on to implement the Mediawiki standard fallbacks, still missing for now.
The Lua module also fixes various quirks (the version copied from Meta-Wiki to Commons doesn't have these features (notably it is still producing "Script errors" if the specified template name is still not marked in translation to generate the /en subpage: so as long as the source template is not marked you need to create manually the final "/en" version, used as the last default).
Consider a template containing something like
[[Main Page|<translate>Go to main page</translate>]]
which becomes
[[Main Page|<translate><!--T:1--> Go to main page</translate>]]
This looks good on the template page, but as soon as you transclude this template, the <translate> tags get visible on the transcluding page. Is there a way to translate the link text only and still be able to transclude the generated content onto another page?
As Help:Extension:Translate/Page_translation_administration says, you can't call translatable templates directly, but only their languages subpages. This is usually done with templates like {{TNT}} or m:Template:Translatable template (the latter uses lua). Maybe in a distant future Translate will support this use case natively.
Is there a possibility to choose the language to translate from? If a message is already translated to Spanish for example, why cannot we choose to show this message in the translation feature instead of English, it would allow more contributors to translate and make it easier since those languages are closer.
Would also be useful if at the top of any of the languages' pages, we could directly click on Translate instead of only saying "This is a translated page".
Bugs and feature requests should go to bugzilla.
I have a large number of documents in Italian and German that I'd like to import and then translate to English. How does one go about posting feature requests to bugzilla?
The feature request already exists. For reporting things in the future, see How to report a bug. In short, go to bugzilla:, enter a new request, select "MediaWiki extensions->Translate". If it's a feature request (not a bug fix), choose "enhancement".
Use the assistant language feature available in your preferences.
"The translation editor: a message with a tip and and a suggestion from an assistant language"
Please fix it.
Thanks. This is still a wiki, by the way. ;-)
I think the extension should create a redirection from the page with the translated title to the page with the English_title/lang_code.
There is no way that would work cleanly because translations in different languages can be same.
Why does the extension required an admin to mark every edit for translation? Shouldn't that be automatic for confirmed users?
The rights are configurable like any other rights. However, the marker has big responsibility to not mess up things or waste translators time.
Why the translation only work from English to other languages? How can a speaker of one of the translated languages add a section to the page directly in its language and it marks the English version that need to be translated. The Extension should work in all directions. And we should be able to directly edit all languages' pages.
When I try to edit a translated page it says "This page cannot be updated manually. This page is a translation of page Wikimedia Indigenous Languages and the translation can be updated using the translation tool." (on Meta), but a contributor cannot use the translation tool to add "new stuff" or a new section to the page, only to translate sections of the English page.
That is a more complex problem. See this presentation at Wikimania about one system that does that.
What would people do if the page to mark for translations already has translations from when the extension wasn't enabled?
You have to get them out of the way and manually copy/convert them to the new system.
Done, but lots of work!
Yes, I know... If you have any thoughts on how it could be made easier, don't hold back...
Just want to note that it's better to not move the translations. If you move them, then they are separate "useless" pages, and if you leave them where the translate feature will be used (FuzzyBot simply overrides it), then the page history is kept and you can still look at past revisions and copy the content from there.
When I try to translate [1]，it will report an error when I try to include an "external link" with this: [https:// secure.wikidc.org/wm/schols/ THE_TRANSLATION]. It's that really an error or just because it can't call out the CAPTCHA verification?
bugzilla:34182: the workaround is to edit the page directly (right click the link that opens the translation editor and open it in new tab or copy the link address.
