Extension talk:Translate

Jump to navigation Jump to search

About this board


Funkenstern (talkcontribs)


Is it possible to install the Translate extension on a Postgres or must I fear breaking MediaWiki?



Tuxxic (talkcontribs)


Honestly, I can only invite you to be careful and have a test on a replication of your MediaWiki instance first, but this goes for any test of any extension you will be using.

But I'd say, regarding requirements, that it is not compatible : Help:Extension:Translate/Installation

Best regards

Reply to "PostgresQL 12 support"

Translate URLs in target language

Tuxxic (talkcontribs)


Is there any means to translate a page URL written in a language to another language ?

For instance, I have : https://mywiki/index.php?title=Mon_titre_en_français

The English version is : https://mywiki/index.php?title=Mon_titre_en_français/en

I would like to have : https://mywiki/index.php?title=My_title_in_English

I already translate the page titles, so I have the translation.

I also use a model to display translated title in the translated pages, which is as follows :

{{#ifexist: Translations:{{{1}}}/Page display title{{#translation:}}<!-- 
     then -->|[[Special:MyLanguage/{{{1}}}|{{Translations:{{{1}}}/Page display title{{#translation:}}}}]]<!-- 
     else -->|[[Special:MyLanguage/{{{1}}}|{{{1}}}]]

So when people use this model and a page name, it is translated to the display page (ex: {{Traduction|Ma page en français}} will display My page in English as a link.

My first guess was to use redirections, but as there are too many pages to redirect, is there a way to do it automatically with Translate module or another technique ?

Reply to "Translate URLs in target language"

Automatically mark pages for translation

Tuxxic (talkcontribs)


I have been using the Translation extension for a few years now, and I wonder if there is a means to automatically mark pages for translation like with a cron for instance.

I am also using the Extension:Replace Text and each time I use it, I have to manually go on each page and mark it.

Also, my users are not very used to mark every update for translation, so the updates are not always marked.

Is it possible or is it out of scope ?

Thanks in advance

DannyS712 (talkcontribs)

I plan to write a bot to automatically mark pages for translation once phab:T235397 is done, but that would still be from the front end

APatro (WMF) (talkcontribs)
Reply to "Automatically mark pages for translation" (talkcontribs)

I have to install this on my english wiki to import templates that use it. E.g. Warning.

Reply to "not template friendly"

MATCH ... AGAINST does not work in SQLITE

Axdr (talkcontribs)

When requesting API the action = translationaids, an error occurs that causes a bug in ApiMain.php.

The error is the syntax MATCH-AGAINST error in SQLite.

The latest version of MediaWiki is not available to me, but I think this bug is there.

Where can we discuss the topic in more detail? ~~~~

Nikerabbit (talkcontribs)
Reply to "MATCH ... AGAINST does not work in SQLITE"
Blinkingline (talkcontribs)

I've just added some translations to my wiki. In Special:RecentChanges, I have my filter to not see translation, but I can still see where new translations are built and show as unpatrolled. Even worse, when I go to patrol them, there's no "Mark as Patrolled" link for these edits. Am I missing something?

Nikerabbit (talkcontribs)

Translate has its own translation review feature. Patrolling the translation pages would be extra work. There is hardcoded whitelist of actions for translation pages, and it doesn't currently include patrolling.

Reply to "Patrolling Translations"

Unused translation units in the percent stats

Want (talkcontribs)

Section "Changing the source text" from Help:Extension:Translate/Page_translation_administration page state:

Unused unit translations are not deleted automatically, but that should not cause trouble.

It's ok. But unused messages is along count into the info value percentual about state of translated page and it is confusing.

Is usable call of the function MessageGroupStats::clearGroup() for remove unused translation units? Or exists another method for it?

Wladek92 (talkcontribs)

By 'unused messages' do you mean for example T:201 T:202 of the following snippet ? (from https://www.mediawiki.org/wiki/Manual:HTMLForm_Tutorial_3). These comments correspond to previous translated sections which have been corrected such as NO longer to be translated now. Advice in the translation rules was to keep the tags. These comments do not appear on the page but if they generate erroneous statistics we can decide in a first step to remove them (?) carefully from the source (non excluding the developpement part of ignoring them for statistics - but this will be a Phabricator task).

Select multiple users.....
<source lang="php">
$formDescriptor = [...

== url== <!--T:201-->

[[File:HTMLForm Url.jpg|500px]]


... let we still read other points of view.

Christian Wia (talk) 07:23, 1 August 2019 (UTC)

Want (talkcontribs)

No. I specifically meant translation units 51 and 52 from page Help:Signatures (Special:Diff/3339237/3338935). After reverting changes and re-mark page to translate for some time, it still showed that only 95 percent of translation units were translated. It seems to have been just some cache, because now it's ok. But still interest me, what method I can use to get a list of currently id's of the translation units from the page what use by the current revision.

Reply to "Unused translation units in the percent stats"

Suggestion: "Translation" section is Special:SpecialPages

DannyS712 (talkcontribs)

I'd like to suggest that the pages added by this extension have their own section in Special:SpecialPages. For normal users, the following pages are accessible

  1. Search translations
  2. Translate
  3. All translations
  4. Translator signup
  5. Export translations
  6. Language statistics
  7. Message group stats
  8. Supported languages

which are distributed throughout the different sections. Translation admins also have

  1. Aggregate groups
  2. Import translations
  3. Prepare page for translation
  4. Translation page migration
  5. Notify translators
  6. Change page language

And there may be more that are only visible to full administrators. Having this many special pages for the extension means that it would make sense to group them together, rather than the way they are now. Thoughts?

Reply to "Suggestion: "Translation" section is Special:SpecialPages"

Problems about the Chinese local variant conversion are still needed to solve

Taiwania Justo (talkcontribs)
Reply to "Problems about the Chinese local variant conversion are still needed to solve"

By FuzzyBot, translation of all of the paragraph is overwritten in the original

Runequest77 (talkcontribs)

Since English is not good is the question of the automatic translation.

*1.Translated the original text

*2.Fixed only settles the original text

*3.In page translated " mark for translation "

*4.By FuzzyBot, translation of all of the paragraph is overwritten in the original .

I want to leave as it is a translation .

I'll be if I do? --~~~~

Reply to "By FuzzyBot, translation of all of the paragraph is overwritten in the original"