Talk:Content translation

Jump to navigation Jump to search

About this board

Please provide feedback about the Content translation tool on this page.

We suggest checking the Frequently Asked Questions page first.

When reporting a bug, it will help us a lot if you will indicate the following things:

  • Which article were you translating and to which language
  • Which browser did you use (Firefox, Chrome, Microsoft Internet Explorer, Safari, Opera, etc.)
  • If you're getting any errors, please provide log from browser console if possible. To open browser console: press Ctrl+Shift+j (or cmd+alt+J () on a Mac).

In case you are familiar with Phabricator, please consider reporting a bug there.

See also:

Remontees (talkcontribs)


I can't understand why I can't publish my traduction in French of the Wikipedia es page. Can you help me please?

Thanks a lot,

Best regards


Laszlo (talkcontribs)

Hello (bonjour),

Je suppose que tu es français, quelle est ta question : tu n'arrives pas à publier une traduction de cet article sur le wikipedia français ?

Contacte moi sur ma page de discussion WP:FR et on va voir ce qui bloque. Laszlo

Sthelen.aqua (talkcontribs)


I also having problems publishing translation of Pax Mongolica into Ukrainian. The button to publish is not active. Could you explain why?



Saintfevrier (talkcontribs)

Same in Greece: I have been trying to publish a translation from English to Greek and the publish button seems inactive. When I make a minor edit, the button becomes blue. Then after I use it it becomes gray again saying "your translation is being published" and it gets stuck there. The pane on the right mentions various issues - e.g. not enough translated, or too short even for a stub - but NONE of these issues is present. It really is a pity because the article I have translated will be the very first instance of this topic on the Greek Internet.



Vingadoncs (talkcontribs)

Hello, same issue here for 1 week and no solution provided yet. What a pitty.

Igel B TyMaHe (talkcontribs)
Remontees (talkcontribs)

Even worse than the other day: the initial loading of my translation doesn't finish (displays Loading saved translation... all the time) and no longer displays the categories assigned to the page.


Lourenço Borja (talkcontribs)

Just joined and started translating some interesting pages to Portuguese... and after all that work, I couldn't publish them. Had to follow the procedure posted above to create the page from scratch, but it tags my article with a bunch of negative tags because I'm a new user  :(

Saintfevrier (talkcontribs)

It is a pity that this bug is preventing new editors from producing articles. I used the hack above, and I am an experienced user, and even as such it's tedious and takes away a lot of the joy of creating a new article... (you have to know what to remove. As a rule of thumb try removing everything that is not enclosed in "ref" and "/ref" tags. Do a preview, and if it looks OK publish it. If not, go back to the previous page without saving changes and wait while I contact a friend who may be able to push things in the right direction to find a solution)

Divinglia (talkcontribs)

will this bug be fixed? I encounter the same problem..

Shahnamk (talkcontribs)

hi i can not publish this

Saintfevrier (talkcontribs)

I have not tried publishing a translation in the past couple of days but since yesterday the button "publish" that was grey has now turned blue, so I guess that is a good sign :)

Lourenço Borja (talkcontribs)

Managed to publish a translation just now! Finally :)

However, the issue with the faulty detection of "uppercase only" paragraphs is still there, and just makes every translation 150% more stressful than it has to be. Please address this sometime :(

Reply to "Can't publish my translation"
Sashatrk (talkcontribs)

Greetings! I have a problem with translation from english to russian in: Well. If I start editing very well, EVERY SINGLE PART, then i get an error. I already said about the error was wrong. Then the filter says: The error is not in the filter, it's in the ContentTranslation. What IS the problem here?

Thanks a lot,

Best regards

Reply to "Problem with russian version"
Jembrat (talkcontribs)

I translate a page all is good, and when click published it does nothing. The page doesnt published and it still in Progress stage in translation. Anyone can help?

Hoshi27 (talkcontribs)

I have the same problem, but know what to do.

Jembrat (talkcontribs)

what you do?

Hoshi27 (talkcontribs)

I trie again to see if everything go back to normal, but unfortanally nothing happen. Sorry if I coudn't help.

This post was hidden by Vingadoncs (history)
Vingadoncs (talkcontribs)

Same here. I can't publish some of my translated articles.

Vingadoncs (talkcontribs)

For your reference, I'm trying to translate from English to Catalan this article: "Ratification Day (United States)" (talkcontribs)

@Amire80 any idea what could happen? I have spent some time translating and I don't want to lose it. Thanks!

Amire80 (talkcontribs)

What happens exactly? The publish button doesn't appear? It appears, but the page is not published? Do you see warnings?

Vingadoncs (talkcontribs)

Hello, when I push the publish button, It keeps "Publishing" all the time but it never publishes. I have tried from 3 different laptops, from my personal phone... Nothing.@Amire80

Inteloff (talkcontribs)

Happened to me too, the button has been on "publishing" for half an hour.

Vingadoncs (talkcontribs)

Hello @Amire80 any solution? Thanks!

Igel B TyMaHe (talkcontribs)

May be there are no corresponding categories in destination wiki, this caused CT crash. You can access translated text with minor trash tags in translation debugger Example for en->ca "Ratification Day (United States)":

fill Source language (en), Destination language (ca) Source title (Ratification Day (United States)), click FIND, click FETCH TRANSLATION, click WIKITEXT tab for source code. Then you need to remove all <section> tags to get clear wikitext ready to publish.

Saintfevrier (talkcontribs)

It was tedious, but it worked. Thanks! (and hope the bug is fixed soon, I'm not going through that again :P )

Hoshi27 (talkcontribs)

How can I look the ID for the text that I'm trying to translate? Like Franklin (peanuts)

Sevkehikmet (talkcontribs)

I have the same problem unfortunately. The publish button is active but after I click the publishing button, nothing happens. I am also looking for any advice tip. Thanks.

LyimeS (talkcontribs)

I wish it would give me the source code, I'd publish it as a common article.

Saintfevrier (talkcontribs)

see Igel's comment above: you can get the source code with this hack, but you have to delete a lot of code before publishing. It worked for me but I need a solution that doesn't take up so much time...

Ranveig (talkcontribs)

I have encountered this problem as well. I have managed to publish another translation fine, but have been unable to do so for Cille Gad from no: to nn: for several days. There is an error message saying that the source article has changed since I started the translation - it hasn't. I couldn't find the work in the debugger.

Divinglia (talkcontribs)

my publish button isn't active too..

Reply to "Translated page wont publish"
Szombara88 (talkcontribs)
Reply to "Problem with polish version"

It just says my translation has some problem, but I don't know what the problem is and how to fix it in order to go publish.

Divinglia (talkcontribs)

Anyone knows? The error refers to the information panel (the summary grid box on the right)

Divinglia (talkcontribs)

anyone can help? where can i find out what exactly the error is?

Reply to "It just says my translation has some problem, but I don't know what the problem is and how to fix it in order to go publish."

Incorrect Error message: The wikipage contains only uppercases

Coel Jo (talkcontribs)


First, let me congratulate the developers of this tool. It is very very useful.

I'm getting a error indicating that I am abusing uppercases - that is not true.

Any ideas on how to bypass this?


Coel Jo

Reply to "Incorrect Error message: The wikipage contains only uppercases"

Impossible to publish translated page due to "not enough experienced editor" message

1 (talkcontribs)

I just translated the italian version of my Company page into english, but unfortunately I can not publish it, just save it as Draft, because "publishing is only allowed to more experienced editors on this wiki"

How can I solve the problem? How many contributions should I make in order to become a trusted contributor and be able to publish my translated page?

Is there any other way to solve the issue? For instance changing language? Please give me any tips!!

Reply to "Impossible to publish translated page due to "not enough experienced editor" message"
Omotecho (talkcontribs)

A table with multiple contents including images does not propagete on CX2; I am pasting the section link from the original enwp page as above. The "publish" button turned to gray, so I decided to feed a new edit;

  1. The error message plainly notes the functionality failed to translate.
  2. I set automatic translation *Google* off, then tried to migrate the wikitable into translation pane,
  3. but still the same error message shows.
  4. The "publish" button came alive in blue;
  5. Pushed to publish, however, button turns gray telling "saving", but not saved to the destination user sandbox at all. Only at the top of CX2 translation card XXX minutes past after last saving" gains the number of minutes since last autosave. Template:Nihongo"
  6. To escape, I went back to the list/CX2 starting page, checked if the above page was published or not.
  7. Opened the translation original in enwp, copied the section which does not propagate into right target pane, then pasted. My anticipation that word count difference between the source (left pane) and the target (right pane) could prevent saving is not proofed right. Still can't publish translation to user sandbox page.

Reply to "Wikitable too large to handle?"

Do you check for translations into Japanese ?

HaussmannSaintLazare (talkcontribs)

I am a Japanese speaker, and I use this feature to translate from other languages including English into Japanese. As you know, Japanese codes are more complicated than English one, which may be causing troubles. There seems to be many English speakers among the developers, and I feel that there are no Japanese speakers. Is that right ?

Amire80 (talkcontribs)

None of us knows Japanese, but it doesn't really matter because Content Translation is enabled for all the languages in which there is a Wikipedia, more than 300. It's just impossible that the developers would know all of them.

The content that is created by Content Translation is checked by the same people who create and edit all other articles: the editors of Wikipedia in each language.

But since you asked, are you experiencing any particular issues with Japanese? Can you give some examples?

Omotecho (talkcontribs)

May I jump in? For example, cite web templates on jawp asks for the access-date parameter, so that CX2 detects in en-ja language pair your translation has a citation problem. I am afraid so many new editors who finds CX2 very handy skips to migrate footnotes/refs from translation original so that they won't see the embarrassing red error notes.

When you try to fix the error and supply the access-date to a cite web template, then please see the workflow below; You see, it's not very encouraging to do the detection work, and I am sure there be any function or extension that automatically search for the exact diff and output the date in UTC. If it be introduced to CX2, the jawp translator community won't be exhausted by the very productive new translators; at the moment, User's Manual for CX2 lacks that part and explain what a translator's job is; even with CX2 output, you don't publish your translation as an unfinished package, or leave template errors infixed; moving on to the next target is very easy with CX2 and speeds up your production rate/edit history. But who fix the error? CX2 is a wonderful tool, but I can't ignore the bitter aftertaste as I am pro-CX2 and feel obliged to fix other's unfinished cite web template errors. sobsob

Fixing cite web template lacking access-date;

  1. Publish the translation anyway;
  2. open the enwp original article, find the exact diff when the dateless cite web template was added; it&s a lot of guess work, and I can't recall anymore when you have not introduced diff slide bar,
  3. then copy the date, to paste into the error-evoking cite web template in your translation.
Amire80 (talkcontribs)

Thanks for the example and for being pro-CX :)

Can you please give me an example of an article that was translated from English to Japanese and had a problem with the access-date parameter? The templates appear to be adapted correctly according to the instructions, so there may be a bug in Content Translation somewhere.

Omotecho (talkcontribs)

Hello, finally sorted out one sample at Elizabeth Cady Stantoninto ja &oldid=75879178: template error due CX2? {{Cite web|url=|title=Architect of the Capitol; Portrait Monument of Lucretia Mott, Elizabeth Cady Stanton, and Susan B. Anthony|publisher=}}. Cheers,

Amire80 (talkcontribs)

Thanks for the example.

So, as far as the Content Translation (CX) algorithm goes, this worked correctly. All the parameters from the original template were copied as they are in the source article. CX has no way guess that accessdate is required in the Japanese Wikipedia—it's a difference in policy between English and Japanese. (I am mentioning English here not because the English Wikipedia gets any kind of special treatment, but simply because this is the language from which this article was translated.)

At the moment, there is nothing that CX itself can do about it. The same thing would happen if the article was translated manually, without CX, and a user would have to add accessdate manually after noticing the red error message. Perhaps this can be done by a bot, although the whole point is probably to let a user check the website.

Perhaps it will be possible to fix this in the future, although it won't happen very soon. At the moment I am trying to find better ways to share templates between wikis, while respecting each wiki's stylistic preferences. As part of this, I am thinking of sophisticated ways to define which templates and parameters must be copied, transformed, ignored, etc. I wrote some ideas about it on the page Global templates/Proposed specification, especially in the sections "Making templates semantic", "It must be possible to make some templates non-global", and "Translating parameter values". I am mostly speaking there about removing unnecessary things or automatically translating things according to rules defined by the communities, but it's also reasonable to add things, as you are asking in this case. If you have time to read it, I'd love to know what do you think about it.

Omotecho (talkcontribs)

What a task you are on to match templates/specifications in advanced level. I will return to your link sooner meeting open ends, and thank you for your thorough follow up in this manner. Regards,

Amire80 (talkcontribs)

Thanks. Yes, it's a big thing, and it's long overdue. People started asking for it back in 2004...

Omotecho (talkcontribs)

Wow, you are super cool to look into the possible cause for the bug, that is where I am not very handy at. Sure, let me check and reply to you.

Reply to "Do you check for translations into Japanese ?"

Minor bug: times new roman everywhere

Igel B TyMaHe (talkcontribs)

All texts (interface and content) are now times new roman (or default serif style) no css access? Just for you information, this is not preventing from translation.


Рассилон (talkcontribs)

I have the same issue: Topic:Vf18jsh7iqwqlssp, except titles of source and destination pages that is in Georgia. By the way, fonts fallback to standard font of web browser, and neither sans, nor sans-serif.

Reply to "Minor bug: times new roman everywhere"