Help talk:Extension:Translate

Error Report

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? ZumarX 06:57, 5 February 2012 (UTC)

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. Nikerabbit 08:53, 5 February 2012 (UTC)

Already has translations

What would people do if the page to mark for translations already has translations from when the extension wasn't enabled? Ebe123 23:28, 6 February 2012 (UTC)

You have to get them out of the way and manually copy/convert them to the new system. siebrand 00:05, 7 February 2012 (UTC)

Done, but lots of work! Ebe123 00:54, 7 February 2012 (UTC)

Yes, I know... If you have any thoughts on how it could be made easier, don't hold back... siebrand 22:14, 7 February 2012 (UTC)

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. SPQRobin 02:06, 9 February 2012 (UTC)

Didn't know that. Thanks for the tip. siebrand (talk) 13:13, 16 February 2012 (UTC)

Why is it only one way?

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. Amqui (talk) 00:32, 29 August 2012 (UTC)

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. Amqui (talk) 00:37, 29 August 2012 (UTC)

That is a more complex problem. See this presentation at Wikimania about one system that does that. Nikerabbit (talk) 06:02, 29 August 2012 (UTC)

Possibility to chose the language to translate from

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. Amqui (talk) 00:39, 29 August 2012 (UTC)

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". Amqui (talk) 00:41, 29 August 2012 (UTC)

Bugs and feature requests should go to bugzilla. Nikerabbit (talk) 06:03, 29 August 2012 (UTC)

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? ~ Michael Chidester ^(Contact) 01:28, 24 May 2013 (UTC)

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". πr² (t • c) 04:10, 24 May 2013 (UTC)

Use the assistant language feature available in your preferences. Nikerabbit (talk) 06:03, 29 August 2012 (UTC)

It should be directly selectionable from the translation feature if the particular message is already translated in other languages, we should have the option of selecting those to make our own translation. Amqui (talk) 07:46, 3 September 2012 (UTC)

Redirections

I think the extension should create a redirection from the page with the translated title to the page with the English_title/lang_code. Amqui (talk) 00:50, 29 August 2012 (UTC)

There is no way that would work cleanly because translations in different languages can be same. Nikerabbit (talk) 06:04, 29 August 2012 (UTC)

I agree, thanks. Amqui (talk) 07:47, 3 September 2012 (UTC)

Admin?

Why does the extension required an admin to mark every edit for translation? Shouldn't that be automatic for confirmed users? Amqui (talk) 00:51, 29 August 2012 (UTC)

The rights are configurable like any other rights. However, the marker has big responsibility to not mess up things or waste translators time. Nikerabbit (talk) 06:08, 29 August 2012 (UTC)

OK thanks Amqui (talk) 01:23, 30 August 2012 (UTC)

Mistype with image caption

"The translation editor: a message with a tip and and a suggestion from an assistant language"

Please fix it. Kaganer (talk) 16:00, 8 November 2012 (UTC)

Thanks. This is still a wiki, by the way. ;-) Nemo 22:08, 8 November 2012 (UTC)

Translate Linktext of a Wikilink transcluded from a template

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? Patrick87 (talk) 18:57, 11 December 2013 (UTC)

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. Nemo 09:11, 12 December 2013 (UTC)

Ah thanks, totally makes sense.

I skipped the paragraph since I knew how to translate templates using such mechanisms, but i didn't know it was a requirement. Will change the template transclusion then. Patrick87 (talk) 09:27, 12 December 2013 (UTC)

See Help talk:Extension:Translate/Page translation administration

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). Verdy p (talk) 14:41, 24 January 2014 (UTC)

Outdated/Fuzzy

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. Lokal Profil (talk) 18:07, 17 February 2014 (UTC)

!!FUZZY!! does still work as far as I know. Nikerabbit (talk) 18:29, 17 February 2014 (UTC)

You are right. I must have written !!Fuzzy!! by mistake and the progressbars do not detect the tag until after reloading. Lokal Profil (talk) 09:56, 18 February 2014 (UTC)

Special page Special:SupportedLanguages php error

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! Hutchy68 (talk) 04:45, 26 February 2014 (UTC)

There is condition just before line 96 in the code, so I don't know. Nikerabbit (talk) 07:53, 26 February 2014 (UTC)

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 Hutchy68 (talk) 17:16, 26 February 2014 (UTC)

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. Hutchy68 (talk) 02:20, 1 March 2014 (UTC)

In these cases I start adding manual debugging statements in the code until I understand what is going on. Nikerabbit (talk) 08:18, 1 March 2014 (UTC)

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. Hutchy68 (talk) 14:37, 1 March 2014 (UTC)

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. Nikerabbit (talk) 15:40, 1 March 2014 (UTC)

Which $users statement is better? I guess we have a Portal namespace, which we eventually use for the languages. Low on my list. Ideas why the <del> tags are showing up? Hutchy68 (talk) 16:34, 1 March 2014 (UTC)

Ok, I have it 1/2 working. I like the page and concept. It is very cool, with great feedback for translation admins or anyone interested. The view is buggy though. Commented out the PORTAL_NS check, just wouldn't work on server. Strike through on the page, every single user under every heading. Call the action=purge and it works for awhile until the cache time expires. Then back to a strike through for every single user again. Buggy. Is this a known bug or should I file one? Hutchy68 (talk) 22:13, 3 March 2014 (UTC)

Link from translation pages to other pages in same page content language

This post by Nemo bis was moved on 2014-02-26. You can find it at Extension talk:Translate/Archive 2/2014#c-Lokal_Profil-2014-02-17T18:12:00.000Z-Link_from_translation_pages_to_other_pages_in_same_page_content_language. Nemo 21:03, 26 February 2014 (UTC)

Can't find outdated text

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 [2]. 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? Jarekt (talk) 16:57, 25 March 2014 (UTC)

mass-mark for translation

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? Stm76 (talk) 22:26, 10 April 2014 (UTC)

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. Nemo 07:12, 11 April 2014 (UTC)

... meaning that you imported them and then marked them for translation manually? Or was there some other kind of trick involved? Stm76 (talk) 18:34, 11 April 2014 (UTC)

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. :) Nemo 09:24, 12 April 2014 (UTC)

A bot can be used to null-edit all pages and then to mark them for translation. Ricordisamoa 09:23, 12 April 2014 (UTC)

Last time I tried, null edit was not enough. Nemo 11:36, 12 April 2014 (UTC)

Required rights for "Special:PageTranslationDeletePage"

Looking through the documentation, it doesn't seem to explain what rights are required to access the page Special:PageTranslationDeletePage. Is it just the translation administrator right (as used locally through WMF wikis) or is it that right in combination with another right? If it is a combination (which I believe that may be), then it would be useful for the error message to say which rights are required (in combination), rather than the right that is missing. I would also note that Special:SpecialPages does seem to note this deletion page, nor can I find ready reference to its actions either. It would be great if those more knowledgeable would be able to remedy this situation. Thanks. — billinghurst sDrewth 06:11, 11 June 2014 (UTC)

Works for me on Meta (where I'm translation admin):

You do not have permission to delete this page, for the following reason:

The action you have requested is limited to users in the group: Administrators.

But yes, permissions could be checked earlier. I expanded docs a bit.[3]

And yes, it's one of many unlisted special pages. Nemo 07:50, 11 June 2014 (UTC)

I have specifically mentioned the special page, otherwise it sits mute, and not findable by use of search, which I consider less than desirable. — billinghurst sDrewth 11:49, 11 June 2014 (UTC)

Submitted bugzilla:66472 for listing the extension page on Special:SpecialPages — billinghurst sDrewth 11:55, 11 June 2014 (UTC)

mapping translated page names

Hi,

I'd like to know if there is a way (without using ad redirect) to map a traslated page in a page with a translated name. To be more clear, let say I have the Materials page in English. I can translate it in Italian having the Materials/it page. But I'd like to have instead the "Materiali" page (because "Materiali" is the Italian translation of Materials.

I see that Main page is translated in Pagina principale, but I cannot find a way to plain translate the page name mapping it to the translated page. 151.40.214.23 22:24, 16 July 2014 (UTC)

Sorry, I don't understand what you mean by "map" and "have" here. The "map" is done by translating the page title in Special:Translate; after that you have a page whose display title is "Materiali".

If you mean that you would like the page to actually reside at the title Materiali, that's not possible because the translations should then be unique across all languages. If you mean that you want to link it, same problem, and you should use Special:MyLanguage anyway. Nemo 22:52, 16 July 2014 (UTC)

[RESOLVED] box styling

Hello, how can I change the look (and content) of the language box that appears when inserting <languages />? I haven't found anything in documentation about how to access this box and how to style it. It appears and it is working, I'd only like to style it to fit the content. Are there any CSS classes related to it? Zabien (talk) 08:44, 7 October 2014 (UTC)

It does have plenty of CSS classes you can use to provide different styling for it. There is no documentation for it so the best way is to look at the source code of a rendered box.

You might be interested that there are plans to change completely how the box is displayed: https://gerrit.wikimedia.org/r/#/c/149585/ Nikerabbit (talk) 09:04, 7 October 2014 (UTC)

This helps, indeed! Thank you! I'll keep track of that! Zabien (talk) 09:47, 7 October 2014 (UTC)

Can't mark translations as reviewed

This is a bit strange. I can translate and modified existing translations, but I can't mark translations as reviewed because it says that my session is closed. But it isn't. Proof ot this is that my translations in the same browser, in the same session, at the same time are saved with my username. I tried closing and opening again my session, but it didn't work. I tried Chromium, Chrome and Iceweasel (Firefox in Debian).

I can't say exactly when this started happennig. Maybe a week or two. Before that, I had no trouble.

Let me know if more information is needed.

Update: I didn't specified the site: it's right here in www.mediawiki.org. I have no trouble in meta (see today log)

Update 2: This also happend to me in translatewiki.net. Could it be the translate extension version?

Update 3: It's already been [4]MediaWiki:Tux-session-expired_shown_when_Reviewing_a_message_44515 reported in translatewiki.net by other users. Macofe (talk) 21:37, 15 December 2014 (UTC)

A backported fix should be deployed here very soon now. Nikerabbit (talk) 16:38, 16 December 2014 (UTC)

Was it? Halibutt (talk) 08:24, 7 September 2016 (UTC)

[RESOLVED] Update untranslatable content in translated pages

Hello, I have translatable and untranslatable content (like weblinks) on a page. When I alter/delete the untranslatable content on the page, it still shows up in the translated pages. Is there a way to update this information? I do not see the link for marking the page anew, tried "runJobs.php" and "refreshLinks.php" with no effect. What could I do?

Example source page:

• Content – Untranslatable content - Content

Shows in translated page (DE):

• Inhalt – Untranslatable content – Inhalt

When I now delete "Untranslatable content" in the source page, it still shows up in the translated pages. Source page:

• Content – Content

Translated page:

• Inhalt - Untranslatable content - Inhalt Zabien (talk) 22:03, 15 April 2015 (UTC)

Thanks for using Translate. The expected behavior is that the translation pages are updated soon after the source page is marked for translation. If you do not see the link to re-mark for the page, please check that 1) you have the correct permissions on the user account you are using 2) that the source page is mark-up is valid, most importantly the translate tags should be balanced and not nested at any point. Also check Special:PageTranslation whether the page is listed there and whether you find the link to re-mark the page there. Nikerabbit (talk) 06:31, 16 April 2015 (UTC)

Thank you for that hint. At Special:PageTranslation I find those pages under "Broken pages": "Older versions of these pages are marked for translation, but the latest versions cannot be marked for translation." That's news to me!

When I remove a page there with "Remove from translation" and look into the source code, everything seems normal, the tags are there. The "mark for translation link" won't show up, though, so I cannot mark it for translation again. Here is the code from the page after removing from translation (The languages bar is included via template). Why are the pages invalid after only deleting a single non-translatable content line? And how can I make this work? Zabien (talk) 20:13, 22 April 2015 (UTC)

http://tangowiki.org/wiki/Lyrics:Adoraci%C3%B3n was removed from translation and is not listed at all on http://tangowiki.org/wiki/Special:PageTranslation

It's not corrupted, you simply have to edit it (e.g. change a space) so that Translate "sees" it again. Then you can mark for translation, I think.

As for other pages, I'm not sure why an edit like [5] would corrupt the page, but it may be something very simple. Try adding a newline after a closing translate tag or before an opening one and see if it changes something. Nemo 07:38, 23 April 2015 (UTC)

Thanks a lot! Empty saving seems to do the job. Also, the Language Extension Bundle somehow escaped our last upgrade, still running on a 2013 version (incompatible with the MW version). We upgraded and now it seems to be working better again. Should have checked that first. Zabien (talk) 10:23, 7 May 2015 (UTC)

Good to hear that Nikerabbit (talk) 15:19, 7 May 2015 (UTC)

Use of <translate> within other custom tags

Can anyone identify how one one can use the translation function within something something like the <timeline> function? I have #tag:timeline'd though when I tried <translate> or #tag:translate, of even tried to get the translation outside in its own template https://meta.wikimedia.org/w/index.php?title=Template:StewardsChart&oldid=12473716, all show the text wrapped inside a visible set of translates tag.

Thanks for any ideas on how to achieve this — billinghurst sDrewth 06:08, 20 June 2015 (UTC)

Cannot see translated content

Hi,

I followed the guideline and translated the main page to Vietnamese.

However when I switched to Vietnamese language, I cannot see translated text. There is only English one.

Any one please help me. Anh DOS (talk) 14:02, 8 September 2015 (UTC)

same problem for me!! 213.208.149.68 (talk) 22:26, 8 April 2016 (UTC)

Did you use the unstructured element translation guide? An action=purge might be needed on the main page in that case. Nikerabbit (talk) 08:38, 12 April 2016 (UTC)

Make sure you added <languages /> at the top of your page. Clementflipo (talk) 16:01, 21 April 2016 (UTC)

How to translate category labels

I have this on my page:

[[Kategorie:Beispiele{{#translation:}}|Beispiele]]

and I get

[[Kategorie:Beispiele/en]]

[[Kategorie:Beispiele{{#translation:}}|<translate>Beispiele</translate>]]

does help at all since the result is the same as above. However since I cannot expect English speaking people to know what "Beispiele" means the only way is seems to label the category.

This may be a noob question. I am sure there is a way but I currently do not get it. This example does not cover it so I am a bit lost. [[kgh]] (talk) 16:28, 26 October 2015 (UTC)

Currently, as far as I know, MediaWiki does not support changing category names from what they actually are. There is a task requesting to support this: T26139. Nikerabbit (talk) 09:07, 3 November 2015 (UTC)

@Nikerabbit : has plans changed on this task by any chance ? Because in fact this is what I request in my comment below. Tuxxic (talk) 08:32, 21 October 2016 (UTC)

I am not sure why you are asking me. My priorities are currently elsewhere. Nikerabbit (talk) 15:15, 25 October 2016 (UTC)

Sorry, I did ask because I thought you were in charge of this task.

I will wait to see it resolved or - better! - try to solve it myself when I get familiar with MediaWiki code.

Anyway you are always of good advice, and you helped me a lot. Thank you ! Tuxxic (talk) 12:45, 26 October 2016 (UTC)

Ouch, admittedly I have never labeled a category differently. I took it for granted that this is possible. I guess this will be a nice feature with regard to content translation. Thanks a lot for pointing to the issue. [[kgh]] (talk) 14:15, 3 November 2015 (UTC)

Just an idea: one could try to transclude the translated content of the page display title of the corresponding Translation name space page:

{{#ifexist: {{Translations:Kategorie:Beispiel/Page display title{{#translation:}}}}<!-- 
then transclucde content via {{…}}
-->|{{Translations:Kategorie:Beispiel/Page display title{{#translation:}}}}<!-- 
else
-->|Kategorie:Beispiel{{#translation:}}
}}

… or in general with the magic word {{FULLPAGENAME}}:

{{#ifexist: {{Translations:{{FULLPAGENAME}}/Page display title{{#translation:}}}}<!-- 
then-->|{{Translations:{{FULLPAGENAME}}/Page display title{{#translation:}}}}<!-- 
else-->|{{FULLPAGENAME}}{{#translation:}}
}}

Andreas P. 20:22, 12 November 2015 (UTC)

I just realized (for the record so to say) that the page I’m testing in #ifexist: must be coded correctly as Translations:… and not as page transclusion {{Translations:…}}:

{{#ifexist: Translations:{{FULLPAGENAME}}/Page display title{{translation:}}<!-- 
then -->|{{Translations:{{FULLPAGENAME}}/Page display title{{translation:}}}}<!-- 
else -->|{{FULLPAGENAME}}
}}

Andreas P. 10:27, 13 November 2015 (UTC)

Thanks for your suggestion. The idea I came up with is to do

<translate>Categories:</translate> [[:Category:General{{#translation:}}|<translate>General</translate>]]

[[Category:General{{|translation:}}]]

and add the HIDDENCAT behaviour switch to "Category:General{{#translation:}}". This is a bit of work depending on how many categories there are as well as make the display of the category link [[:Category:General{{#translation:}}|<translate>General</translate>]] appear as if the added category was never hidden but I quite like it. [[kgh]] (talk) 23:15, 12 November 2015 (UTC)

Hi,

I came upon this help topic and it helped a lot.

I need to do a slightly different thing than @Kghbln : my goal is to have the translated category name, but point it to the translated link

Like "Catégorie:Blanc" displays "Catégorie:White" but points to "Catégorie:Blanc/en" Tuxxic (talk) 07:56, 20 October 2016 (UTC)

change default language for a page different to wiki default language

My Wiki is a german wiki. I write a german page and i can translate pages to other languages and it works fine.

But what if i start to write an english article first and i want to translate it into german ? How do i do that ?

When i go to edit it says on top "this is a translation from the german page". Even if i choose "translate to german" then the page is default shown in english.

if i put the /de at the end of the url , i can see the german content

but page loads default without any /<language>

How can i change the default language page individually  ?

my e-mail kristijan80 (at) web.de and the wiki page is http://wiki.yunity.org/index.php/Foodsharing_Transfer_Open_Issues

I don't understand where i can ask for help in a very efficient way.

regards

Kristijan Miklobusec 89.14.26.108 (talk) 19:37, 19 November 2015 (UTC)

I have a related question, I have a Polish language page on outreach wiki and I would like to translate it to English and perhaps a couple other languages. Yet when I mark the page for translation, the system automagically assumes it's in English and I can then "translate it" to Polish. The page is at the moment at outreach:Education/Ideal workshop/pl.

Anyone? I tried the IRC, I looked everywhere, but to no avail so far. Halibutt (talk) 08:23, 7 September 2016 (UTC)

Note: cross-posted the question at Extension talk:Translate/Archive 2/2016#h-Change_the_default_language-2016-09-07T08:33:00.000Z Halibutt (talk) 08:33, 7 September 2016 (UTC)

It seems there is no way to do this, per Extension talk:Translate/Archive 2/2016#h-Change_the_default_language-2016-09-07T08:33:00.000Z... :/ Halibutt (talk) 23:34, 7 September 2016 (UTC)

Translate recurring word/sentence once?

If a word or sentence is used many times on a page, can I somehow code the extension so that this word/sentence only needs to be translated once? abbedabb (talk) 21:27, 21 March 2016 (UTC)

No. If that word or sentence is an independent unit, you can use the translation memory to speed up the translation. Nikerabbit (talk) 08:51, 22 March 2016 (UTC)

You mean, if a user has to translate the same word three times, the system suggests the first translation when translating the second occurance if the word?

(In my template, the line "Photo:" has to be translated four times.) abbedabb (talk) 11:09, 22 March 2016 (UTC)

Yes, you need to translate it four times, but you can pick up the translation from the translation memory. The translation memory works on the unit level, so it does not suggest translation for words embedded in a sentence. Nikerabbit (talk) 09:38, 23 March 2016 (UTC)

Using a <tvar> twice?

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.

---

I want to use a <tvar> at least twice in a template. Is that possible? How do I code that? abbedabb (talk) 11:15, 22 March 2016 (UTC)

I mean that I want tu use THE SAME <tvar> at least twice. It is a year that will pop up in a few places in the text. For now the year will pop up in different scentences, though. That might make it easier. abbedabb (talk) 08:50, 23 March 2016 (UTC)

Can you give an example of the markup? Nikerabbit (talk) 09:39, 23 March 2016 (UTC)

I tried using twice, but it is in two different <translate>-tags, so it seems to work just fine.

The template headline is "Eurovision Song Contest <tvar|year>{{{1}}}" and later in the text the same year is mentioned. But in another translate-section. abbedabb (talk) 09:50, 24 March 2016 (UTC)

It looks like you found a working solution, is that correct? Nikerabbit (talk) 16:49, 25 March 2016 (UTC)

Yes. When two <tvar>-tags with the same name are used, but within two different <translate>-tags, they do not interfere wit each other. abbedabb (talk) 09:03, 29 March 2016 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Adding a conlang, and supported languages

Hi,

If I'm setting up a mediawiki installation about a constructed language, it makes sense that I be able to render pages in that language as well as any others my community may want to use. I can't seem to find any information on how I add a "local" language to a Language Extension Bundle site.

Also, even just translating a page between natural languages (say, English to German) seems to work fine, but when I go to Special:SupportedLanguages, I still see that there's "0" supported languages in my wiki. What piece of config am I missing for the wiki to "know" it supports some languages? Shawnomancy (talk) 22:44, 9 April 2016 (UTC)

$wgExtraLanguages['language-code'] = 'Language autonym'; assuming it is supported by ULS. If it isn't, then there is no easy way to make it appear in the language selector in Special:Translate (but modifying the URL it should work).

For the latter question, the page is cached for some time. If it does not start working, then closer investigation is needed. Nikerabbit (talk) 08:28, 12 April 2016 (UTC)

api error "nomessagefortitle" (2016.04)

Hi,

I upgraded to the new translate extension 2016.04 from the language bundle, but it does not translate new pages:

• api error code:"nomessagefortitle" and info:"Title does not correspond to a translatable message" shows up
• when I save it and look into the Firefox developer console (http://localhost/w/index.php?title=Special:Translate/editpage&suggestions=checks&page=Translations:Taiji+Power+Secrets+(Kelly+2015)/12/en&loadgroup=page-Taiji+Power+Secrets+(Kelly+2015)) it reports a JSON containing just <!-- Box check not available: unknown group --> and the message is not saved by reporting «Unknown error: "tpt-unknown-page"»

What is wrong here? I used already a simply set up but it does not change the behaviour.

• Any hint or solution?
• a configuration problem?

In 2016.01 I had no such problems

Regards Andreas Andreas P. 17:34, 16 May 2016 (UTC)

Please check whether emptying the JobQueue fixes this error. You can run jobqueue with php maintenance/runJobs.php in the mediawiki installation directory. Nikerabbit (talk) 18:02, 16 May 2016 (UTC)

Thanks. Running php maintenance/runJobs.php helped indeed. Is this documented anywhere to check runJobs in that case? Andreas P. 21:11, 16 May 2016 (UTC)

Manual:Job queue should help you to set up job queue so that jobs are processed with low delay. Perhaps this should be better highlighted in the Translate extension configuration page? Nikerabbit (talk) 06:54, 17 May 2016 (UTC)

Perhaps this should be better highlighted in the Translate extension configuration page?

Yes, I agree Andreas P. 09:42, 17 May 2016 (UTC)

Is it possible to hide category pages not in my current language ?

Hi,

I am using Translate to translate my category pages, therefore there are many pages added to them.

My goal is to display on my category page only the pages containing the language code I am using, for instance "Page title/en" should only be displayed on English version of my category page.

Is it possible to do it ? Tuxxic (talk) 12:11, 30 August 2016 (UTC)

You can leave the category inside <translate> tags and change it in translations. Or you can leave it outside <translate> tags and use something like [[Category:Name{{#translation}}]] magic word to automatically append language code of the translation page (and none for source page). Nikerabbit (talk) 08:30, 31 August 2016 (UTC)

For people who would read this as a means of help, the right tag to use is {{#translation:}} (see https://phabricator.wikimedia.org/T148029 )

Thanks a lot @Nikerabbit Tuxxic (talk) 07:35, 14 October 2016 (UTC)

Thanks, but how can I display translated page name instead of Name/en ? Is it possible using MsCatselect, another plugin I use for selecting categories ?

I want to use MsCatSelect to do category selection, so I put the categories out of <translate> tags.

I have so many questions lately, sorry @Nikerabbit, maybe one day I will help you with the code :) Tuxxic (talk) 11:19, 1 September 2016 (UTC)

At the moment it's not possible in MediaWiki core to display translated page names in category listings. Nikerabbit (talk) 19:35, 1 September 2016 (UTC)

OK, I can stop searching :) Thanks for advice ! Tuxxic (talk) 12:27, 2 September 2016 (UTC)

How can I add "Special:MyLanguage" on all category links ?

Hello,

I am searching to add "Special:MyLanguage" in front of all my category links. I know I have to hook some functions, I searched and it seems that Manual:Hooks/OutputPageMakeCategoryLinks can be a good candidate to modify those links.

Can you please help me on writing a hook I can add to my LocalSettings.php ?

Thanks in advance. Tuxxic (talk) 16:03, 7 October 2016 (UTC)

Canonical page for source language

Hmm... which page is canonical for e.g. search engines. I have an English language source page and an English language subpage with /en. Well this does not just apply to search engines: Which English language page is supposed to be served to users? [[kgh]] (talk) 00:49, 12 November 2016 (UTC)

Currently, the /en (or whatever is the source language) is only there to be used for transclusions (Template:TNT for example). Nikerabbit (talk) 16:44, 12 November 2016 (UTC)

Well all languages should be treated equally so the /language code pages are the once to be served to the audience. Still not sure what search engines like Google make of it and what this means for sitemaps [[kgh]] (talk) 18:13, 12 November 2016 (UTC)

Ah, did not see Nike's post. [[kgh]] (talk) 18:14, 12 November 2016 (UTC)

Can't import .po files on my setup

Hello,

I am using Special:ImportTranslations to import .po translations from offline translators.

When I import them, I can "Execute" (see screenshot)

But when I go to my page, the translations are not taken into account.

What do I do wrong ? Tuxxic (talk) 16:23, 23 November 2016 (UTC)

Hey there,

@Tuxxic the same thing is happening in my wiki setup. It would be realy nice if you could share your solution to us.

Did you already solved this Problem??? I realy need to now. StefanN91 (talk) 12:47, 9 March 2017 (UTC)

Hi @StefanN91, what I did was importing the .po files manually, by using Translate/script/poimport.php script, mentioned here: https://www.mediawiki.org/wiki/Help:Extension:Translate/Off-line_translation

I know it's not optimal, but it did the job. I am still waiting for help on the special page, too, since I can't access my web server freely ... Tuxxic (talk) 13:34, 15 March 2017 (UTC)

Thanks for your help. I'm going to use the poimport.php script and see if I works.

Do you know if someone is working on that problem? StefanN91 (talk) 07:06, 23 March 2017 (UTC)

No, I don't, but feel free to open a bug on https://phabricator.wikimedia.org/ :) Tuxxic (talk) 12:10, 23 March 2017 (UTC)

Looks like the bug is known and already solved. https://phabricator.wikimedia.org/T151585

I used this patch https://gerrit.wikimedia.org/r/334907 and it realy worked.

Be careful, the last added version https://gerrit.wikimedia.org/r/336786 caused a different bug in my version. Couldn't change translation Language.

Good luck ;) StefanN91 (talk) 08:04, 24 March 2017 (UTC)

Aha ! Thanks for help, we get closer to the perfection as patches are put ! Tuxxic (talk) 06:58, 27 March 2017 (UTC)

How can I make appear in MediaWiki:Sitenotice?

The idea is to have the languages links appear on all pages.

If you have any alternative suggestions then I'm interested. JamesPoulson (talk) 02:18, 14 December 2016 (UTC)

Not possible with Translate extension. The sitenotice does not know which translations exist. I am not sure it even knows which page it is displayed on, but if it does, you could make your own template that mimics the look of the language box. Nikerabbit (talk) 07:24, 15 December 2016 (UTC)

Automatically switch to reader's preferred language if it is available.

Hello,

I want the page to automatically show the translation for the user's selected laguage if the page is available in that language. I see that on the Extension:Translate page, if I switch my language to Spanish, then it automatically loads the Spanish translation of the page, but on my site https://bible.exchange/translate/Test it does not do the same thing.

Is there a setting that I need to change? Mjamesderocher (talk) 14:38, 22 March 2017 (UTC)

Yes there is. It is called $wgTranslatePageTranslationULS. Nikerabbit (talk) 15:25, 22 March 2017 (UTC)

Is it possible to disable the split in units?

Hi Friends,

I'd like to know if it's possible to disable the auto split in units?

When the page is mark for translation, the system will insert tags like inside the wiki-text.

I'd like to avoid that, so that the entire text inside the <Translate> tag will be translated in one string (Even if there is a hard return inside the <Translate>).

I hope I am clear. Thanks a lot for your help. ClemFlip (talk) 17:19, 20 June 2017 (UTC)

Hi. Could you give us a link to the page you're working on, so that we can understand the use-case/problem you're trying to solve?

And/or, paste the content (or similar) into a sandbox? (Feel free to use User:Quiddity (WMF)/sandboxtranslation). Quiddity (WMF) (talk) 19:14, 20 June 2017 (UTC)

Hi @Quiddity (WMF), thanks for your quick reply.

Unfortunatly, I can't share a link with you since I am working on a local environment.

However, on the sandbox, if you switch to the wikitext edit mode:

https://www.mediawiki.org/wiki/User:Quiddity_(WMF)/sandboxtranslation?action=edit&veswitched=1&oldid=2493201

You can see that

<!--T:1-->

,

<!--T:2-->

,

<!--T:3-->

,... have been inserted inside the wikitext to split all the content inside <translate> and </translate> into translatable strings (Witch is fine).

However, on my wiki, when I switch to the VE edit mode, I see little grey mark that looks like !T:2 in lieu of the

<!--T:2-->

tag (witch is not very convenient for the user).

On the sandbow, however, those little marks don't seems to show up. Is it something that as been solved in a new version of VE maybe?

---

Another question, is their a way to simply disable the auto split? (so disable the fact that the extension automatically insert

<!--T:1-->

,

<!--T:2-->

,

<!--T:3-->

into the wiki-text)

Thanks a lot. ClemFlip (talk) 10:01, 21 June 2017 (UTC)

Re: Visual editor - no, I'm afraid that editor does not currently support Extension:Translate (which is an old and complicated extension).

Re: merging all "translatable units" into a single unit - I don't think so, beyond using <br> at the end of every line. (Which I strongly advise against) -- The extension is designed to make it easy for various people to do "little bits, one at a time" (So if they get bored or busy, halfway through the work, then at least some of the page is translated); therefor, to have "multiple paragraphs all in a single translation unit" isn't possible (as far as I know, and I cannot think of any other hacks/workarounds to make it do that). Sorry, but hope that helps. Quiddity (WMF) (talk) 16:01, 21 June 2017 (UTC)

Re: Re: merging all "translatable units" into a single unit - I don't think so, beyond using <br> at the end of every line. (Which I strongly advise against) -- The extension is designed to make it easy for various people to do "little bits, one at a time"

How to insert a fully translated text to the place of the translated text?

Maybe there is a ready-made fully translated text. In addition, texts for different languages may differ in content and may be they are not a direct translation of one into another. Axdr (talk) 01:09, 27 January 2019 (UTC)

"texts for different languages may differ in content and may be they are not a direct translation of one into another."

This extension is generally intended for direct translations. It is primarily used for keeping multilingual copies of documentation updated.

"How to insert a fully translated text to the place of the translated text?"

Section by section. –Quiddity (talk) 01:30, 27 January 2019 (UTC)

Probably, it is time for you to expand the idea of why a CMS exists. Not only to translate texts in it.

Where do you discuss system tasks? Axdr (talk) 03:28, 27 January 2019 (UTC)

I'm not sure what you mean by "system tasks". We track software issues (bugs and feature requests, etc) in https://phabricator.wikimedia.org/ (documentation at Phabricator). This wiki's purpose is described at Project:About. Some discussion happens here, and some in all the other places listed at Communication. It's a complicated place! –Quiddity (talk) 04:38, 27 January 2019 (UTC)

I think that another extension is needed, which only keeps track of whether there are language-versions of text, and by analogy of the <languages /> tag shows a switch of languages. Axdr (talk) 03:07, 28 January 2019 (UTC)

Links or examples almost always help! They can show other people what you're thinking of, or what you've found that wasn't ideal (and why), or related examples from elsewhere. Your current comments are too short and abstract for me to understand quite what you mean. Please link to or explain the specific use-case(s) that you are thinking of. –Quiddity (talk) 05:45, 28 January 2019 (UTC)

The <languages /> tag works only when the text is translated into other languages with the Translate extension.

But in a situation where the text is not translated, but simply there are other corresponding texts in other languages, the <languages /> tag does not work. But it does need to work.

I think it would be helpful to have a tag capable of displaying a language switch for cases where the texts are not "translated section by section". Axdr (talk) 19:34, 28 January 2019 (UTC)

Ah, I believe Template:Languages works for that use-case, on this wiki. –Quiddity (talk) 21:45, 2 February 2019 (UTC)

Do we always need /en

When we mark a page for translation it always generates the /en language which is the same as the source. Can this be switched off or is it a requirement? If the latter, please indicate this clearly in the documentation. (@Wimjongman) 213.127.250.211 (talk) 20:06, 14 October 2017 (UTC)

[22:17] <wimjongman> Does the translate module always need the /en language even if this is the source?

[22:28] <Nemo_bis> wimjongman: only if it's the source

[22:31] <wimjongman> So if english is the source I cannot block the /en generation?

[22:34] <Nemo_bis> wimjongman: with sufficient effort you might be able to break it, but are you sure you understand the consequences?

[22:34] <Nemo_bis> What are you trying to achieve?

[22:36] <wimjongman> Nemo_bis: I just want to understand if this is the intended behavior.

[22:38] <Nemo_bis> wimjongman: yes, it is

[22:39] <Nemo_bis> The subpage is needed so that all language codes are treated equally and so that a version of the page without Translate's markup is always available

[22:39] <Nemo_bis> Without the /en subpage, you would not really be able to make templates translatable, for instance. The subpages are what gets transcluded

[22:42] <wimjongman> Nemo_bis: I understand. Thanks. Another thing is that our translators have found the Special:MyLanguage tag and starting to put that in the source pages. Is that best practice?

[23:16] <Nemo_bis> wimjongman: yes, we currently have no way to redirect links to the correct page without wikitext changes

[22:46] <wimjongman> Nemo_bis: is SpecialMyLanguage needed in combination with $wgTranslatePageTranslationULS?

[23:16] <Nemo_bis> $wgTranslatePageTranslationULS only works for the first click Wimjongman (talk) 10:43, 15 October 2017 (UTC)

It is not possible to switch this off with configuration. The existence of such pages is mentioned in Help:Extension:Translate/Page translation administration Nikerabbit (talk) 18:41, 16 October 2017 (UTC)

Is there a way to stop the source language pages appearing in search results?

We end up with two sets of search results for the page in the source language, one with /en, and one without. 109.181.53.25 (talk) 11:10, 17 April 2023 (UTC)

Requirements for Special:MyLanguage

On a wiki project I'm working on, I've had an issue for a while, where Special:MyLanguage doesn't redirect properly and instead shows me someone else's version of a cached/static article.

E.g. if it's a logged out user, it shows me a static of being logged out and if I stumble upon a registered user's static, then it will display me as if I'm logged in as someone else.

Any ideas how to fix this? Because currently I'm unable to utilize Special:MyLanguage as its intended purpose. It's more of a burden, than of help. Lyrixn (talk) 12:45, 2 December 2017 (UTC)

First of all, Special:MyLanguage has been in MediaWiki core for some time. Secondly, it sounds like you have a frontend cache that is not properly configured. I've never seen MediaWiki give out pages intended for some other use. Nikerabbit (talk) 17:20, 2 December 2017 (UTC)

Existing translations must be moved

I mean this is one of the main reasons why this extension not get wider used, because there is no function to do this simple time consuming work. Normally there exist already around 20 target subpages e.q. on Commons. So it's not fun to use it. Maybe use Extension:Replace Text. → User: Perhelion 10:02, 22 July 2018 (UTC)

PS: Beside the fact we can't move any page under i18n/ if the page /i18n exists (so we must delete them first?).

EDIT: That was a very bad idea from me [[phab:T114592]] (<-- I love this flow) → User: Perhelion 08:23, 26 July 2018 (UTC)

It is not clear whether you mean existing non-Translate translations (for that use Special:PageMigration) or renaming pages (use the move action), but both are supported with some known issues. Nikerabbit (talk) 11:26, 29 July 2018 (UTC)

Thanks for answer, there is a serious problem on Template:Mozilla Public License/(after moving, which was unnecessary in my opinion too). I edited the /i18n subpage again to refresh the ext.translate (bot), and now any language got overwritten with English (I guess restoring the "bot deletion" was a very bad idea). I really do not feel like re-entering each language manually. An undo of Move or something would be very good!? PS:Maybe a detailed documentation, what is going wrong here, would be good too.

PS: I trying the Special:PageMigration thing, but I got an JS error on the page (nothing happen). I guess it comes from "mediawiki.searchSuggest" (Uncaught TypeError: Cannot read property 'indexOf' of undefined) → User: Perhelion 06:25, 30 July 2018 (UTC)

I'll look into these errors later when I have time. Perhaps there is easy way to restore the translations. Nikerabbit (talk) 15:59, 30 July 2018 (UTC)

Multilanguage import and translate

I have a 'practical' question, but i am not sure where to put it - please direct me elsewhere if this is not the correct "talk" page…

I setup a new Wiki (V1.30) on a NAS and I want to import all of a old (V1.81) Wiki - located on a PC.

The 'source language' for the wiki is 'da' (Danish), but I want to add en' (English) as an option - so I guess that i need to prepare a bit to get that right…

I have some 2-400 Wiki pages of English text… that I want to import and then translate. For that I need to import the pages to say wiki/n1:whatever/en - but when I translate this, to 'da' ,will that then end up in \whatever\dk or will it go in \whatever… ?

Furthermore - I need to split up these pages into namespaces (like, n1:, n2:, n3:… say I will have a name space like this: wiki/n1:whatever\en

My general questions are:

• Can I somehow import texts to land in the "correct" place...
  • wiki/n1:whatever1/en
  • wiki/n1:whatever2/en etc.

When i translate from the /en version, where will this end.. and will the Wiki work with a mix of /da, /en and <source language> pages…  what happens if there are the following page combinations at the same time:

wiki/n1:whatever1/en the english page

wiki/n1:whatever1/da page in danish

wiki/n1:whatever1 - standard name for the 'n1:whatever1' page, should also be in Danish

_{p.s. I did this interface to goggeltranslate at some time in the past. https://www.mediawiki.org/w/index.php?oldid=1351872} AssetDenmark (talk) 12:41, 8 October 2018 (UTC)

I would do it like this:

1. Import all English pages into the wiki in a way you want (no language codes in the page names)
2. Mark them translatable
3. "Translate" them to English by just copying the source text
4. Translate the source text page into Danish manually
5. Re-mark the source page for translation
6. Mark the English translations as non-fuzzy Nikerabbit (talk) 06:36, 9 October 2018 (UTC)

Naturally! Clever.. :-) - could have thought about that, but would I have.. before it was too late?

Than How do I handle the 'da' language tags - the "source languag" will be Danish, so can I simply translate to a page "without" the page name language code? Over time the wiki would probably contain a mix of no-tag, da and en - but can I do anything to prevent that from happening...

I guess I could leave out the 'da' option all together.. but will that create oher issues? AssetDenmark (talk) 10:42, 9 October 2018 (UTC)

The system will create /en and /da pages for you. There will be no automatically generated links to /da, because links to that language will point to the page without language code. Nikerabbit (talk) 16:03, 9 October 2018 (UTC)

Not done - yet - but now I have a Wiki up, and I am trying to bend my head around the translate bundle!

My challenge, still, that I do have some 200 word documents in uncomplicated English . These should be transferred to a the wiki as-is and then translated into danish.. I just wonder how to do this in some way that will give a simple workflow, and the least amount of work.

Going from @Nikerabbit's idea - still nagging me that I did not think of that - I get to this rough solution:

What if, I can make a few changes to the [[Help:WordToWiki#Word2MediaWikiPlus|Word2Wiki]], so the result is pages that have been marked for translation into 'da' (Danish) and with the page language 'en' (English)... and they will be imported to the Wiki, using the import translations function (probably, if that makes sense?).

So - if the import function works as if an editor did the pages (?: if not so I would need to make a special import!) - the pages should be automatically marked for translation (into 'da'...) ..

I just wonder if either of the import functions would behave like I want it to, or if there is a need to "post-process" the pages.

To spice things up a bit, this all have to end up in a dedicated namespace, I wonder if that will pose some extra challenges?

AssetDenmark (talk) 16:37, 11 April 2019 (UTC)

Source page language differs from the wiki language

Wiki language = English

Suppose there is a page LifeOfCats

Special:MyLangauge works like this:

LifeOfCats = English

LifeOfCats/fr = French

LifeOfCats/ru = Russian

If I create a page in Russian, it should obviously be LifeOfCats/ru

When I translate it into English, I want that the parent page LifeOfCats to be created. But there is no such possibility.

If I create LifeOfCats/ru and assign it the language Russian, then the translation into English produces LifeOfCats/ru/en. It is wrong. The English version must be LifeOfCats - the parent page relative to other languages. Only then will the hierarchy of translations and Special: MyLanguage work correctly

Is there an easy way to create pages with a source language different from the wiki language so that they can be translated? Axdr (talk) 21:03, 26 January 2019 (UTC)

Special:PageLanguage, accesible from "Page information", should do the trick (live example). Matěj Suchánek (talk) 09:30, 27 January 2019 (UTC)

I solved this problem with "Shaman's Magic Tambourine".

Does it make sense to publish the algorithm here in the discussion? Axdr (talk) 03:02, 28 January 2019 (UTC)

I'm interested in what that means... Matěj Suchánek (talk) 12:43, 28 January 2019 (UTC)

When the source text is created in another language, there is an algorithm that will help translate it into the main language and at the same time maintain the correct page hierarchy, as well as ensure the proper operation of the Special:MyLanguage links. Axdr (talk) 19:49, 28 January 2019 (UTC)

Just in case still helpful, there are docs on the Special:PageLanguage feature at Manual:Language#Page_content_language - see the subsection "Manually changing page language". –Quiddity (talk) 23:14, 3 February 2019 (UTC)

Process for migrating translated pages between wikis?

Can someone please explain the process to move a set of translated pages from one wiki to another? There are numbers of templates and translated pages that I wish to bring to wikimaniawiki from meta and the like. The xml import doesn't allow the writing of the Translations: ns. pages, and I cannot tell whether that is a straight permissions issue, or whether it is wanting to see pre-existing files prior to occuring. The export translations function seems to be a one translation in one language at a time process. Help pages don't seem to overtly cover this, or I am completely misunderstanding. Thanks for any direction. — billinghurst sDrewth 12:08, 16 February 2019 (UTC)

The XML import should work in case you have first copied the source page(s) and marked them for translation. Nikerabbit (talk) 07:12, 26 February 2019 (UTC)

What determines the list of languages into which translation is allowed?

Sorry if the answer is obvious. I couldn't remember and couldn't find the answer within a few minutes of searching.

I'm not talking about the list of priority/allowed languages you can set for a specific page. I mean the set of languages you can use in general. πr² (t • c) 01:14, 21 April 2019 (UTC)

I'm not sure if this is the exact right list (perhaps Wikimedia supports more or fewer languages than MediaWiki does by default?) but the list I know of is at https://phabricator.wikimedia.org/source/mediawiki/browse/master/languages/data/Names.php

Further clues might be found in Manual:Language#Names.php and in Manual:$wgExtraLanguageNames Quiddity (WMF) (talk) 03:49, 21 April 2019 (UTC)

How to export source and translated pages to another wiki?

Hello,

I need to transfer pages in source language (French) together with their translated versions (English) to another wiki. When I use the Export Pages feature of the wiki it seems that some information is missing. Is there some additional data that I need to export like for example information in specific mysql tables? Or how would you do it? Rdal (MS) (talk) 13:54, 6 June 2019 (UTC)

What information is missing? Do you want to transfer them just for reading or actually move them to another wiki permanently and continue translating there? Nikerabbit (talk) 14:44, 6 June 2019 (UTC)

I know the language selector is missing and maybe other things. I need to move them permanently. The Translate extension is installed on both wikis. Is there any info in database tables that is not exported when you use the Export Pages feature? Rdal (MS) (talk) 15:03, 6 June 2019 (UTC)

There is plenty. But if you just mark the page translatable again on the new wiki, it should get pretty close to the state compared of trying to manually port info from the database tables. Nikerabbit (talk) 08:05, 7 June 2019 (UTC)

Do you mean that if I mark an exported page as "translatable" again on the new wiki, the link between the different translations of the same page will be restored? Rdal (MS) (talk) 13:53, 13 June 2019 (UTC)

Yes, assuming you also exported the translation units from the Translations: namespace. Nikerabbit (talk) 09:50, 18 June 2019 (UTC)

Semantic MediaWiki compatibility

Hi,

I was wondering the following:

I have a page with Semantic properties. When I translate this page to another language, the Semantic properties are copied as well. My goal is to ensure that, when the properties are changed in the source page, that they are automatically updated in the translated page as well.

Is there any feature that supports this? Marlonke (talk) 08:55, 28 October 2019 (UTC)

Can you give an example? If they do not depend on a language, just put them outside <translate> tags and they are automatically copied when page is marked for translation. Nikerabbit (talk) 16:23, 28 October 2019 (UTC)

Thanks for your reply, Nike. We appreciate it. Just to be clear, we're running Semantic MediaWiki.

I have a 'Context' property on a page. When initially creating the translated versions of the page, the property and value of this property ('situation') is copied correctly. However, what we aim for is that, when the value of the property of the source page (if we change the Context property's value to 'role' in the source page source code) - or if a new one is added - that the derived translated page automatically reflect this change as well.

In essence, we want it so that if properties are added, edited or deleted on the source page, it also automatically does this on the translated pages. Consistent semantic properties are a staple of our current work philosophy, and we want our users to have to do as little work as possible. Marlonke (talk) 07:56, 29 October 2019 (UTC)

Currently translatable pages must be re-marked manually to update translation pages. Perhaps you want to have it possible to automate that.

Not sure if it works in your use case, but I believe if those values could be set via a template, then the same effect could be had by just updating that template. Nikerabbit (talk) 14:26, 30 October 2019 (UTC)

We do use plenty of templates, but they are more akin to categories rather than managers of individual pages. I am probably going to look into automating the process of updating semantic properties whenever properties on a source page are edited. I've looked at some of the hooks of the Translate extension, and I think we can make it work somehow.

Thanks for your time, we really appreciate it. Marlonke (talk) 14:44, 30 October 2019 (UTC)

Is it possible to use interwiki links?

I have 5 different wikis connected with interwiki links. (EN, DE, FR, ES, RU)

Let's say write a page in EN and mark it for translation. Every translation should not be displayed under {PAGENAME}/DE and so on, but the translated pagename under the de.mywiki.de/{PAGENAME}. Is this possible?

If so, then if someone write a page in FR for example and mark it for translation in EN only. After translation into EN, the source page have to be changed to the EN one and the FR page to the translated one. From now on the EN page will be translated to the other LANG Wikis. Is this somehow possible?

Thanks for answering :-) 90.186.253.229 (talk) 03:01, 2 November 2019 (UTC)

About Chinese Translation

The extension disabled translation to zh-hans and zh-hant, but most pages or interfaces have zh-hans or zh-hant versions, and they would shown in English by default, with 0% translation (Like the main page Template:Main page/zh-hans and Common's rename template Rename/i18n/zh-hans). Tim Wu (talk) 12:32, 28 December 2019 (UTC)

It is not disabled by the extension, but by its Wikimedia configuration. zh is available with language conversion, as far as I know. Nikerabbit (talk) 08:40, 31 December 2019 (UTC)

Add uselang to language switcher

Is there a way to force the uselang parameter to be added to links in the language switcher?

I apologize if this is already written somewhere, but I spent a few hours and can not find information on this issue. 91.214.30.198 (talk) 13:37, 3 February 2020 (UTC)

I am not sure what you mean, but you could set

$wgTranslatePageTranslationULS = true; Nikerabbit (talk) 11:31, 7 February 2020 (UTC)

bar disappears after switching language

The <languages /> tag does need to be included in the translation. But you need to do a dummy edit to get it to show up.

I have added the <languages /> tag to my english main page. And it displays the languages i have converted to.

However when I click on a different language, it takes me to the translated version of that page but the languages bar has

disappeared. I cant browse back to English.

I've tried to wrap the Languages inside of the translate and outside of it. Neither work.

I've tried to add it onto the translated text but it then has a broken element. I have scoured here and I cant seem to find a fix for this. BensDBN (talk) 10:40, 3 June 2020 (UTC)

See the following pages:

• https://www.mediawiki.org/w/index.php?title=Professional_development_and_consulting&action=history
• https://www.mediawiki.org/w/index.php?title=Professional_development_and_consulting/ja&action=history

A dummy edit is REQUIRED to update translation pages :( Shirayuki (talk) 10:54, 3 June 2020 (UTC)

Hi Shirayuki,

Sorry i'm not expert of the mediawiki but I did not understand what I have to change in order to adjust my page that has the same error.

thanks in advance Tambmar (talk) 14:37, 21 August 2020 (UTC)

Re-marking the page for translation is required to update translation pages. Shirayuki (talk) 21:55, 21 August 2020 (UTC)

Hi Shirayuki

Thanks for the help. It worked. BensDBN (talk) 12:17, 3 June 2020 (UTC)

$wgTranslatePageTranslationULS doesn't do anything

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.

---

Hello, on my wiki (https://jojowiki.com), setting the language using ULS doesn't seem to redirect to that page's language when clicking a link. For example, clicking a "Star Platinum" link or searching for that page just goes to the English page even though there are French, Italian, and Russian translations. Any way to fix this? Vishkujo (talk) 08:12, 9 August 2020 (UTC)

You need to use Special:MyLanguage/PageName to produce such language-aware links.

The configuration option only configures whether that happens for the current page automatically when changing the interface language. Nikerabbit (talk) 13:46, 9 August 2020 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Hyperlinks dont work

When I try to use hyper links, I get an error. Dunno but other people can use hyper links in translate 89.42.63.47 (talk) 12:05, 20 August 2020 (UTC)

How to split a page into two and keep the translations for the "new" page?

As part of phab:T250700 I am thinking of moving the section How_to_become_a_MediaWiki_hacker#Communication_tips_and_guidelines (which is simply not a "MediaWiki only" thing, so it's at the wrong place) to a better place, probably New_Developers/Communication_guidelines. And after that, transclude that page into several pages.

How can I take all and any existing 25 translations for those strings that are part of that section with me?

Stuff like Help:Extension:Translate/Move_translatable_page only explains moving a complete page, but here I'm after splitting.

Any best practices documented somewhere?

Thanks in advance! AKlapper (WMF) (talk) 14:53, 30 October 2020 (UTC)

I am afraid there is no support/help for this use case currently. Basically you need to move the relevant source language parts to the new page (keeping the existing ID markers if you wish), mark it for translation and then copy over each translation. Last part can probably be automated with pywikibot or similar and a bit of scripting. Nikerabbit (talk) 12:49, 4 November 2020 (UTC)

Disable Edit/Create Source but Enable Translate

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.

---

I would like to disable users from editing the source text for all pages in my wiki but still allow them to publish translations. Whenever I add $wgGroupPermissions['user']['edit'] = false; to Local Settings.php and $wgGroupPermissions['user']['translate'] = true; it comes up with the error "Publishing the translation failed: The action you have requested is limited to users in the group: Administrators." Is there any way to allow translators to publish translations without allowing them to edit the source text of a page?

Thanks in advance for any help you can provide! Nstrole (talk) 18:09, 16 December 2020 (UTC)

I would simply use the protect feature to protect the source pages.

Another option would be to restrict editing using $wgNamespaceProtection in namespaces other than Translations:. Nikerabbit (talk) 07:04, 17 December 2020 (UTC)

The protect feature did the job. Thank you so much! Nstrole (talk) 18:06, 17 December 2020 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

FuzzyBot Deleting Pages

In an effort to minimize the number of modifications made to a page marked for translation on my wiki, I started deleting pages and then recreating them with updated content. We are still in draft mode on our wiki, so I figured deleting pages would be the cleanest way to make sure the source text and translations were up to date. I have also found that editing a page marked for translation creates multiple versions of that page in the category pages ("[pagename]," "[pagename]/en," "[pagename]/fr," etc.). Deleting and recreating these pages seemed to be the best way to prevent these problems from happening.

However, hours (or even days) after recreating and marking for translation pages that have been deleted, FuzzyBot deletes the pages again. Should I have not deleted these pages in the first place? Is there a better way to go about editing a page marked for translation without causing the errors recounted above? To prevent FuzzyBot from deleting the pages again, should I restore the original pages I deleted and then edit them?

Thank you for any advice you can give! Nstrole (talk) 16:50, 18 December 2020 (UTC)

FuzzyBot automatically manages translation pages, and the best thing to do is to leave FuzzyBot to do its work and not touch translation-related pages manually. FuzzyBot relies at the job queue – if you feel it takes a lot of time to FuzzyBot to delete pages, once you perform an action as a translation administrator, it's possible that the job queue is being slow for your wiki Martin Urbanec (talk) 18:50, 18 December 2020 (UTC)

How to move a translated subpage?

My use case: somebody used the wrong language code, “zh-hans”, to translate a page. I need to move that to “zh-cn”. The documentation doesn’t cover that case. Renamed user 23o2iqy4ewqoiudh (talk) 20:11, 2 January 2021 (UTC)

OK, the way I did it is, I moved (without leaving a redirect) all of the translation-unit subpages, one by one (there can be hundreds!) and deleted the translated page with the wrong code. Then, in order to nod the Translate extension to refresh, I made a trivial edit to one of the newly moved translation units. This created a new translated page at zh-cn; however, the page has none of the history of the previous page, and the extension doesn’t allow me to restore the history entries neither by using Special:MergeHistory or by manually restoring entries. Yet another one of this extension’s many grave defects. Renamed user 23o2iqy4ewqoiudh (talk) 21:07, 2 January 2021 (UTC)

You could have unmarked the page for translation and moved the translation page as well.

But why is the lack of history of the translation page a grave defect? Nikerabbit (talk) 13:36, 5 January 2021 (UTC)

Everytime I publish a translation the api.php returns "permissiondenied"

I have all the group permissions set to true (I've even tried it with the "*" group), but everytime someone tries to publish a translation the translated text is yellow and in the browser's network tab, the api.php POST returns:

code: "permissiondenied", info: "You are not allowed to execute the action you have requested."

I'm not sure what I'm doing wrong 98.0.152.222 (talk) 15:17, 5 February 2021 (UTC)

See Help:Extension:Translate/Configuration#Sample configuration. If that doesn't work, you mave have some other extension that is causing problems. What are you translating? Pages? Nikerabbit (talk) 20:13, 5 February 2021 (UTC)

Yeah I have all of those entries in my LocalSettings.php. We have other extensions but I've already tried turning them off and was still getting the permissions error. The guide that I followed wanted to load a bunch of other extensions:

wfLoadExtension( 'Babel' );
               
wfLoadExtension( 'cldr' );
               
wfLoadExtension( 'CleanChanges' );
$wgCCTrailerFilter = true;
$wgCCUserFilter = false;
$wgDefaultUserOptions['usenewrc'] = 1;
            
wfLoadExtension( 'LocalisationUpdate' );
$wgLocalisationUpdateDirectory = "$IP/cache";
               
wfLoadExtension( 'Translate' );
$wgGroupPermissions['Translators']['skipcaptcha'] = true;
$wgGroupPermissions['Translators']['translate'] = true;
$wgGroupPermissions['Translators']['translate-messagereview'] = true;
$wgGroupPermissions['Translators']['translate-groupreview'] = true;
$wgGroupPermissions['Translators']['translate-import'] = true;
$wgGroupPermissions['Translators']['pagetranslation'] = true;
$wgGroupPermissions['sysop']['pagetranslation'] = true;
$wgGroupPermissions['sysop']['translate-manage'] = true;
$wgTranslateDocumentationLanguageCode = 'qqq';
$wgExtraLanguageNames['qqq'] = 'Message documentation'; # No linguistic content. Used for documenting messages
wfLoadExtension( 'UniversalLanguageSelector' );

98.0.152.222 (talk) 00:17, 7 February 2021 (UTC)

I don't have other ideas then. Do note that MediaWiki namespace has restricted editing. Nikerabbit (talk) 10:43, 8 February 2021 (UTC)

Translate + VisualEditor, not working?

After wrap the text by "<translate>" & "</translate>" to the entire paragraph, enter edit mode,

message prompts: "You are editing a translatable page. Editing these in this editor is not yet officially supported."

MLBP version: 2021.01

Mediawiki version: 1.34.12

php version: 7.3.20

MySQL: 5.7.31

VisualEditor version: 1.35

Is it a know-problem w/o fix? my users is general clerical users, it would be difficult to persuade them to input w/o rich-text editing or MSWord-style editing Lamjon (talk) 04:04, 10 March 2021 (UTC)

It's known. See MediaWiki Stakeholders' Group/TechConf Input#Improved Translate - VisualEditor integration for example.

We are currently working on some changes for better integration with MediaWiki parser. Work to improve VE support is expected to happen some time after that, but there is no estimate as of now. Nikerabbit (talk) 09:19, 10 March 2021 (UTC)

Unaccesible page Special:SearchTranslations

I have installed extension Translate from 2019-07-22 (3da1d7c). Page is in code, but Special page not accessible because wiki does not have a translation search service. What I must set for available it? Thank you – Want (talk) 12:06, 13 March 2021 (UTC)

It requires ElasticSearch. Please see Help:Extension:Translate/Translation memories. Nikerabbit (talk) 11:16, 15 March 2021 (UTC)

Thank you about your answer. But ElasticSearch isn't open source solution, and in addition depends on java engine. Exist any alternative for it? Want (talk) 11:53, 15 March 2021 (UTC)

The currently supported versions of ElasticSearch are open source. 7.x is not yet supported. The future is still unclear, but perhaps there will be open source fork of ElasticSearch.

It's not worth the effort for us to write a search engine ourselves. Besides, MediaWiki itself requires ElasticSearch for advanced search features. Nikerabbit (talk) 14:41, 15 March 2021 (UTC)

Thank you for the explanation. Want (talk) 16:29, 15 March 2021 (UTC)

Chinese

Hi Someone told me that Translate does not support the various chinese languages zh-tw, etc ? Bouzinac (talk) 21:57, 6 April 2021 (UTC)

Translate supports any language. Perhaps they mean the configuration at Wikimedia wikis? Nikerabbit (talk) 06:07, 9 April 2021 (UTC)

Hi Tacsipacsi, could you specify examples of not working chinese with this Translate ? Bouzinac (talk) 06:33, 9 April 2021 (UTC)

Translation into Chinese variants like zh-tw, zh-hans etc. is disabled on Special:Translate. (I don’t know if it’s a Wikimedia setting or Translate’s default setting, but it doesn’t matter either.) This is fine as long as one translates pages, since the variant selector appears on the top (and I’m pretty sure this is why the manual translation into variants is disabled). However, it doesn’t work, at least not out of the box, in templates unless they are used on such extension-translated pages. These templates may be used on pages that are translated manually, without the Translate extension (these should be converted to the extension in the long run), or may be used on non-translatable pages like talk pages or file description pages (these usually use the user interface language with the {{int:lang}} hack, and won’t be converted to the extension ever, so probably they won’t variant selectors). I’ve read about the <langconvert> parser tag, which may solve the issue if it’s built into {{TNT }} et al., but haven’t got around trying it yet. (The thing I’m worried about is that, according to the Phabricator task, it expects a variant identifier as the input variant, but {{TNT }} only knows that it’s some variant of zh.) Tacsipacsi (talk) 23:07, 9 April 2021 (UTC)

Using current page language instead of Special:MyLanguage for links

Hello,

we have been using syntax like this for links

[[Special:MyLanguage/Getting Started|<translate>[[Special:MyLanguage/Getting Started|<translate><!--T:55--> Getting Started</translate>]]</translate>]]

But the problem is that if the user clicks any link it will redirect to the user language, not the current document language. Is there a way to use something like

[[Getting Started/{{TRANSLATIONLANGUAGE}}|<translate>Getting Started</translate>]]<translate><!--T:55--> Getting Started</translate></translate>]]

I saw that with this commit https://phabricator.wikimedia.org/rETRA5e8106cdc353294bb97b626fbd1bf46c860ebb02 it was introduced but cannot find it in the current release.

TLDR: I want easily maintainable links which automatically point to the page of the current document language, NOT user language.

Any insight would be very helpful.

Thank you in advance. C schmitz (talk) 18:36, 25 October 2021 (UTC)

{{TRANSLATIONLANGUAGE}} only works inside translation units, and is probably not what you want anyway. You can hardcode links to [[TargetPage/{{PAGELANGUAGE}}]] if you don't mind about links pointing to non-existent pages when translation is missing. Nikerabbit (talk) 09:15, 26 October 2021 (UTC)

Thank you. It would be nice to have such an operator that, if needed, falls back to the base language, if no translation exists yet. C schmitz (talk) 07:22, 29 October 2021 (UTC)

relation "revtag" does not exist

Hi, after I installed that extension (translate), this comes up:

Sun Oct 30 18:50:24 CET 2022 debian mediawiki-public- Error 42 from TranslatablePage::getTranslatablePages, ERROR: relation "revtag" does not exist LINE 1: ...ablePage::getTranslatablePages */ rt_page FROM "revtag","...

Data are as follows:

Justman10000 (talk) 18:00, 30 October 2022 (UTC)

Did you remember to run update.php after enabling Translate?

Possibly this is specific to PostgreSQL, which we are unable to test ourselves currently. A full query and stacktrace would be helpful. Nikerabbit (talk) 12:01, 31 October 2022 (UTC)

Did you remember to run update.php after enabling Translate?

Sure, otherwise only a whitescreen came! Justman10000 (talk) 12:03, 31 October 2022 (UTC)

@Nikerabbit Justman10000 (talk) 14:02, 31 October 2022 (UTC)

Different link on translated page?

Hi there! Question, how can I change the links (non Wikimedia) on a translated page? I am currently attempting to translate this page to German and for the German version I would like to add resource links in that language. While I am able to translate all the text, I am unable to change the links. Any help would be much appreciated. Thank you so much :) MFischer (WMF) (talk) 11:37, 31 October 2022 (UTC)

This would also allow me to added correct resources in all the other languages. Thank you :) MFischer (WMF) (talk) 11:38, 31 October 2022 (UTC)

That is more of a question for translating admins in Meta to mark the page in such a way that the links can be changed. I suggest to ask it in https://meta.wikimedia.org/wiki/Meta_talk:Babylon [edit: correct link]. Nikerabbit (talk) 13:26, 31 October 2022 (UTC)

Noted, thank you kindly! MFischer (WMF) (talk) 02:33, 1 November 2022 (UTC)

Marking minor edits as not needing translation

I couldn't find anything about this feature, and I think it would be useful. If I'm editing a page that is enclosed in <translate> tags, and in one part I am making significant content changes, and in another part, I am only fixing typos or grammar, it would be nice to be able to mark the minor edits as not needing a new translation, as typo or grammar fixes probably won't affect the translation and will just waste translators' time.

For example, it could be done by placing <minoredit> tags around the grammar fix, which the Translate Extension then deletes from the source, and then it makes sure to not display the edited unit as needing translating (unless, of course, it still has major edits that need translating from prior revisions or from a different part of the unit). Cheesycow5 (talk) 02:31, 9 November 2022 (UTC)

The re-translation flag is controlled by the translation admins when they review the changes to each unit and re-mark the page for translation. Nikerabbit (talk) 10:39, 9 November 2022 (UTC)

Oh ok, thanks, that does sound like it would work well for that purpose. Cheesycow5 (talk) 17:30, 9 November 2022 (UTC)

How do I use this for a non-Mediawiki website?

I see that the documentation says "It can be used to translate the content pages, the interface of the wiki and even other software products", but I can't find any information on how to set it up for my non-Mediawiki website. Dimpizzy (talk) 23:42, 20 February 2023 (UTC)

I think it means you can use it to translate other software products, but you still need a dedicated wiki for this. See for example translatewiki.net. Matěj Suchánek (talk) 07:23, 21 February 2023 (UTC)

That is correct. It only runs on MediaWiki, but you can translate various things with it. Nikerabbit (talk) 09:19, 21 February 2023 (UTC)

Oh got it. Maybe I'll have the translatable parts of my website on a wiki just for the Translate extension, and the core of the website would use the MW API to get and insert the translated content into the website.

Edit: Oh, just realized that's what Matěj was referring to. Dimpizzy (talk) 13:08, 21 February 2023 (UTC)

Could you provide an example link to a Mediawiki instance that is connected to translatewiki.net, which is used for software interface messages? For example, where is the wiki located that maintains all the translations for the software messages of Mediawiki itself? Dimpizzy (talk) 08:37, 14 March 2023 (UTC)

The wiki that maintains translations for MediaWiki itself is translatewiki.net. Tacsipacsi (talk) 09:29, 15 March 2023 (UTC)

Oh ok, I thought translatewiki.net somehow pulled the messages to translate from another wiki hosted by Wikimedia or Mozilla, or whoever. Dimpizzy (talk) 11:38, 15 March 2023 (UTC)

There is no other wiki involved, translatewiki.net pulls the English messages and pushes the translations directly from/to Git (e.g. core repo). Tacsipacsi (talk) 11:54, 17 March 2023 (UTC)

Understood. Is there any guide on setting up a git repo and connecting it to translatewiki.net and/or a private wiki with the Translate extension? Dimpizzy (talk) 01:14, 18 March 2023 (UTC)

See translatewiki:Translating:New project about getting a project on translatewiki.net and Help:Extension:Translate about self-administered Translate extension. Tacsipacsi (talk) 19:04, 18 March 2023 (UTC)

Ok, thank you! Dimpizzy (talk) 19:09, 18 March 2023 (UTC)

Can I reuse a translation unit multiple times on the same page?

Hello! On the same page, there are 4 times the same sentence. Can I reuse the same translation unit, or do the translators have to translate the same sentence 4 times?

For future reference, someone had the same question 7 years ago, but maybe the devs created some kind of unit variable like <ref> that can be reused in the same page (example : <unit name=1$ />?

Thank you. Brochon99 (talk) 21:52, 12 March 2023 (UTC)

This is not currently a supported feature. There are some templates here and/or meta.wikimedia.org that allow referencing other translation units. Don't remember the exact names right now. Nikerabbit (talk) 14:19, 13 March 2023 (UTC)

On Meta it's m:Template:Tunit. Don't know about any similar templates on MediaWiki.org. * Pppery * _{it has begun} 01:01, 14 March 2023 (UTC)

Technically no problem, practically big problem, because in another languege may be identically TU tranlated in other sense, by context. I use templates with combination a contents of the translated pages very much. See for example page 1A and try change language of the interface to 'polski'. It's not finished page for now. It's only example, how can be generated content from translated pages by Template:svitek Want (talk) 22:15, 26 March 2023 (UTC)

Importing translation content

I manage an English wiki with 7,000 pages written in English. To enhance its bilingual nature, I've generated machine translations for all those pages. These translations are stored in text files located in separate subdirectories like "/translations/es" and "/translations/fr".

Right now whenever I import my text files into MediaWiki I use Manual:ImportTextFiles.php/, is there a certain namespace or formatting that I have to use to upload the translations?

Is there a way I can easily import these pages into the Translate Extension? MarblehorseNet (talk) 23:53, 13 June 2023 (UTC)

Importing Translation Content through CSV MarblehorseNet (talk) 18:31, 14 June 2023 (UTC)

Am I the only one who thinks this sucks?

I just expanded the Setup section of FlaggedRevs, an extension that gave me lots of problems that could have been prevented with proper instructions.

I was taken aback by these <translate> tags. I did the best I could, but I have no idea if I broke something or did something wrong. Is this really the best way to make MediaWiki multilingual? Manifestation (talk) 16:03, 31 July 2023 (UTC)

You are not the only one, though most people appreciate the value of supporting translations even though the method has shortcomings. We are exploring how to make the process better: https://meta.wikimedia.org/wiki/Research:Translatable_Pages_Research Nikerabbit (talk) 10:51, 1 August 2023 (UTC)

Thanks. User:Shirayuki has altered my edit and made it compatible with the translation system... I think.

I honestly have no idea how this convoluted system works. I can't make heads or tails of it. For example, what are these <!--T:[number]--> markers? Manifestation (talk) 13:48, 1 August 2023 (UTC)

They are explained for example in Help:Extension:Translate/Page translation example. Nikerabbit (talk) 13:23, 2 August 2023 (UTC)

Hide "Translate this page" link, or protect translations of page?

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.

---

Hi, Our main page has the following source code: <languages/><translate></translate>{{Main Page}}. So there is nothing to edit or translate (except the title "Main Page") and people should edit or translate the template instead. Is there a possibility to hide the "Translate this page" link, so I can replace it with a link to the Template? Thanks. PKFP (talk) 10:13, 25 January 2024 (UTC)

I don’t think there’s an officially supported solution for that, but I don’t think it makes sense either. You should decide whether you want the page to be translatable: if yes, the link shouldn’t be hidden; if no, the page shouldn’t be marked for translation. If nothing except for the title is translatable, then there is something that’s translatable: the title.

You have some options:

• (Supported and IMO best solution) Merge the template into the main page
• (Supported) Keep the link for translating the main page, add a link in wikitext to Special:Translate/page-Template:Main Page
• (Unsupported, I recommend against it) Add the link in wikitext and hide the link for translating the main page itself using the CSS .mw-pt-translate-header { display: none; } Tacsipacsi (talk) 10:45, 28 January 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Integrating English Articles with Polish URLs in MediaWiki

I'm managing a MediaWiki site with Polish as the primary language. However, we occasionally receive content in English that needs to be incorporated seamlessly into our site, including adopting Polish page titles/URLs without the "/pl" suffix typically used for translated content. For example, I wish to translate the title "My new page" from English to Polish and use it as the main content, ensuring the URL reflects the Polish version without indicating it's a translation. Our site primarily translates content from English (or Spanish) to Polish, displaying it in Polish by default. I'm looking for advice on how to manually mark these articles for translation and adjust their URLs to blend with our Polish content. Any suggestions on setting this up efficiently would be greatly appreciated. Jacekpoleszak (talk) 13:46, 13 February 2024 (UTC)

That's not supported by the Translate extension because general solution is not possible due to naming conflicts. You can create redirects manually. Nikerabbit (talk) 14:49, 13 February 2024 (UTC)

Page named Resources

I have a page called "Resources", English version of it works fine, but any translated not,

I believe it's because resources is one of the folders in mediawiki engine, and when that page gets translated, it changes to /wiki/Resources/de

Is there any solution for this, how to fix that in .htaccess? Or renaming the page is the only way? 193.91.164.56 (talk) 22:34, 26 April 2024 (UTC)

fixed 193.91.164.56 (talk) 12:48, 27 April 2024 (UTC)

Sidebars

Hey,

Is it not possible to translate Sidebar without ULS? Truemib (talk) 20:27, 1 May 2024 (UTC)

After update MW 1.35 -> 1.42 translation editor is not displayed..

Hi, today I've updated my wiki and all the extensions. Everything is wokring so far. But when clicking on translate button for a site, it will only show an empty section. I.e. clicking 2A02:810D:6040:64A:96A:ACCF:4337:2214 (talk) 20:09, 9 August 2024 (UTC)

translate on the page "Manuals:Test" will lead to ".../index.php?title=Special:Translate&group=page-Manuals%3ATest&action=page&filter=".

Here it only shows "Translate to German" (I'm from Germany). But the editor to translate is missing. Also I can't select any other language to translate to. As far as I can remember I could select any language before.

The above buttons also work, I can view the translation stats. Here all my sites are shown as translated.

What is missing here? Checking the debug log and console did not give me any clue. Please help, thanks!! 2A02:810D:6040:64A:96A:ACCF:4337:2214 (talk) 20:17, 9 August 2024 (UTC)

It sounds much like a JavaScript problem. Maybe the upgrade coincided with you disabling JavaScript (using NoScript, browser preferences etc.)? Or there is some JavaScript error on the browser console? If your wiki is publicly available, it would make debugging a lot easier if you could share its URL. Tacsipacsi (talk) 09:28, 14 August 2024 (UTC)

Please enable subcategorizing translated pages on Commons

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.

---

See meta:Community Wishlist/Wishes/Enable subcategorizing translated pages on Commons. I think that's currently not possible but if it is, users can't do so and it's not done automatically. Prototyperspective (talk) 22:32, 21 October 2024 (UTC)

The Translate extension does not handle categories in a special way. That's why we have left it up to translation admins to decide whether they want all translations to be in one category or in separate language categories and this is reflected in our documentation: Help:Extension:Translate/Page translation administration#Markup examples.

This might change a little in the future if https://phabricator.wikimedia.org/T285463 gets implemented. Nikerabbit (talk) 13:45, 23 October 2024 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

How to set the page display title of the source translation?

E.g. for Commons:De minimis the wish is to italicize the latin phrase "de minimis". I can let the Danish translation display Commons:De minimis/da , but how do I do the same for the English version? I'm not allowed to edit Translations:Commons:De minimis/Page display title/en directly. Bdijkstra (talk) 19:37, 28 February 2025 (UTC)

Use the {{DISPLAYTITLE}} parser function (wrapping it in an if statement only if {{#translation:}}) is empty), the same way as if Translate wasn't enabled. * Pppery * _{it has begun} 19:41, 28 February 2025 (UTC)

That works, thanks! Bdijkstra (talk) 20:13, 28 February 2025 (UTC)

Is it wise to add among tvar tags?

I find tree tvar tags that is not conveyed from an /en page to /ja equivalent. [6]. My question is if the prevents the matching?

• Three (3) short forms/switches need to be updated :
• $1: emergency;
• $2: human rights;
• $3: ca : or;

• better input as Checkuser actions?

Would you have a look please? cc:@Uzoma, kindly, Omotecho (talk) 01:53, 7 July 2025 (UTC)

I’m not sure I understand you. The bullet points part of your comment is totally unclear for me.

By “tvar tags that is not conveyed from an /en page to /ja equivalent”, you mean that they don’t result in clickable links? That’s because they’re not meant to be used as links: the they lack the mailto: prefix, they lack the domain name and they use an image instead of an @ character (whose purpose is exactly to make it less machine-readable, as a countermeasure against spam bots, but also preventing clickable links) – all these have nothing to do with the Translate system, and would also happen if you copied and pasted the wiki code into a manually translated page. —Tacsipacsi (talk) Tacsipacsi (talk) 21:11, 8 July 2025 (UTC)

What's undeniable is that the English document makes things unnecessarily harder for translators when one could simply use e.g. "[[$1|emergency channel]]" and have a harcoded target (if that's wanted) while you still let them translate things properly. Someone said "wiki markup should be kept simple" but maybe nobody told the author(s) of that page.

Edit: I have notified the original author about it, but by past experiences with WMF staff I wouldn't hold my breath. --Tactica (talk) 22:12, 8 July 2025 (UTC)

Hi, @Omotecho. Those strings are meant to represent email addresses. I've changed the strings to use the full address now, which should make things clearer for everyone.

[For background context/trivia: "ca@" is a reference to the very old name of the "Trust and Safety" team, which used to be named "Community Advocacy" until ~2016 (see the disambiguation page CA for example). It is not a reference to checkusers. The email address has just stayed the same over the years, in order to keep things things like this consistent and to minimize changes elsewhere.]

@Tactica thank you for the notification about the ongoing discussion to allow us to clear up this confusion, though that final comment doesn't feel in good faith.

Thanks again, all. Quiddity (WMF) (talk) 18:17, 9 July 2025 (UTC)

That comment was addressed at the WMF staff in a broad sense, not implying anyone in particular, and meant to tell you that you have to do things better. I know that expecting fast action when problems are reported isn't realistic neither here or in any "big" organisation, but it's frustrating when you report trouble with more than enough time for solutions to be implemented and yet nothing is done, no matter how trivial the issue is (example 1) (example 2a, 2b). But getting back on topic, as far as translations is concerned the situation here IMO is hopeless as most vandalism affecting them isn't reverted, partly I guess because the way the extension works spammers have it much easier to do their business than rollbackers and casual reverters. Tactica (talk) 19:43, 9 July 2025 (UTC)

I understand the frustration, we are all (as volunteers and as affiliate or foundation staff) trying to do many more things than are possible. We have big dreams/goals, and we're great at noticing imperfect details! Similar problems occur for every big "open" project (e.g. some of the bugs and feature-requests I've submitted for things unrelated to Wikimedia, like Firefox, that remain open many years later).

The topic of vandalism in translations seems to be unrelated to this thread. Perhaps you may like to start a new section if you'd like to discuss or ask any questions about that?

Re: Your example 2, I've fixed the link and left a comment in the thread, using my volunteer account. I hope that helps. Quiddity (WMF) (talk) 20:10, 9 July 2025 (UTC)

It does. Thank you. Tactica (talk) 23:07, 9 July 2025 (UTC)

Thank you all to check on each hick-up notes like mine (;. My input is based on a background of a wiki editor turned translator for the Movement. Terminology is among the keys I rely on, and CA vs CU mentioned above: misleading of this kind is hopeless when you translate, or shame on me.

I'll be honest. I don't believe for Foundation staff and service providers, including translators, the golden rule for wikis apply: "Be bald at editing/writing wikis, and somebody will come and correct mistakes". That said:

• Could we have a proofreading team on the Foundation team, on the thread hold of giving out pages and announcements?

Feels very strange that a NPO with recognizable impact on the Internet goes "naked" for its official pages. Our readers, including donors, should not be mislead by "mistranslation" or incorrect wording at the first stage.

• Are those contracted with the Foundation given effective initiation to write/edit on wikis?

FYI, on major Wikimedia wikis, newly started editors are given self-tutoring extension. And pat-on-the-shoulder on Wikipedia Apps.

Let's be realistic.

• Do we have any data how far energy loss is generated by careless/ untutored changes to translation-source pages?

Obstacles to other people's tasks cause frictions, not only to translators and translate-admins, but how far?

Being inclusive and universal is among the goals we look after towards 2030. Maybe it needs us to bridge the minds/customs of wiki editors and those tasked to announce on behalf of our Movement.

How do we look at the same thing and be proud of being inclusive and accessible, move on to discussion, if we apply jargons that put ppl off the wagon? Cheers, --Omotecho (talk) 05:30, 10 July 2025 (UTC)

Where is our official thesaurus?

Working on translation for Wikimedia and Mediawiki pages, we need a common "dictionary" for Wikimedia terms / words. And do we have one?

(A few discussion came before this post including: #Is it wise to add among tvar tags?)

Or, when will we be safe to tell ourselves "Here, this is TermBase, our common thesaurus or Movement Dictionary": are we safe doing so, without maintainers?

• Which and when Foundation team surrogate the TermBase as the maintainer, being orphaned and put to hibernating after the caretaking team was disbanded?
• Do we plan to cover so many languages yet to be included as the target language? Is it feasible on volunteer endeavor?

I wonder if TermBase has not been told to people because maintaining is unrealistic. How do we catch up before 2030 with some strategic approach / timeline and build a universal thesaurus ?

I dream of a page you come and learn Wikimedia way of looking at the world. --Omotecho (talk) 06:02, 10 July 2025 (UTC)

I posted a related proposal here but so far there has been no interest. Or maybe I should move it to a more prominent place, but where exactly? Tactica (talk) 10:39, 10 July 2025 (UTC)

Glossaries of terms in the Wikimedia are much-needed, but not as well-organized as they should be. I wish that this area was better organized, and I try to contribute to it whenever I can, but it's a big undertaking.

On Wikidata, there's the item Project:Glossary (Q1389361) for glossary pages on specific wikis. Some of them are quite well-developed.

There's the translatewiki:Translating:MediaWiki/Basic glossary page, which I started on translatewiki (in fact, @Omotecho translated some of it into Japanese). It's intentionally far from being a complete glossary because I tried to make it friendly to new translators and users (and "new" here means not only "new on translatewiki", but also new in reading and editing Wikipedia and even in using computers and the web).

There's the page Manual:Glossary, which is more technical.

Some extensions and projects have their own specific glossaries, like Wikidata, Wikidata Lexemes, and Wikifunctions.

There's the m:Glossary on Meta, which is supposed to be universal, and has a lot of useful things, but it is also not complete.

A particular problem is that some concepts in our terminology are universal, such as "Edit", "Category", "Template", and "Upload", and some are familiar only in a few languages. For example, the terms "MFD" and "MOS" are important in the English Wikipedia, and in several other large languages, but are not so relevant in smaller languages, at least for now, because the need for them has to develop over time. Amir E. Aharoni {{🌎🌍🌏}} 14:21, 14 July 2025 (UTC)

@Amire80 and @Tactica, thank you so much for your input. Wow, there are so much treasure troves, and I totally overlooked how rich Wikidata is with those terminology pages.

What a big undertaking, I agree, as myself coined terms in Japanese years back, then I "wrecked my back" that technical terms were all Latin to me. Some were bound to specific period of our history, or near distinct as the Foundation had evolved: new terms such as UCoC had been coined and accumulated rapidly.

The landscape looks to me that drawing a map of thesauri is near unaccessible task, however, chicken or egg, aren't those terms so varied or multiple terms holding very similar meaning, since there is not a global/universal container to organize those terms?

The following is what Amire80 has shared the wisdom, put into dagger list by project.

• Wikidata
  • item Project:Glossary (Q1389361)
  • for glossary pages on specific wikis. Some of them are quite well-developed.
  • Wikidata
  • Wikidata Lexemes
• translatewiki:Translating:MediaWiki/Basic glossary page
  • for en-ja-en, Translatewiki : terminology;
  • newly started editors / readers in mind.
• Manual:Glossary
  • more technical.

Extensions and projects

Some has their own specific glossaries:

• Wikifunctions
• m:Glossary
• m:Termbase

For Japanese readers

(c&p from my m:Userpage Glossaries.)

Not being sorted out at yet with a single dicipline.

• mw:Growth/newcomer’s glossary - draft especially centered newcomer editors in mind, mirroring Personal Homepage or Suggested Edits;

topic/theme specific

• meta:Privacy_policy in ja;
• meta:Recommendations/Glossary/ja for the Movement Strategy;
• mw:VisualEditor/dev glossary
• meta:Wikimedia grants specific glossary
  • (see also m:the Draft, Funds_Dissemination_Committee)
• jawp:Handbook for Wikimedia Movement Implementation Grants (draft)
  • ja-en, en-ja glossary centered around Grants program, which calls for understanding UCoC and Wikimedia Movement Implementation, and Initiatives.

I remember the frustration at jawp when we had discussions on Foundation jargons, so to speak, which produced a terminology page on jawp, because more users gave us wisdom on translating terms and offering their private lists. At the voting, when Foundation Board encouraged us to verify our thoughts on the Movement. A record breaking volume of votes from Japanese speaking users were cast (3,000?).

I miss TermBase, which was small but focused, and had a bit of universality, to try and bridging editor-MMF team members, with starting editors also in sight.

How can we thread through those "Gems"^※ which might be sleeping at the elbow of us working on translation?

Are we safe discussing big project as Wikimedia without common book of terms, I wonder.

("※" off-topic, there was a miniature pocket dictionary titled "Gems" back in 1980s ;) )

Omotecho (talk) 16:16, 14 July 2025 (UTC)

"Small and focused" is probably the key because otherwise you risk ending up with tasks like the one linked by TBurmeister (WMF) below that stall for years (or even decades when changes to MW core functionality are involved). If something with a comparatively small scope like a MoS for translating this site is uninteresting⁽¹⁾ I don't see any grandiose WM Movement thing getting anywhere no matter how fancy your HTML looks in the mandatory 50K project page, but then again ICBW.

⁽¹⁾ Or maybe most translators (and LAs) simply prefer the status quo where everyone and their dog is free to translate as they please. Why should I support imposing rules when anarchy is simpler...?. In that case decisions from the higher ups are required. Tactica (talk) 17:17, 20 July 2025 (UTC)

https://phabricator.wikimedia.org/T150263 is a related Phabricator task (thanks to @Quiddity (WMF) for updating the task to note the discussion happening here). TBurmeister (WMF) (talk) 20:02, 18 July 2025 (UTC)

list of languages?

I asked this somewhere else, but I just want to check over here, since there seems to be more activity. I know https://translatewiki.net/wiki/Special:ActiveLanguages, but is there a list of ALL MediaWiki languages, in a table or list? I know I saw it one time, but I haven't been able to find it since. Is there any list? Is this the right place to ask? If not, I can move this if needed. AtTheTownHouse (talk) 02:55, 30 September 2025 (UTC)