Extension talk:Translate/Archive 2/2014

Archive.

When I enable CAPTCHAs on my wikis for "edits" and "new page creations", the translate tool does not display them. This makes it impossible to save translations that are being submitted.

It took me a full day to realize this was happening; now I have to disable CAPTCHAs on edits and new pages.... which makes it very much more difficult to combat spam and vandalism.

I'd love if this could be corrected somehow! 70.74.182.14 18:47, 1 January 2014 (UTC) Reply

Translate does not currently support captchas. If possible, exclude the user group allowed to do translation from captcha. Nikerabbit (talk) 18:52, 1 January 2014 (UTC) Reply

Information: I did initiate a duplicate of this one in https://phabricator.wikimedia.org/T144009

Sorry and Best Regards Marc.leurent (talk) 07:33, 31 August 2016 (UTC) Reply

Are there advanced search options for the translated pages? For example:

User A: only wants to see pages in language X in the search results

User B: prefers language X, but if no pages exist then include pages in language Y

I see this extension configured here to use subpages and that seems logical, but also seems to make the search results less useful, especially on this wiki. Skunark (talk) 04:03, 23 January 2014 (UTC) Reply

Currently there is no search engine integration besides some tabs on the search page to search only in translations.

A multilingual search is a whole another topic altogether. Nikerabbit (talk) 05:01, 23 January 2014 (UTC) Reply

So if i search for "configuration", the fourth result is a translated page, is that a bug, profile setting issue or inclusive of translation? And the search only in translation is exclusive of the default language? Skunark (talk) 06:44, 23 January 2014 (UTC) Reply

Are you talking of Special:Search or Special:SearchTranslations? Only the latter is provided by Translate (and it's not integrated with Special:Search in any way yet). It is expected that the normal search will treat all languages the same, yes, but not ideal: see bugzilla:54832. Nemo 07:31, 23 January 2014 (UTC) Reply

I am talking about Special:Search with the search results mixing languages in the results. There should be a clever way to group/exclude the subpages or configure language specific namespaces. I guess even to exclude a language category would be effective enough. I like the idea of this translate extension for smaller wiki's, but special:search can't select between languages, like you said, it's not ideal.

I've asked a related question about the sphinx search extension to see if anyone has a configuration supports this extension. You would have to create search attribute for each language, which I think is possible given the right regex, but the Sphinx extension would have to understand this extension or at least the user default language along with the wiki default language. Of course this doesn't help the bulk of the wiki's out there. Skunark (talk) 02:44, 24 January 2014 (UTC) Reply

Translate already sets page language, all you describe does not belong to Translate. Nemo 06:36, 24 January 2014 (UTC) Reply

Is there a way (similar to {{int:lang}}) of getting the language code of the current translation? This is needed to build something similar to Template:Msg-mw on e.g. Commons. Lokal Profil (talk) 18:12, 17 February 2014 (UTC) Reply

That would be bugzilla:57603. As a workaround you can use titleparts magic word to extract language code from the page name. Nikerabbit (talk) 18:29, 17 February 2014 (UTC) Reply

That workaround works for translations done directly on the page (i.e. going to commons:Translations:Commons:Welcome to Commons brochure/text/192/ru) but not when going through the translation interface [1] since the detected pagename is API. Lokal Profil (talk) 11:49, 18 February 2014 (UTC) Reply

Looking at bugzilla:57603 it is also not obvious if this would solve the issue of determining the language in the translation interface. How is this solved in translatewiki.net? Lokal Profil (talk) 11:56, 18 February 2014 (UTC) Reply

I don't understand what "determining the language in the translation interface" means. Language of what? Determining for what purpose? What part of the translation interface?

I see you linked a Special:Translate page view but I don't see the specific problem you want to report about it, please be specific. I guess somewhere a magic word or something is rendered incorrectly in Special:Translate itself? In that case, this is not a real problem: the parsing in page view is limited by nature and doesn't need to be perfect (it's not like you send people there to read the page). Translators of course need to know where their wikitext will end up in order to translate properly, the solution when it's not obvious is that you must clarify that in the qqq documentation. Nemo 14:33, 18 February 2014 (UTC) Reply

Sorry. I thought the link to the Msg-mw template explained it but I'll clarify:

Purpose

I'd like to add a note that text 1 depends on the the translation of text 2 or similarly that an update of 1 should lead to an update of 2. In order to be useful though the link should go to the particular language version of text 2 which we are currently editing (and/or transclude said message). This is frequently done in translatewiki.net using the above mentioned template.

Attempted solution(s)

In order to do this a comment is added to the documentation of text 1 (i.e. .../1/qqq) linking to text .../2/LANGCODE. There are two distinct interfaces for translating messages where the documentation is shown.

• a) The wikipage of the actual translation. I.e. something like [2]
• b) The Special:Translation interface ([3] filtered by "Wikipedia, page 4 step 1, top of Commons main page" for the same message as the one above)

For the example above we want the .../192/qqq message to display a link to .../47/ru.

• {{int:lang}} cannot be used since this gives the interface language
• *{{#titleparts:{{PAGENAME}}|0|-1}} works for a) but not for b) since {{PAGENAME}}=API on this page.

Some way of detecting the language set by tux-languageselector would work for b) Lokal Profil (talk) 16:42, 18 February 2014 (UTC) Reply

See meta:Template:Pagelang Kaganer (talk) 20:41, 18 February 2014 (UTC) Reply

As Kaganer says, you only need the page language.[4]

If that's not displayed correctly in every place you'd want, I recommend subst'ing. Nemo 07:47, 19 February 2014 (UTC) Reply

Substing is not an alternative since the message should be dynamically updated depending on the current language of the translation.

meta:Template:Pagelang won't do the trick since this also relies on #titleparts which will not give the relevant result on Special:Translation.

"Page content language" on the info page is what is needed for a) but for b) we would instead want "data-language" or "data-targetlangcode". I'll add a note about this on bugzilla:57603. Upon closer inspection of translatewiki.net I see that their template also breaks on Special:Translation (returning the interface language instead of the target language)* so I'll consider this to not have a solution for now. To avoid confusion the Commons template now only returns the transcluded message in a) (leaving a link to the english page for b).

Anyway thanks for helping me get to the bottom of this.

• To see:

1. go to [5] filter by "No such special page".
2. Click on the message and see the link + transcluded text in the definition .
3. Use the language drop-down menu to switch to another language
4. Click on the message and see the link+transcluded text in the definition, in the same language as in step 2. André Costa (WMSE) (talk) 11:59, 20 February 2014 (UTC) Reply

Last post was also by me. Sorry for the mixed log-ins. Lokal Profil (talk) 12:07, 20 February 2014 (UTC) Reply

Hello everyone!

I am Pratik Lahoti (User:BPositive) from Pune, India. I am willing to participate in the Google Summer of Code this year. I am interested in the project titled - "Tools for mass migration of legacy translated wiki content".

My mentors for this project would be Niklas Laxström and Federico Leva.

With their help, I have drafted the first version of my proposal page. You can find it here:

https://www.mediawiki.org/wiki/Extension:Translate/Mass_migration_tools

This project is a blessing in disguise for all the translation administrators, as it completely automates the tedious manual task of preparing the pages for translation as well as importing the translations. The proposal page mentions the Project Outline and the approach/solution towards the problem statement. I am done with most of the sections and left with the Project Schedule (which I will finish off when everything is finalized).

Please have a look at the proposal and give your valuable feedback/suggestions. While I have no problems in replying to the suggestions put forth over here, I would appreciate if you can do the same on the discussion page of the proposal, so that all the feedback is at one single place. Looking forward to hearing from you, Thank you! BPositive (talk) 05:04, 4 March 2014 (UTC) Reply

The announcement of the last Language Bundle mentions in the Translate section: "Added support for insertables with numbers in the end on translatable pages." What does it mean? Qgil (talk) 20:27, 31 March 2014 (UTC) Reply

This refers to tvar variables with names like "$value2". Notice the number in the end of the variable. There was a bug that didn't show them in the row of buttons with insertable text at the bottom of the translation editing textarea. As an example, such variables are used quite often in the translation of the weekly tech newsletter, so now it's easier to translate it. Amir E. Aharoni (talk) 20:30, 31 March 2014 (UTC) Reply

I have imported pages which already have tagged and marked for translation (corresponding translated pages also already exist). But Translate extension in Mediawiki not displaying languages menu. I need to make any change on the page to make "Mark this page for translation" link appear and after some clicks menu appears. How can I add Translate menu for all imported pages at once? GeorgeRu (talk) 20:32, 2 April 2014 (UTC) Reply

There is no solution that I'm aware of: until you make a local edit and mark the page for translation, the Translate extension won't recognise the page. Why did you choose XML import, what are you trying to do? If you just need a read only copy, you may want to try Manual:$wgEnableScaryTranscluding instead; there are many other possibilities though. Nemo 22:21, 2 April 2014 (UTC) Reply

Is the possibility given, that f. e. an english written text can get new text input in the translated german version? Thank you for tips, this extension is new for me, Conny (talk) 15:47, 10 April 2014 (UTC).Reply

No, unless you "translate" a unit by adding more text than the original had. Also, bugzilla:35489. Nemo 15:59, 10 April 2014 (UTC) Reply

This post by Nemo bis was moved on 2014年04月16日. You can find it at Project:Village Pump/Flow/2014#c-Brackenheim-2014年04月15日T18:29:00.000Z-Translate_extension_guideline_for_user_pages. Nemo 13:17, 16 April 2014 (UTC) Reply

How do you change the source language of an article? Varnent (talk)^(COI) 13:52, 19 April 2014 (UTC) Reply

I may be wrong, but I think the source language is just whatever $wgLanguageCode is set to. There may be a configuration variable to change the extension's default, but I don't think there is any client-side way to define the source language of a translatable page. GeorgeBarnick (talk) 13:58, 19 April 2014 (UTC) Reply

Please see the linked bug 35489 for more information and workarounds. Nikerabbit (talk) 08:52, 20 April 2014 (UTC) Reply

Hi all,

I have been accepted into the Google Summer of Code 2014 and will be working on the "Tools for mass migration of legacy translated wiki content" project.

As per the project timeline, I have drafted the requirements for this project after discussing with my mentors - Nikerabbit and Nemo_bis. It would be great if the translation admins and translators have a look at the requirements and let us know if they have any other requirements from their side.

Please mention them on the corresponding discussion page. I would like to get some feedback on the importance of requirements mentioned as optional in that page.

I need to get done with this by the next couple of days, so I would appreciate if you can give this a quick look. :)

Thank you! BPositive (talk) 19:39, 23 April 2014 (UTC) Reply

Great! Will have a look. Ricordi samoa 20:04, 23 April 2014 (UTC) Reply

Thanks, looking forward to hearing from you! BPositive (talk) 12:57, 24 April 2014 (UTC) Reply

I'd like to know if there is a way to avoid the header in top of a translated page for unauthenticated user, that cannot do nothing about translation except to read it. It clutters the page making it less readable. 151.40.237.216 17:05, 29 April 2014 (UTC) Reply

Put this in "MediaWiki:Common.css" on your wiki:

.mw-translate-page-info{
display:none;
}

Then override it via "MediaWiki:Group-user.css" (or "MediaWiki:Group-autoconfirmed.css" for autoconfirmed users):

.mw-translate-page-info{
display:inline!important;
}

Read Manual:User group CSS and Javascript. Ricordi samoa 01:38, 30 April 2014 (UTC) Reply

When working with outdated messages and press the "Show differences" link the entire page is displayed in the left column with "Prevoius text" not only the message worked on as in the right column with "New text". It makes it very difficult to work with the message when you have a lot of text in the page. Any solution/suggestion? 195.234.150.70 08:24, 5 May 2014 (UTC) Reply

This only happens for translations made long ago with older version of Translate. There is not much we can do, perhaps except trying to detect those and not show diff at all. Nikerabbit (talk) 10:57, 5 May 2014 (UTC) Reply

Ok, then I understand! Thanks for a quick reply! 195.234.150.70 11:25, 5 May 2014 (UTC) Reply

How can they be detected before opening diff..? Ата ^(talk) 15:29, 6 May 2014 (UTC) Reply

I am trying out MediaWiki 1.22.5 / XAMPP with Apache 2.4.7, MySQL 5.5.36, PHP 5.4.25 as a single site supporting multiple languages on my PC. I have problem using the Translate Extension (in MediaWikiLanguageExtensionBundle-2014.03) to translate a page from a native language say French to English. It seems MW defaults the source language of the page to the site language which is defined as English in this case: $wgLanguageCode = "en"; While I can translate a page in French into other languages like Chinese, I cannot translate it into English, as the generated link for English in Other Languages actually displays the original French page. I tried naming the page with /fr suffix but it does not work. Please see these links as examples: http://61.18.209.180/wpw1/index.php/Ma_deuxi%C3%A8me_page http://61.18.209.180/wpw1/index.php/Ma_troisi%C3%A8me_page/fr

My question is: is there a way to specify the source language for a translatable page when it differs from the site language? Kc.kclau (talk) 18:28, 20 May 2014 (UTC) Reply

That's currently not possible. See Extension talk:Translate/Archive 2/2014#c-Varnent-2014年04月19日T13:52:00.000Z-Change_source_language Ciencia Al Poder (talk) 09:25, 21 May 2014 (UTC) Reply

Please help me. I did a wiki on virtual server and it worked. Now I try it on an online server and always get this error:

Fatal error: require_once(): Failed opening required '/wiki/Flusserwiki2/extensions/cldr/cldr.php' (include_path='.:/usr/lib/php5.4') in /homepages/9/d522574303/htdocs/wiki/Flusserwiki2/LocalSettings.php on line 141</pre>
The path is correct, I changed it a few times and tried some other ways to solve the problem. Nothing worked out. None of the needed extensions like Babel, cldr can be found and included.
Thats my server http://s522574288.online.de/wiki/Flusserwiki2/
My Mediawiki version 1.22.6 with the new MLEB.
Thats whats written to my localsettings.php at the bottom: 
$IP = "/wiki/Flusserwiki2";
$EXT = "$IP/extensions";
require_once( "$EXT/Babel/Babel.php" );
require_once( "$EXT/cldr/cldr.php" );
 
require_once( "$EXT/CleanChanges/CleanChanges.php" );
$wgCCTrailerFilter = true;
$wgCCUserFilter = false;
$wgDefaultUserOptions['usenewrc'] = 1;
 
require_once( "$EXT/LocalisationUpdate/LocalisationUpdate.php" );
$wgLocalisationUpdateDirectory = "$IP/cache";
 
require_once( "$EXT/Translate/Translate.php" );
$wgGroupPermissions['user']['translate'] = true;
$wgGroupPermissions['user']['translate-messagereview'] = true;
$wgGroupPermissions['user']['translate-groupreview'] = true;
$wgGroupPermissions['user']['translate-import'] = true;
$wgGroupPermissions['sysop']['pagetranslation'] = true;
$wgGroupPermissions['sysop']['translate-manage'] = true;
$wgTranslateDocumentationLanguageCode = 'qqq';
$wgExtraLanguageNames['qqq'] = 'Message documentation'; # No linguistic content. Used for documenting messages
require_once( "$EXT/UniversalLanguageSelector/UniversalLanguageSelector.php" );</pre> 92.206.70.252 07:30, 23 May 2014 (UTC)
:Now it says
:Reply 
Fatal error: require_once(): Failed opening required '/wiki/Flusserwiki2/extensions/Babel/Babel.php' (include_path='.:/usr/lib/php5.4') in /homepages/9/d522574303/htdocs/wiki/Flusserwiki2/LocalSettings.php on line 142

:This is a shared webserver, right? Have you checked that you set the permissions as requested by the hosting provider? Some require 755 or even 777. Nemo 08:11, 23 May 2014 (UTC)
::Yes I included babel require_once command recently. but its the same problem. I think permissions is a good clue. Sadly Im not the admin of the server and it takes time to communicate ... . 92.206.12.170 08:36, 23 May 2014 (UTC)
:Your $IP is wrong. It starts with absolute path "/wiki/..." when your actual path is "/homepages/9/d522574303/htdocs/wiki/...". Nikerabbit (talk) 08:16, 23 May 2014 (UTC)
::Thank both of you! Now I got this page (I had it before):
::http://s522574288.online.de/wiki/Flusserwiki2/mw-config/?page=ExistingWiki 92.206.12.170 08:35, 23 May 2014 (UTC)
:Thats the adress of my wiki: http://s522574288.online.de/wiki/Flusserwiki2/
:I use mediawiki 1.22.6 and the latest version of MLEB.
:When I include the code lines described on
:http://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle to my
:localsettings.php I get following error:
:Fatal error: require_once(): Failed opening required
:'/extensions/Babel/Babel.php' (include_path='.:/usr/lib/php5.4') in
:/homepages/9/d522574303/htdocs/wiki/Flusserwiki2/LocalSettings.php on line
:138
:I tried to solve it by myself over and over again. I have php5.4 on my
:server running, i tried different paths for the $IP variable(it solved the
:same problem on a virtual server i ran on my localhost), i even experimented with the cache
:and other soultions.
:I do not understand why mediawiki doesnt find the extensions. Other extensions I included with the main installation of mediawiki have the same directory and path and there is no problem at all. 92.206.12.170 10:44, 23 May 2014 (UTC)
::Now you seem to have an empty $EXT. You should have something like the following:
::Reply 
$IP = "/homepages/9/d522574303/htdocs/wiki/Flusserwiki2/";
$EXT = "$IP/../extensions";

::or 
::
$IP = "/homepages/9/d522574303/htdocs/wiki/Flusserwiki2/";
$EXT = "$IP/extensions";
 Nemo 14:31, 23 May 2014 (UTC)
:Problem solved! But it's just a work around. Developers still should work at this problem. The displaying of errors connected with the magicword.php hinders installing MLEB, if you cut those lines it will work.
:That's how you get MediaWiki 1.22.6 running with MediaWikiLanguageExtensionBundle-2014.04.tar.bz2:
:1) Upload Mediawiki + MLEB to your server
:2) Delete in ./includes/MagicWord.php:
: if ( !$this->mSynonyms ) {
: $this->mSynonyms = array( 'brionmademeputthishere' );
: wfProfileOut( __METHOD__ );
: throw new MWException( "Error: invalid magic word '$id'" );
: }
:3) Install Wiki
:4) Upload LocalSettings.php
:5) Put following code lines to the bottom of LocalSettings.php:
:Reply 
$wgCCTrailerFilter = true;
$wgCCUserFilter = false;
$wgDefaultUserOptions['usenewrc'] = 1;
$wgLocalisationUpdateDirectory = "$IP/cache";
$wgGroupPermissions['user']['translate'] = true;
$wgGroupPermissions['user']['translate-messagereview'] = true;
$wgGroupPermissions['user']['translate-groupreview'] = true;
$wgGroupPermissions['user']['translate-import'] = true;
$wgGroupPermissions['sysop']['pagetranslation'] = true;
$wgGroupPermissions['sysop']['translate-manage'] = true;
$wgTranslateDocumentationLanguageCode = 'qqq';
$wgExtraLanguageNames['qqq'] = 'Message documentation';
# No linguistic content. Used for documenting messages

:6) Reinstall Mediawiki with [yourserver]/[yourwiki]/mw-config/ in your Browser 92.206.100.50 10:22, 24 May 2014 (UTC) Reply 
exclusion
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

Hello, 
Is it possible to exclude some elements of the original article from appearing on translations? Keeping in ming, that the MediaWiki Language Extension Bundle is all that I've got to work with. 85.253.84.55 04:04, 27 May 2014 (UTC)
:It depends what you mean by "appearing". With a simple parser function or a template for it, you can make a wikitext show up only on the source page, for instance. Nemo 05:44, 27 May 2014 (UTC)
::Yes, but as I said, I can only make use of the MediaWiki Language Extension Bundle. I know how to do this, using ParserFunctions, but since that's not an option, I was hoping extension:translate itself had such options. 85.253.84.55 14:28, 27 May 2014 (UTC)
:::Well, before parser functions we had if* templates to do the same things. You still didn't describe what you want to achieve exactly, hence it's hard to suggest what's the best solution. Nemo 15:21, 27 May 2014 (UTC)
::::I wish that some of the elements of the original article would not be included in articles.
::::For example:
::::The quick brown fox jumps over the lazy dog [[File:image]] <- text that is included in the original article
::::The quick brown fox jumps over the lazy dog <- text that is lifted onto translations
::::I could produce something like this [[File:image]], but our goal is to make the job for translations as easy and less confusing as possible. 85.253.84.55 18:45, 27 May 2014 (UTC)
:::::Also.. templates are only shortcuts to strings of code, composed with the help of different wiki provided functions, including parserfunctions. So I think you're confusing templates with something else, since you cannot have a "template" on if functions, if there are no ParserFunctions present. 85.253.84.55 18:52, 27 May 2014 (UTC)
::::::Oh my god.. why can't I edit my posts? The loading icon seems to loop forever.
::::::Fixes:
::::::*I wish that some of the elements of the original article would not be included in translations* 85.253.84.55 18:55, 27 May 2014 (UTC)
:::::::Parser functions were introduced because otherwise users did crazy things with templates. I assure you that we had if* templates before parser functions, just look a bit for history.
:::::::So, you want to hide images on translations? Why? Nemo 20:33, 27 May 2014 (UTC)
::::::::Can you point me to these templates, where if is used without extensions, please? 62.65.231.186 14:16, 29 May 2014 (UTC) Reply 
Template translation
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

Say I mark a page for translation and said page transcludes a template (or other page) which is also marked for translation. Will that template automatically show up in the correct language? Or will I need to adjust each translation to include the language code version of the template, i.e. {{sometemplate/de}} for German? Thanks and regards, ChrisiPK (talk) 01:10, 28 May 2014 (UTC)
:Only mark the page for traslation with <translate></translate> and the translationadmin mark the idioms for translate. Leitoxx (talk) 01:28, 28 May 2014 (UTC)
::I'm afraid I don't really understand. What idioms? And where does this relate to my template question? Regards, ChrisiPK (talk) 08:43, 28 May 2014 (UTC)
:Translate doesn't offer a solution for this yet, you have to copy some templates used here or on Meta.
:Help:Extension:Translate/Page_translation_administration#Markup_examples (last section). Nemo 13:19, 28 May 2014 (UTC) Reply 
Translations not being saved
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

I am having a bit of an issue. Translations provided by anyone other than myself (the admin) will not save. I have someone wanting to start translating my wiki into Russian, but once he finishes translating and he saves everything and refreshes, all his translations disappear and never seem to go through.
I created a test account to see for myself, and it's true. This does not occur for me on my admin account.
I thought that maybe it had something to do with the permissions, but everything appears to check out fine, I'm not sure what would prevent pages from being saved.
require_once( "$EXT/Translate/Translate.php" );
$wgGroupPermissions['user']['translate'] = true;
$wgGroupPermissions['user']['translate-messagereview'] = true;
$wgGroupPermissions['user']['translate-groupreview'] = true;
$wgGroupPermissions['user']['translate-import'] = true;
$wgGroupPermissions['sysop']['pagetranslation'] = true;
$wgGroupPermissions['sysop']['translate-manage'] = true;
$wgTranslateDocumentationLanguageCode = 'qqq';
$wgExtraLanguageNames['qqq'] = 'Message documentation'; # No linguistic content. Used for documenting messages</pre>
The wiki is creawiki.net if you want to see for yourself. You have to be a member to sign in though, but the test account I created is username test, password 123. Special:Contributions/kirabook 22:34, 16 June 2014 (UTC)
:Are you the only user with "skipcaptcha" right? pandorawiki.org had similar symptoms and that was their problem.
:If that's the case, technically the cause is bugzilla:34182, but if translations require entering a captcha you didn't configure your captcha well. Ensure you use QuestyCaptcha and don't require captcha for edits. Nemo 06:14, 17 June 2014 (UTC)
::Aha, so I wasn't completely off. I thought it had something to do with the catcha and tries some different settings, but I didn't see much of a difference. 
::I will look into the QuestyCatcha and see if it works. Thanks so much. kirabook 14:51, 17 June 2014 (UTC)
:::Update: Yes, it was the captcha. I have simply disabled it for certain people and I will be creating a new usergroup (I think) just for the translators to do their thing. Thanks again! kirabook 15:02, 17 June 2014 (UTC)Reply 
Languages tag broken
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

There seems to be something in the water. The languages tag seems to have vanished in "MLEB 2014.07" at least it is not longer showing on "Special:Version" and thus not working on e.g. WikiAPIary. [[kgh]] (talk) 13:16, 5 August 2014 (UTC)
:I'm unable to reproduce on Translate master. Perhaps some other code you have is clearing ParserFirstCallInit or that ParserFirstCallInit is run before our hook is registered. Or you have disabled page translation. Nikerabbit (talk) 15:03, 5 August 2014 (UTC)
::Yeah, that's a strange one since it is working on e.g. this very wiki. Since it is still possible to translate, just done it, it must be some conflicting extension or so. I opened an issue on GitHub. Jamie will know which extensions were upgraded recently and may track this down faster than we can. [[kgh]] (talk) 15:11, 5 August 2014 (UTC) Reply 
Text form and variables
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion
翻訳ツールのテキストフォームと変数
Variables from source text are overwrapping onto the text form, and cannot press the "Save Translation" button.
Hope this is not duplicated. Takot (talk) 13:09, 10 August 2014 (UTC)
:As I am using Chrome on Mac OS X, saving itself can be done with pressing Ctrl-Option-S. Takot (talk) 13:22, 10 August 2014 (UTC)
::Those are called "insertables". PLease file a bug, it seems I previously neglected to. A thing I did is suggesting translation admins to use shorter tvar names. Nemo 19:02, 10 August 2014 (UTC) Reply 
Unable to delete pages marked for translation
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

Hi! 
I have problem with deleting the original page that is marked for translation. When deleting, all translated pages are deleted by the Fuzzybot but the original page is not removed. If I remove the translate-tags I am able to delete the page however(now with my own sysop user account). So I suppose there is some issue with the FuzzyBot user rights. Any suggestions? Is it related to the Translate extension or MW?
I am using:
MediaWiki 1.22.7 ,PHP 5.4.12 (cgi-fcgi) ,MySQL 5.5.22 ,Translate (Version MLEB 2014.05)
Thanks in advance! MWuser 13:06, 12 August 2014 (UTC)
:# Make sure job queue is completely drained (empty)
:# What is the error message when deleting the source page after this? Nikerabbit (talk) 13:27, 12 August 2014 (UTC) Reply 
Unable to delete translation pages
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion
Tracked in Phabricator 
Task T71398 

Hi. Unable to delete Manual:Running_MediaWiki_on_Windows/diq and Download_from_SVN/hu (marked for speedy deletion).
 Permission error
 You do not have permission to delete this page, for the following reason:
 You cannot delete this page because you do not have permission to edit it. Shirayuki (talk) 11:29, 13 August 2014 (UTC)
:There's a fix in master, and this will be deployed on Wikimedia sites by 28 August, AFAIK. siebrand (talk) 18:48, 22 August 2014 (UTC) Reply 
Add support for translating whole page
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

Please add support for translating the whole page including templates that are added here. Paladox2017 (talk) 13:25, 27 September 2014 (UTC)
:Thanks for the suggestion/question but I'm unable to understand it. You may want to look for "template" in the manual: Help:Extension:Translate/Page_translation_administration. Nemo 20:40, 27 September 2014 (UTC) Reply 
Échec de l’enregistrement de la traduction : Unknown error: "tpt-unknown-page"
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

i cannot save my translation
it gives me the error : Unknown error: "tpt-unknown-page"
what shall i do to solve this ?
as information i had the issue concerning the magicword.php
and i used the woraround i found in this discussion
problem solved! But it's just a work around. Developers still should work at this problem. The displaying of errors connected with the magicword.php hinders installing MLEB, if you cut those lines it will work.
i did not found much information about this Unknown error: "tpt-unknown-page" 83.155.122.25 12:53, 29 September 2014 (UTC)
:This is usually caused by badly configured JobQueue. I recommend using the cron approach as explained on that page. Nikerabbit (talk) 14:43, 29 September 2014 (UTC)
::thank you i will check this
::actually my server logs are giving this kind of error
::mod_fcgid: stderr: PHP Notice: Uncommitted DB writes (transaction from DatabaseBase::query (LCStoreDB::get)). in /public_html/w/includes/db/Database.php on line 4147 83.155.122.25 15:15, 29 September 2014 (UTC)
:::The notice "Uncommitted DB writes" can be ignored for now. siebrand (talk) 15:18, 16 October 2014 (UTC)
::::Hi siebrand and nikerabbit : I just had the same error message on Wikimedia Commons, any idea why ? (I was trying to translate some new part of WLE 2015) VIGNERON (talk) 22:06, 24 May 2015 (UTC)
:::::You probably had to wait some more minutes or hours before starting the translation. Nemo 10:52, 8 July 2015 (UTC) Reply 
language choice
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion
Tracked in Phabricator 
Task T37489 

actually my wiki is configured in french
i want to use the translate wiki to help translation from german to french
it seems the wiki considers that any new created page is in french and do no want to change this
and i do not know how to tell the wiki what is the initial language of each page
is there anything i am doing wrong ? 83.155.122.25 17:23, 29 September 2014 (UTC)
:No, it's bugzilla:35489. However, this is (almost) fixed if you use MediaWiki 1.24alpha (Download from Git): see the MediaWiki 1.24 release notes to enable Special:PageLanguage and remember to tell us your experience at User talk:SPQRobin/Page_language. Nemo 20:12, 29 September 2014 (UTC)
::With MW 1.24.2 and Extension:Translate MLEB 2015.04 it was confusing: I tested an English page to be thee translation source page in a German Wiki, on Special:PageLanguage it logged as being changed from German to English but extension Translate 
::* did display translation links the first time correctly, than later on in red (red English link) when viewing on the German page
::* (when the page supposedly was English) I translated to German but the Title did not translate although ext Translate had a translated title, the English title was shown on the German page
::* did not recognise settings from Special:PageLanguage, the language of the translation source page could not be altered from the ext Translate point of view although Special:PageLanguage filed it as to be changed.
::Seems still buggy :-/ Andreas P.   22:05, 22 May 2015 (UTC) Reply 
'Saving the translation failed: The modification you tried to make was aborted by an extension hook' and Documentation problems
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

:Hello, I have the following problems:
:Issue 1:
:When translating, some of the translation units would give me the following error:
:
Saving the translation failed: The modification you tried to make was aborted by an extension hook&lt;/pre&gt;
This seem to occur completely random, some of the units will translate some of them won't. It happens on pages with freshly created markup, as well as on those which I'm only modifying.
Issue 2:
After adding documentation for translation units in the core language (British English), documentation would usually appear on the next day, but only in other languages (not even in all of them) and in pieces. Saving documentation to particular languages fails completely. 
Also:
Is it possible to create markup which won't ask translators to deal with something like:
&lt;pre&gt;'Lorem ipsum, [[(this is not translatable)|(this is translatable)]].'?

:The page I'm referring to is Whonix.org.
:Thank you. 217.172.250.140 00:15, 24 October 2014 (UTC)
::# I see many messages contain links, so this is probably bugzilla:34182. Translators lack "skipcaptcha" permission, add it to them.
::# I'm not sure what you mean by "documentation for translation units in the core language": message documentation, AKA "qqq", is the same for all languages, because it's about the source messages. Where are you looking for message documentation? I do see it in [6], for instance.
::## First of all, please check that the documentation was actually saved: after adding some, visit Special:MyContributions and ensure some pages were created in Translations: namespace with /qqq suffix.
::## While doing so, I noticed [7]. It seems your wiki is misconfigured and believes that all edits come from localhost: this is bound to produce a number of problems, including unexpected behaviour for blocks and ConfirmEdit.
::# Yes, check the manual for "tvar" syntax. Help:Extension:Translate/Page_translation_administration. Nemo 08:39, 24 October 2014 (UTC)
:Hi, just in case someone is wondering, I came across it.
:This was caused by my page having semicolons in the title, which couldn't be properly escaped by the Special:PagePrepare.
:I removed them, and was able to prepare the page. Tuxxic (talk) 12:25, 23 June 2016 (UTC)
:Hi,
:I am getting the following error, even when not using semicolons in data I try to translate:
: {"error":{"code":"hookaborted","info":"The modification you tried to make was aborted by an extension hook","*":"See http://kb/api.php for API usage"}}
:I am aware of the skipcaptcha permission, and it is added to my user's permissions.
:@Nemo bis can you please tell me what to look for ? How can I debug that ?
:Thanks a lot. Tuxxic (talk) 15:36, 14 October 2016 (UTC) Reply 
Deleting languages
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

Quick question, I couldn't find answer in documentation.
How particular languages can be deleted from pages marked for translation?
For example someone accidentally translated to Deutsch(Sie Form), but we only want Deutsch. How we can delete this particular language? 37.190.185.113 18:07, 28 October 2014 (UTC)
:As always: open the translation page, click the "delete" button. Nemo 14:22, 29 October 2014 (UTC) Reply 
Country flags
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

Hello, quick question:
Does language bar (<languages />) support country flags? 217.172.250.215 06:31, 19 November 2014 (UTC)
:There is no such built-in feature. However you should be able to adapt the CSS to include additional images such as flags, sure. On most wikis we know, it would be a terrible idea because the language bar is already so stuffed. Nemo 08:01, 19 November 2014 (UTC)
::In addition, in most cases it is not appropriate to use country flags to represent languages. There exists thousands of languages and less than 200 countries, for example. Nikerabbit (talk) 08:18, 19 November 2014 (UTC)
:::Thanks for information guys. 217.172.250.215 09:22, 19 November 2014 (UTC) Reply 
Error when I run update.php
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion


RESOLVED

Unsolved, no updates in many months.


The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


:When I run update.php I get the following error:
:<pre style="overflow:auto">php extensions/LocalisationUpdate/update.php
:[41a2c536] [no req] Exception from line 24 of /var/www/lighttpd/sjwiki.org/extensions/LocalisationUpdate/fetcher/GitHubFetcher.php: Unable to get directory listing for wikimedia/mediawiki-extensions-Cite
:Backtrace:
:#0 /var/www/lighttpd/sjwiki.org/extensions/LocalisationUpdate/Updater.php(115): LU_GitHubFetcher->fetchDirectory(string)
:#1 /var/www/lighttpd/sjwiki.org/extensions/LocalisationUpdate/Updater.php(137): LU_Updater->fetchFiles(LU_FetcherFactory, string)
:#2 /var/www/lighttpd/sjwiki.org/extensions/LocalisationUpdate/update.php(57): LU_Updater->execute(LU_Finder, LU_ReaderFactory, LU_FetcherFactory, array)
:#3 /var/www/lighttpd/sjwiki.org/maintenance/doMaintenance.php(104): LU->execute()
:#4 /var/www/lighttpd/sjwiki.org/extensions/LocalisationUpdate/update.php(75): require_once(string)
:#5 {main}</pre>
:All help appreciated! SJWiki (talk) 12:49, 26 November 2014 (UTC)
::Does this happen for all extensions or just Cite? Nikerabbit (talk) 19:32, 26 November 2014 (UTC)
:::Just for the update script in LocalisationUpdate. SJWiki (talk) 11:44, 27 November 2014 (UTC)
::::I know, but it would be helpful to know if there is something special in Cite extension or whether it is a problem communicating with Internet/GitHub. Nikerabbit (talk) 14:12, 27 November 2014 (UTC)
:::::What's the best way to check?
:::::I can use git to pull and clone stuff. SJWiki (talk) 19:03, 27 November 2014 (UTC)
::::::You can uninstall Cite and see if the error still happens. Nemo 07:27, 28 November 2014 (UTC)
:::::::Don't I need cite for this to work? SJWiki (talk) 10:41, 8 December 2014 (UTC)
::::::::"This" what? LU and Translate don't require Cite. Nemo 10:38, 14 December 2014 (UTC)
:Today I just get a similar problem. The message differs in directory only:
:<syntaxhighlight lang='text'>Unable to get directory listing for wikimedia/mediawiki</pre> Атомный трамвай (talk) 12:25, 11 January 2016 (UTC)
:What version of MediaWiki and LocalisationUpdate are you using? It sounds like you are using very old version. Nikerabbit (talk) 16:09, 19 January 2016 (UTC) Reply 
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

[edit]
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

Hello,
are [edit] links dependent on Language Extension Bundle and is it possible to directly point them to specific code parts? Right now, they seems to be completely shuffled.
Example: 
https://www.whonix.org/wiki/Starting_Whonix#PAE_crash
Any idea on what's causing this?
Thank you. 89.228.164.154 11:02, 30 November 2014 (UTC)
:See Help:Formatting   . Do not use level 1 headings. Shirayuki (talk) 11:22, 30 November 2014 (UTC)
::Thanks, switching levels solved the problem. 89.228.164.154 11:32, 30 November 2014 (UTC)
:::You may use level 2 - 6 headings as written in the help page. Shirayuki (talk) 12:13, 30 November 2014 (UTC) Reply 
Avoid accidental creation of source language pages
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

It seems that almost every time we try to create a translated page, the extension defaults to English (which is our source langage) and creates a page/en (and friends). We delete them, and then FuzzyBot seems to really bog down the server. It would be best if we knew why it automatically creates the /en pages, or if we knew steps to avoid to prevent this from happening. 216.246.135.233 01:37, 2 December 2014 (UTC)
:As I wrote, "/en" pages are useful for templates translation. Shirayuki (talk) 02:19, 2 December 2014 (UTC)
::We have a lot of very powerful content built with DLP (the third party version). Having /en versions of our content pages causes problems with DLP, because it lists both page and page/en - which is not what we want. Perhaps I could be more clever with the way I structure the DLP queries, but... I'm admittedly not that clever. Thanks for the suggestion though. 216.246.135.233 02:54, 2 December 2014 (UTC)
:::See Help:Extension:Translate/Page_translation_administration on categories. You can place each language code subpage in a different, language-based category. Nemo 06:29, 2 December 2014 (UTC) Reply 
noinclude?
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

Our wiki uses a lot of transcluded content. Until we found a way to work around this, it had the unfortunate side-effect of creating nested translate tags (which show up in the page's output pages). We've found that we can prevent this by surrounding every <translate> and </translate> tag with <noinclude> and </noinclude> tags. Though that solves the problem, it is somewhat cumbersome, and the </noinclude> tag always shows up at the beginning of the translation editor page as something that ought to be translated (as does the <noinclude> tag at the end). I am hard pressed to think of a reason the translate tags should ever be included in a transcluded page - shouldn't this be the way it behaves by default? 216.246.135.233 01:48, 2 December 2014 (UTC)
:Since automatically-created "/en" pages do not contain <translate> tags, transclude "/en" pages not the source pages. I think the template {{TNT   }} will help you. Shirayuki (talk) 02:16, 2 December 2014 (UTC)
::Thanks for the response. I looked into TNT, but it's a non-starter with my service provider (they will not enable proc_open). Also, I am not in control of who serves our wiki, so suggesting that I change providers is not helpful (I would love to, BTW). I will look into using /en templates though. Thanks again. 216.246.135.233 02:50, 2 December 2014 (UTC)
:::This revision does not require LUA and is simple :) Shirayuki (talk) 03:43, 2 December 2014 (UTC) Reply 
Unable to patrol edits made by users
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion
Tracked in Phabricator 
Task T44162 

The wiki tells me that it fails to mark any translation by users as patrolled when I ask to "Mark as patrolled". Any ideas? SJWiki (talk) 10:43, 8 December 2014 (UTC)
:You can patrol their edits from Special:Contributions (in Translations namespace). Nemo 18:13, 8 December 2014 (UTC) Reply 
Question about Translation Extension
[edit ]
Latest comment: 11 years ago 1 comment1 person in discussion

I installed translate extension and put some text to translate .My wiki's interface language is "zh".But it is shown as 'zh' text.How to change source text to English without change interface language?
(My English is not good....) Zhangjintao(Connect to me at zh.wikipedia.org 09:03, 21 December 2014 (UTC)
:Can you provide a link to your wiki so we can see the problem?
:Also, to clarify: You want the interface text to show in English instead of Chinese? Or you just want the source language to be English? ☠MarkAHershberger ☢(talk)☣ 03:39, 22 December 2014 (UTC)
::Like this,http://zhangjintao.org/wiki/Think_Java:Main_Page ,and I want to keep my interface language is Chinese. Zhangjintao(Connect to me at zh.wikipedia.org 10:48, 30 December 2014 (UTC)
:::I have to say, that is a really beautiful wiki!
:::Your interface language language is set to English. I confirmed that your wiki is not changing language to Chinese even when I set my browser to Chinese and visited your wiki.
:::Look at $wgLanguageCode to change the default language for your wiki.
:::If you still need help, then we should get Amir to help you with the translation bit. ☠MarkAHershberger ☢(talk)☣ 16:05, 30 December 2014 (UTC)
::::Oh,I used universal language selector extension... Zhangjintao(Connect to me at zh.wikipedia.org 23:57, 31 December 2014 (UTC) Reply