Help talk:Extension:Translate

Jump to: navigation, search

About this board

By clicking "Add topic", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 3.0 License and GFDL

api error "nomessagefortitle" (2016.04)

Andreas Plank (talkcontribs)


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

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

Nikerabbit (talkcontribs)

Please check whether emptying the JobQueue fixes this error. You can run jobqueue with php maintenance/runJobs.php in the mediawiki installation directory.

Andreas Plank (talkcontribs)

Thanks. Running php maintenance/runJobs.php helped indeed. Is this documented anywhere to check runJobs in that case?

Nikerabbit (talkcontribs)

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?

Andreas Plank (talkcontribs)

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

Yes, I agree
Reply to "api error "nomessagefortitle" (2016.04)"
This comment was hidden by ClemFlip (history)
Reply to "Allow users to edit translated pages"
LeGiangAnh (talkcontribs)


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. (talkcontribs)

same problem for me!!

Nikerabbit (talkcontribs)

Did you use the unstructured element translation guide? An action=purge might be needed on the main page in that case.

Clementflipo (talkcontribs)

Make sure you added <languages /> at the top of your page.

Reply to "Cannot see translated content"

Adding a conlang, and supported languages

Sk4p (talkcontribs)


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?

Nikerabbit (talkcontribs)

$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.

Reply to "Adding a conlang, and supported languages"
Summary by Nikerabbit

Possible to use same name if they are in different sections.

Abbedabb (talkcontribs)

I want to use a <tvar> at least twice in a template. Is that possible? How do I code that?

Abbedabb (talkcontribs)

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.

Nikerabbit (talkcontribs)

Can you give an example of the markup?

Abbedabb (talkcontribs)

I tried using <tvar|year> 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.

Nikerabbit (talkcontribs)

It looks like you found a working solution, is that correct?

Abbedabb (talkcontribs)

Yes. When two <tvar>-tags with the same name are used, but within two different <translate>-tags, they do not interfere wit each other.

Translate recurring word/sentence once?

Abbedabb (talkcontribs)

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?

Nikerabbit (talkcontribs)

No. If that word or sentence is an independent unit, you can use the translation memory to speed up the translation.

Abbedabb (talkcontribs)

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.)

Nikerabbit (talkcontribs)

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.

Reply to "Translate recurring word/sentence once?"

change default language for a page different to wiki default language

1 (talkcontribs)

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) and the wiki page is

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


Kristijan Miklobusec

Reply to "change default language for a page different to wiki default language"
Kghbln (talkcontribs)

I have this on my page:


and I get


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.

Nikerabbit (talkcontribs)

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: task T26139.

Kghbln (talkcontribs)

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.

Andreas Plank (talkcontribs)

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:}}}}<!-- 

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

{{#ifexist: {{Translations:{{FULLPAGENAME}}/Page display title{{#translation:}}}}<!-- 
then-->|{{Translations:{{FULLPAGENAME}}/Page display title{{#translation:}}}}<!-- 
Andreas Plank (talkcontribs)

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}}
Kghbln (talkcontribs)

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

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


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.

Reply to "How to translate category labels"

Use of <translate> within other custom tags

Billinghurst (talkcontribs)

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, all show the text wrapped inside a visible set of translates tag.

Thanks for any ideas on how to achieve this

Reply to "Use of <translate> within other custom tags"

[RESOLVED] Update untranslatable content in translated pages

Zabien (talkcontribs)

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
Nikerabbit (talkcontribs)

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.

Zabien (talkcontribs)

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?

Nemo bis (talkcontribs) was removed from translation and is not listed at all on

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 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.

Zabien (talkcontribs)

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.

Reply to "[RESOLVED] Update untranslatable content in translated pages"