Talk:Content translation/2019/03

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+Shift+J on a Mac).

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

See also:

• Frequently Asked Questions
• User manual
• Content translation/V2 - updates about the new version
• Highlights of Content Translation software updates (until 2017)

Article is already being translated and critical error

Hi there, I am trying to use the Content translation for the first time and I've encountered this: The tool says that the article I've chosen is already being translated by another wikipedian and that I should coordinate with him/her. Then, a little bit bellow it says Critical error: Content translation failed to load due to internal error while the loading of an article freezes. A bug? Or a normal behaviour? What should I do? Printscreen on the right. YjM (talk) 11:51, 1 March 2019 (UTC)

Yes, I think so. My first idea is to wait, to have the other user completing the translation. First check if the destination article exists, even it may be not liked by Wikidata, You see on the articles left border linked to its other language versions.

If translation takes too long, see other topic in this talk how to create a temporary copy to translate that one.

If Your are translating into English language, Your account needs to have contributed least 500 edits to the English Wikipedia project due restriction of experienced users only. Hans Haase (有问题吗) 12:10, 1 March 2019 (UTC)

Thanks for the tips.

The user is not going to complete the translation now, I've spoke with her off-wiki.

The article does not exist in the target Wikipedia, I've checked it.

I'm translating to Spanish. YjM (talk) 12:16, 1 March 2019 (UTC)

Thanks for trying the tool, @YjM.

This is one current limitation of the tool. Currently we are working on both, making it possible for multiple people to start a translation on the same topic, and removing very old translations. Pginer-WMF (talk) 18:57, 4 March 2019 (UTC)

Pginer-WMF, users should be asked if they want to release a started translation to another user or if they share their translation, but only one user can work the translation until the user exits the translation and interrupt working on it. Hans Haase (有问题吗) 13:35, 5 March 2019 (UTC)

Why were my translations deleted?!

About 20 translations (or more, I don't even know anymore) of science-related topics were simply deleted by WiIkipedia! The content was removed and is not available to portuguese speaking people anymore. The content was not updated by me in the past year (the notification had this claim as an excuse for removing the page), but I cannot imagine how an slightly outdated translation is worse than no translation at all. Specially because many "original articles" in pt Wikipedia in the field of the biological sciences are either poorly written or incomplete drafts and have not ever been removed.

I am very frustrated, as these pages contain some important topics in biology , such as the translations of https://en.wikipedia.org/wiki/Platelet-activating_factor to portuguese .

Is it possible to put them back on Wikipedia?

These deletions are very upsetting and a neglect of the lusophonous community. TiagoLubiana (talk) 13:34, 1 March 2019 (UTC)

I only see 3 deleted articles from Your account in the Portuguese Wikipedia. One has been recreated. If those articled have been published, usually notes about deletions will remain. See https://xtools.wmflabs.org/pages/pt.wikipedia.org/TiagoLubiana?uselang=pt Hans Haase (有问题吗) 13:52, 1 March 2019 (UTC)

Thanks for the feedback, @TiagoLubiana.

The tool deletes the old translation drafts that were started but not the final content that was published. If you started a translation but do not publish it in more than one year, that in-progress transalation gets deleted. If you publish the translation, the published content becomes a regular Wikipedia page that does not get automatically deleted by the tool (the community will review it and may decide to delete it as part of the review process, but that is a different story).

There are several reasons to avoid in-progress translations to be stuck for a very long time, including outdated content, blocking others from translating the same topic, and use of database space. Pginer-WMF (talk) 18:52, 4 March 2019 (UTC)

This is insane.

a) There is no warning before deletion, and it is unexpected, at least for the first deletion a user is subjected to, as nowhere when they started the translation did it say that it might get deleted. Because the deletion is unexpected, it is frustrating, and makes the user whose translation was deleted feel out of control

b) What if somebody put hours and hours into translating parts of an article, and now you delete these translated parts? You are deleting their work

c) You could at least, when you delete something, email the author the content Distelfinck (talk) 19:07, 5 March 2019 (UTC)

Re the reasons mentioned for deletion:

"outdated content"

When I get back to a translation draft after some time, I make sure to look if the article to be translated has changed. So the reason "outdated content" doesn't apply to me. Furthermore, by deleting you are treating the user like you are the nanny, and as if like the user can't properly take care of such things as outdated content. I can do that myself, thank you.

"blocking others from translating the same topic"

There is an alternative available to deleting drafts, that accomplishes the same thing: We could after a year make the topic available for translation by others, without deleting the translation draft.

"use of database space."

You gotta be kidding me. When I donate like a dollar, that could pay for how many translation drafts to store for 10 years? Thousands, tens of thousands? Storage is incredibly cheap these days. But if it is a problem, I am willing to donate, just say so. Also, if you really have to delete it, which I doubt, why not email the user the contents first? Distelfinck (talk) 19:20, 5 March 2019 (UTC)

Simply do not delete, publish as a draft in user space with a notice on user talk page. Igel B TyMaHe (talk) 09:19, 12 March 2019 (UTC)

Many pages simply do not exist anymore. For some reason, even the logs are not present anymore.

The pages were translated, I am sure.

I will just hope it does not happen again... TiagoLubiana (talk) 13:43, 30 March 2019 (UTC)

After a year not working on a translation, it will be deleted. Hans Haase (有问题吗) 14:08, 30 March 2019 (UTC)

Thanks for the quick answer. Why is that so?

Does that apply for finished translations, or only to works in progress?

EDIT: By finished translation, I mean published works. TiagoLubiana (talk) 16:20, 30 March 2019 (UTC)

I petition whoever can stop this to put deletion on hold, so that not even more user content is deleted! Distelfinck (talk) 21:20, 30 March 2019 (UTC)

2 Issues: Auto capitalization of Georgian words and missing articles

1. There is known issue with Georgian font, example source, which cause some word to display as missing, as a rectangle. There is similar selecting a wiki article as missing. I'm translating this article https://en.wikipedia.org/wiki/Spotlight_effect, and this authors Georgian article is saved like this
2. I'm not sure if this issue, but shouldn't missing articles be displayed as red? For some reason I can't mark article as missing, if I got right CT automatically creates articles with just a title. like the one liked above of Thomas Gilovich.

See screenshot for reference https://i.imgur.com/PojH7oe.jpg Kintrbr (talk) 14:33, 2 March 2019 (UTC)

2. Marking as missing generates a red link, also displayed in red. The gray marked replacement of a missing link will not be created as any link. Hans Haase (有问题吗) 14:38, 2 March 2019 (UTC)

It doesn't :/, there is a bug. One more example. I wanted to mark as missing the link on "anchoring and adjustment" in the Spotlight effect article.

First it did this https://i.imgur.com/tnohI0N.jpg. it is red but it made an article with same name on Georgian wiki https://ka.wikipedia.org/wiki/Anchoring.

I tried to edit it https://i.imgur.com/c7VDfyv.jpg, but after saving it turned blue https://i.imgur.com/vnvKId8.jpg (+ issue #1) Kintrbr (talk) 15:21, 2 March 2019 (UTC)

The Google autotranslation has problems, due the Georgian destination articles does not exist. So Google translator assumes the correct translations and the CXT does not find any article, sometimes coping the source, non-translated article name. This is the reason why the link is displayed in blue, suggesting an existing article. Hans Haase (有问题吗) 16:19, 2 March 2019 (UTC)

Is requires more manual work, creating and naming and linking the missing articles. Hans Haase (有问题吗) 16:21, 2 March 2019 (UTC)

The red links issue is a known bug. It will be resolved.

Can you please explain a bit more about the capital letter issue? At which point does this happen? Does this happen only with Content Translation? Amir E. Aharoni {{🌎🌍🌏}} 18:18, 2 March 2019 (UTC)

Mtavruli is a different version of Georgian letters. You may say it's capital letters (some don't agree, not the point here). These Mtavruli letters have been added to UNICODE but and it is considered as Georgian capital letters. The issue is that it is not yet supported by -how to put it- browsers and operating system, and for user it is displayed as rectangles. Here are more technical details in case of Chrome browser.

So, in Content Translation it happens when I try to edit link to a missing article, there are screenshots is previous comment. Kintrbr (talk) 11:15, 3 March 2019 (UTC)

Yeah, I'm familiar with the general problem about Mtavruli letters. But can you please describe the steps you took to arrive at the situation that appears on the screenshot at https://i.imgur.com/PojH7oe.jpg ? I cannot reproduce it myself.

Amir E. Aharoni {{🌎🌍🌏}} 13:47, 3 March 2019 (UTC)

Terrible results

A majority of Norwegian Wikipedia users vote to turn automated translations off entirely, since the results are sub-par, to say the least. This technology is still far from production ready, at least for a minor language like ours. We have limited resources, and in addition to fighting vandalism, we now also have to fight another form of disruption, namely the dumping of unusuable text, courtesy of Wikimedia's content translation.

Please disable this tool entirely for the Norwegian edition. Get back to us in a few years, when the output has become somewhat acceptable. Asav (talk) 13:27, 3 March 2019 (UTC)

See the English project, restricting it to experienced users only. Hans Haase (有问题吗) 15:21, 3 March 2019 (UTC)

Thanks for your reply. How could this be implemented in other editions? Asav (talk) 15:35, 3 March 2019 (UTC)

In the EN:WP it is en:Wikipedia:Requests for permissions/Extended confirmed Hans Haase (有问题吗) 21:03, 3 March 2019 (UTC)

Thanks for the feedback, @Asav. There are different mechanisms that can be used to encourage better translations.

I'd not recommend disabling the tool entirely, or blocking the use based on the number of edits of the user. Based on the results of other Wikipedias where machine translation is available, the translations produced are less likely to be deleted than the articles started from scratch. For example, on French Wikipedia during 2018 the deletion ratio was 6% for articles created with Content Translation, and 23.6% for new articles created otherwise. In general, I don't think that makes much sense to set a higher bar for translation than for new page creation made with other tools.

I think the best approach is to focus on the content that users create (instead of who the user is). Content translation keeps track of how much the initial automatic translations have been modified by the user. Currently, when a translation has a paragraph with 80% or more of unmodified machine translation, a warning is shown to the user encouraging to review. If the user publishes despite these warnings, the published translation will be added to a tracking category for editors to review. For Norwegian, this is the tracking category of translations with potentially unreviewed content.

For the more extreme cases, with 99% or more of unmodified contents th tool directly prevents publishing the translation. We can adjust these thresholds or the approach to obtain them, but for that we need more detailed feedback about the quality of the content produced. So feel free to provide more details in this area. Pginer-WMF (talk) 18:45, 4 March 2019 (UTC)

Like most other patrollers in the Norwegian edition, I immediately mark any and all entries produced by machine translation (be it Content translation or other engines) for speedy deletion. Mostly, they're pure gibberish. This also applies to shorter entries that might otherwise be more easily edited/corrected, as accepting machine translations is an open invitation to dump even more of them into our pages.

Again, a vote/poll amongst active Noreagian users showed an overwehelming majority wants to get rid of this technology entirely until it's ready for roll-out. As for the Norwegian edition, it's not even close as of today.

Please bear in mind that our edition is a small one with limited patroller and editor resources, and our time is much better spent with contructive work rather than cleaning up the mess forced on us by programmers who have no insight into the dismal quality of these translations. Whatever the results may be from major languages, such as French, they hardly apply to Norwegian.

Furthermore, including these meaningless translations seriously diminishes Wikipedia's standing as a quality encyclopedia.

Lastly, we fully understand that content translation may work better or even well for engine translations into major languages with a larger text corpus (and probably more resource spent on them). But Norwegian is not such a language, and until this technology truly can deliver, it ought to be barred completely from our edition. Asav (talk) 19:12, 4 March 2019 (UTC)

I think, experienced users give an article a primary review. Hans Haase (有问题吗) 13:31, 5 March 2019 (UTC)

I frankly don't understand what that's supposed to mean. (Du kannst auch auf Deutsch schreiben wenn du willst.) Asav (talk) 16:14, 5 March 2019 (UTC)

Translation of above section: Ich denke, erfahrene Benutzer werden einen Artikel nochmal durchsehen. PS: …Before editors publish their translation. Hans Haase (有问题吗) 18:37, 5 March 2019 (UTC)

Well, that may be the case for larger editions, but again, the Norwegian one has very limited resources, so speedy deletion is our only feasible option. Making these machine translations available here is disruptive at best. As stated before, it also diminishes Wikipedia's overall quality considerably.

The programming team behind this technology may think it's all fine and dandy, but in reality, it's really destructive. Asav (talk) 18:45, 5 March 2019 (UTC)

Potential spam content was detected in your translation. Details: amazon.com

I have problems with this menssage, I tried to traslate english to spanish, but this don t me allow to publish. Someone can help me with it Lordthe6 (talk) 13:14, 5 March 2019 (UTC)

Use the gear button to publish it as personal draft. Then edit the article and remove the unwanted link or reference. Then move the article to the article name space.

Note: Amazon is not seen as a reliable source. The reason: It is volatile and a primary and not reviewed information. The article will have a problem, when holding this unsourced or weak statements. Hans Haase (有问题吗) 13:41, 5 March 2019 (UTC)

I tried it but appear the same mensagge, in the articles not appear a link with amazon.com, for example https://en.wikipedia.org/wiki/Triglyceride and others maths articles appear the same message, Lordthe6 (talk) 13:50, 5 March 2019 (UTC)

Try to delete the [1] or whatever the amazon reference it. Ensure it is used once or delete the copied also. Hans Haase (有问题吗) 14:23, 5 March 2019 (UTC)

Thanks the problem was in the isbn url of one reference Lordthe6 (talk) 14:42, 5 March 2019 (UTC)

Problem with content translation

When I try to save a translation of the Italian article it:Liceo moderno into English Wikipedia, the Wikipedia Translate-page feature shows this "Automatic edit filters have identified problematic content in your translation. Details: Hit AbuseFilter: Content Translation Edits" error message, but I do not understand where is the problem.

Also is not available the button "change editor". DelvecchioSimone12 5 96 (talk) 17:03, 5 March 2019 (UTC)

For translating articles using ContentTranslation tool in English Wikipedia, you need to have 500 edits in enwiki. KartikMistry (talk) 05:38, 11 March 2019 (UTC)

Ability to show article from translation-list first; before decision, which one to translate

On the translation-page, I would like to be able to open an article for translation first, to decide which article to translate.

{Presently, one needs to select the title of the article & copy-paste it on to a new browser-tab - quite cumbersome.}

I like to ask the website-coders of Wikipedia kindly to make the article-titles of the translation-page operable links, which open on a new browser-tab, when clicked/finger-dabbed. [1] Fin434 (talk) 07:50, 6 March 2019 (UTC)

Template translation

Yo, i see you removed "translating templates in html" and replaced it with native templates. That is nice, but i most of the time need this feature for non-existent templates on trwiki and other wikis. It is very useful and required for translations in most cases.

please put it back Erentar2002 (talk) 21:13, 9 March 2019 (UTC)

Ref tag bug with archived url on Safari

When the ref tag clause include archived url, it does not work properly while translating https://ja.wikipedia.org/wiki/Special:ContentTranslation?title=Special:ContentTranslation&campaign=contributionsmenu&to=ja&page=National+Parks+and+Wildlife+Service+%28Ireland%29&from=en&targettitle=国立公園野生生物保護局++%28アイルランド%29&version=2 en->ja. I am using Safari on iPhone6Plus (12.1.4 16D57 lang=ja)</nowiki>

Below I changed actual terms into en for convenience but word order remaining in that of ja. [] indicates it is a link.

There are two refs in above translation pair, and for the firstvone [1] I expected it to show. The second has identical issue ss the first.

• [1] “Author, [Xxx], [archived], publisher, date, archive-date accessed.”
• Xxx is the url-title and _archived_ is link to external archive service such as Wayback machine.

But currently it shows :

• [1] “Author, [Xxx] someterm [Yyy], publisher, date, archive-date searched.”
• Xxx and Yyy are segments of a single url/title; the term ‘searched’ should be corrected as ‘accessed’.
• And the archive-url link is lost as both Xxx and Yyy links to the original/before archived site.

I have published the translation with underconstruction temp for 3 days, as I was curious what Xxx and Yyy will link to. Omotecho (talk) 10:27, 10 March 2019 (UTC)

Automatic translation failed.

I get this message and it refuses to translate one paragraph of the text. I tried putting in a new paragraph to translate it myself but it also doesn't want to do that. What now? Jpeda (talk) 10:45, 10 March 2019 (UTC)

Mark a smaller section of text to translate, then use CRTL+ALT. Hans Haase (有问题吗) 11:24, 10 March 2019 (UTC)

Ability to continue translating not allowed

I published a half translated article just to see what it would look like when published, but I am now unable to edit the translation I was making and finish it. Should I start over or what? QuickWittedHare (talk) 21:05, 10 March 2019 (UTC)

Eu publiquei metade de um artigo traduzido apenas para ver o que aconteceria quando eu o publicasse, mas agora eu não tenho permissão para terminar de traduzir o que comecei. Eu deveria começar de novo ou oque? Andre machado15 (talk) 00:10, 11 March 2019 (UTC)

Looking for confirmed editor to publish translation

Hello, I would like to publish the english translation for this french article https://fr.wikipedia.org/wiki/Dominique_Warluzel but the translate page can only be used by confirmed editors. I have already translated the text in english.

Can someone help me there ? Olivier Aebersold (talk) 07:12, 12 March 2019 (UTC)

Try publishing as personal draft. Hans Haase (有问题吗) 07:15, 12 March 2019 (UTC)

Зачем переводятся ref-ы?

В новом CT текст внутри тэгов ref переводить не надо, там, как правило, библиографическая ссылка, которая переносится без изменений. Принудительно при копировании абзаца-шаблона сносок поставил "Копировать исходный текст", но при публикации он всё равно был переведён, теперь все сноски нужно вручную, по одной, копировать из исходной статьи. Igel B TyMaHe (talk) 09:14, 12 March 2019 (UTC)

Can someone give a hand with this table?

I'm trying to translate this page into Spanish: International Short Film Festival Oberhausen.

I have an issue with the table. I cannot fill the Infobox film festival. It doesn't allow me to edit it. Is that why when I click on publishing, it freezes and stays there frozen?

It also gives an advice that it seems that it is an automatic translation but I guess that's because there are many proper names that are exactly the same. Julesplus (talk) 15:18, 12 March 2019 (UTC)

Cannot publish/edit old translation

I have a translation that I started several months back, "Linked list" from en.wp to ro. Now, if I try to resume it, it never saves. Also, if I try to publish what is already translated, I get: nothing, the "Publishing..." button turned grey and no response. The JS debugger console contains this:

Error: Attempting to set unmodified MT without an MT provider 2 load.php:2419:181

   mw.cx.dm.SectionState.prototype.setUnmodifiedMT https://ro.wikipedia.org/w/load.php:2419:181

   mw.cx.TranslationTracker.prototype.processSectionChange https://ro.wikipedia.org/w/load.php:2410:16

   mw.cx.TranslationTracker.prototype.processChangeQueue https://ro.wikipedia.org/w/load.php:2408:736

   mw.cx.TranslationTracker.prototype.getTranslationProgress https://ro.wikipedia.org/w/load.php:2414:100

   mw.cx.TranslationTracker.prototype.init https://ro.wikipedia.org/w/load.php:2407:907

   mw.cx.TranslationController.prototype.onSurfaceReady https://ro.wikipedia.org/w/load.php:2404:27

   oo.EventEmitter.prototype.emit https://ro.wikipedia.org/w/load.php:195:479

   ve.init.mw.Target.prototype.surfaceReady https://ro.wikipedia.org/w/load.php:1696:124

   ve.init.mw.CXTarget.prototype.surfaceReady https://ro.wikipedia.org/w/load.php:2554:902

   <anonymous> self-hosted:973:17 Andrei Stroe (talk) 12:37, 13 March 2019 (UTC)

Can't translate article

I want to translate Rotavirus article form English Wikipedia to Indonesian using Content Translation. It seems a new user has started the translation so I can't use this tool. This new user has 0 contribution in global wiki and I can't contact him/her. What should I do? Thank you Yogwi21 (talk) 08:43, 14 March 2019 (UTC)

Thanks for the feedback, @Yogwi21.

Due to technical reasons, this is a current limitation of the tool. There are plans for not blocking the translation to a single user. This ticket captures the details, and you can subscribe to track its progress and add further comments.

There is also a proposal to automatically discard very old translations. This can also help to alleviate the problem of articles being blocked. Pginer-WMF (talk) 15:04, 14 March 2019 (UTC)

citation transformation not helpful

I like how some of the things work, but citation transformation is the least helpful part. It would actually be more helpful if templates would be removed and transformed into an URL. That way I would be able to use the Visual Editor to transform URL into a more meaningful, elegant and easier to edit reference. Nux (talk) 22:27, 14 March 2019 (UTC)

Thanks for the feedback, @Nux.

Templates were not created to easily work across languages, which is especially problematic with the plethora of templates used in each wiki to structure the information in references. we are working to improve the support for references, and improving the documentation for communities to provide the appropriate template metadata that would help Content translation to better map template information across equivalent templates.

For references based on a URL, we may consider how such URL can be used to generate a new reference in the target wiki, even automatically. Thanks for the suggestion. Pginer-WMF (talk) 13:41, 22 March 2019 (UTC)

Spaces inserted after punctuation

When using Google Translate to translate content, it adds additional spaces after some punctuation marks - specifically periods, and references. I edit them out during translaton, but many users don't realise, and it looks really bad. Here's an example, before editing:

https://cy.wikipedia.org/w/index.php?title=Alice_Williams&oldid=7700621 Dafyddt (talk) 17:27, 15 March 2019 (UTC)

Thanks for the feedback, @Dafyddt

This issue is captured in this ticket and we plan to work on it soon. Feel free to track the progress of the ticket or add further comments. Pginer-WMF (talk) 13:13, 22 March 2019 (UTC)

Please add new feature

If would be so much easier if we could also edit source code directly, sure I can publish a page and do it then but sometimes there are so many things it's just easier to start it on my own. You could hide it under some advanced tab if you think most users don't want it. Still something deleting one word or changing one little thing in code would get it to look so much better. Otherwise I like this tool a lot! Great work! Karakondzula (talk) 17:28, 17 March 2019 (UTC)

Hi,

Can you give an example of things that are easier for you to do in source code? Amir E. Aharoni {{🌎🌍🌏}} 18:58, 17 March 2019 (UTC)

Sure, here are couple

1. often Templates are wrong and with little bit of editing it can be fixed, then most that are even right are just copied as they are in English and you can't translate those fields unless you have access to source code of that article.
2. If something is quoted again it is just copied "as is" in English and you can't translate until you publish the page and edit the source
3. Similar thing happens with math formulas and pronunciation text as well but it can be easily fixed once you publish the page
4. Text under images is sometimes impossible to edit or really hard (can't navigate through it so you have to delete entire translation if you need to change one word)
5. Editing Phylogeny tree is not possible

Those are just couple I could think of right now, there are probably more. Karakondzula (talk) 20:05, 17 March 2019 (UTC)

Most of these issues are with templates. It is possible to edit most templates in Visual Editor, and the current version of Content Translation uses the same tools for template editing as Visual Editor does. Have you tried it? The Phylogeny template is perhaps too complicated, but most others are usable through Visual Editor. Amir E. Aharoni {{🌎🌍🌏}} 20:41, 17 March 2019 (UTC)

Sure it is possible to enter templates in some cases but often it is not possible. I have tried to edit it in VIsual editor but even when it is possible to edit templates often it's not possible to edit all fields, some fields you can only edit in code. Still I do think it would be a lot easier if it was possible to edit it in code. Sure editing in code is not for everyone but it should at least be an option for those who want to use it. Then I don't expect everything to be directly transferable and being able to edit it in code sure would help a lot with it.

P.S. I wasn't just thinking about Phylogeny template, but also regular Phylogeny tree even though both of those I assume are complicated they would be easily editable in code.

Then I understand why feature won't be added, you are thinking if you want to edit in code just edit it normally like most people and just use Google translate. Still I do think this tool has a lot to offer and makes so many things easier when translating.

Thanks for hearing me out! Karakondzula (talk) 20:59, 17 March 2019 (UTC)

No, not necessarily. It's actually possible that source editing will be added some day. Other people have requested it, too. It's not planned for the immediate future, but it may happen further down the road. I'm just trying to suggest solutions for now. Amir E. Aharoni {{🌎🌍🌏}} 21:51, 17 March 2019 (UTC)

Oh okey. Hope it does become availble sooner rather then later.

Thanks for your help! Karakondzula (talk) 22:19, 17 March 2019 (UTC)

Translations from Spanish to Galician

Hi, I'm reviewing translations from Spanish to Galician and I have found some problems:

• spanish text "una" is not translated, and it should be translated to "unha"
• spanish text "para" is translated as "paira", but it's incorrect, it should be translated as "para"
• the spanish model "cita publicación" is adapted to gl.wiki as "cita publicación periódica", it adapts some parameters but others no, for example "nombre" and "año", they should be adapted to "nome" and "ano" respectively

Who knows how fix this problems? I'm working with that problems at https://gl.wikipedia.org/wiki/Usuario:Elisardojm/Carl_SaganBye. Elisardojm (talk) 11:41, 18 March 2019 (UTC)

I have found another issue at model "cita noticia", it's adapted to galician model "cita novas", but it doesn't have "data" e "dataacceso" parameters. Elisardojm (talk) 11:55, 18 March 2019 (UTC)

Another issue, at es.wiki model "cita web", parameter "fechaacceso" and "fecha" are not adapted to "dataacceso" and "date" in gl.wiki model "cita web". Elisardojm (talk) 12:00, 18 March 2019 (UTC)

Another issue, at es.wiki model "cite news" is adapted to gl.wiki model "cita novas" but only adapts parameters "url" and "título". At gl.wiki "cite news" model is supported, perhaps it should not be adapted. Elisardojm (talk) 12:13, 18 March 2019 (UTC)

Model "cite web" it's supported too at gl.wiki, it should not be adapted. Really, all en.wiki cite models are supported at gl.wiki with english parameters and should not be adapted. They are at https://gl.wikipedia.org/wiki/M%C3%B3dulo:Citas Elisardojm (talk) 12:19, 18 March 2019 (UTC)

Another issue, es.wiki "Cita enciclopedia" should be adapted to gl.wiki model "Cita enciclopedia". Elisardojm (talk) 12:23, 18 March 2019 (UTC)

Another issue, es.wiki "cita entrevista" should be adapted to gl.wiki model "cita entrevista". Elisardojm (talk) 12:31, 18 March 2019 (UTC)

Could somebody help with these issues? Bye. Elisardojm (talk) 23:37, 21 March 2019 (UTC)

Thanks for the feedback, @Elisardojm.

Regarding the translation of specific words (such as "una" or "para") in the examples, we cannot do much about it directly. Content translation integrates existing machine translation services, and improving these services is part of their corresponding teams work. What we do is exposing the user corrections made for them these teams to process and make improvements based on them. So improving those initial translations for each article you translate, you are already helping the translation services to improve in the future.

Regarding the translation of templates there are some aspects that help Content translation to do a better job. Templates exist independently in each wiki, so Content translation relies on metadata to find the equivalent template first, and then find the equivalent parameters to copy over the data.

For example, Content Translation finds that "Cita novas" is the equivalent template to "Cita noticia" because they are connected in Wikidata. However, the tool cannot find the equivalent parameters between the two templates because of the lack of metadata. For parameters with the same name in both templates (such as "autor") the tool can copy the information, but there is no information telling the tool that "fechaacceso" and "dataacceso" are equivalent. In order to support this, editors need to provide the corresponding templateData. In particular, the "dataacceso" of the Galician template needs an alias named "fechaacceso" for Content translation to know they are equivalent.

The underlying problem in this case is that templates were not designed to work well across languages, so we rely on metadata to do the best possible mapping.

Hope this is helpful. Pginer-WMF (talk) 13:34, 22 March 2019 (UTC)

Thanks Pginer, I have added some data to the TemplateData and some problems are fixed.

But we have a problem with the words with incorrect translation, you know that "una" and "para" are words with a lot of appearance in spanish. Could we ask to somebody to notify about the problem? Bye. Elisardojm (talk) 01:01, 23 March 2019 (UTC)

Hi, could somebody help me to fix the incorrects words translations from Spanish to Galician? It's an important issue to be fixed because "una" and "para" are words very used in spanish, and that problem adds and extra work to users that could be easily avoided. Where can I notice about that issue for it be fixed as soon as possible? Do you know where I can ask @Pginer-WMF? Or with who could I talk? Thanks. Elisardojm (talk) 11:04, 25 March 2019 (UTC)

Each translation service has their own feedback channel:

• For Google, go to Google translate, type a sentence to translate and clicking on the translation you'll see the "improve this translation" option that allows you to report improved translations.
• For Yandex, you have a similar option. You can go to Yandex translate and you can click the pencil icon to correct translations.
• For Apertium, you can report issues in their Github repository. In particular, for the Spanish-Galician language pair, you can create a new issue here.

Since these are external services I don't know how effective they are at incorporating the feedback back into the services. Pginer-WMF (talk) 22:47, 25 March 2019 (UTC)

Thanks @Pginer-WMF, the problem is with Apertium, I have reported there about the issue. Bye. Elisardojm (talk) 10:25, 27 March 2019 (UTC)

Major problems during en => tr translations

I really like the tool as it made the translation process much much easier compared to manual translation, but I've just noticed some very major problems while using en => tr content translator;

First of all, virtually %80 of the citations do not work after translation. It seems to work when I click on the small number but when I click ''edit'' or upload the article, it states ''boş kaynak'' which means empty source.

This happens when the source contains specific templates like {{web source}} or {{book source}}, and its simply translated to ''web kaynağı'' or ''kitap kaynağı'' templates, but the information within the template gets deleted during this process. In the article, after uploading, I can only see {{web kaynağı}} template and there is no source in it. In addition, those templates are translated even though they are supported in tr.wiki.

Also almost always I encounter spaces after punctuation marks after translation. It's really time consuming to delete every space after citations, virgules, dots...

Lastly I'm not sure if that's intended but when I choose to give a red link to an article that can be found in en.wiki but not in tr.wiki the red link contains the English phrase, not the translated one.

For example, during translation of [[collar]], CX translates it as [[tasma]] which is written in grey as its not found in tr.wiki. When I choose it to make it a red link for others to create, new link becomes something like [[Collar|tasma]] and not [[tasma]]. This is so frustrating and time consuming to correct.

I've been using the last version on Google Chrome and Safari btw.

thanks for your help! Gogolplex (talk) 21:29, 18 March 2019 (UTC)

Hi,

Thanks a lot for the feedback.

For templates, you can try adapting the templates for work with Content Translation using the instructions at Content translation/Templates. See also https://phabricator.wikimedia.org/T214581

The problem with extra spaces is known and tracked in https://phabricator.wikimedia.org/T213694

The problem with links are tracked at https://phabricator.wikimedia.org/T197787 Amir E. Aharoni {{🌎🌍🌏}} 06:49, 19 March 2019 (UTC)

All suppress

I must suppress step by step : its too long ! How I can all suppress in one command please ? Speltdecca (talk) 06:46, 21 March 2019 (UTC)

What are you trying to suppress? Amir E. Aharoni {{🌎🌍🌏}} 10:23, 21 March 2019 (UTC)

when I do a translation,

from a language 1 to a language 2, (en -> fr, for exemple)

once the translation is finished,

I save the translation,

So far so good,

then,

when I start a new translation,

on the left page, I have the original page to translate (language 1 or en), but on the right page,

there is still the old translation of my first translation in language 2 (fr) of my first translation, which I have to delete section by section.

I would like to be able to delete (suppress) everything at once this language 2 (fr) and start the new translation right away

Speltdecca (talk) 12:16, 21 March 2019 (UTC)

This is quite strange. Every time you start a translation of a new article, the column of the target language is supposed to be empty.

Can you please say which article are you actually translating, and to which language? Amir E. Aharoni {{🌎🌍🌏}} 17:51, 21 March 2019 (UTC)

for example, when I translated the page in https://en.wikipedia.org/wiki/Neo-Assyrian_Empire Cx couldn't translate the infobox « {{Infobox country », so I copied and pasted the « {{Infobox country » into , I removed the « {{ » and now, Cx kindly translated all the lines of the « Infobox country » that after I put back in the page https://fr.wikipedia.org/wiki/Empire_n%C3%A9o-assyrien (with {{).

En:Neo-Assyrian Empire

Fr:Empire néo-assyrien

en:Wikipedia:Sandbox

Fr:Empire néo-assyrien

Similarly, when I translate tables that are too long, like here: https://en.wikipedia.org/wiki/Biblical_manuscript#Earliest_extant_manuscripts, Cx was telling to me as "error", so I cut the table into five parts, I put it on , I translated on the same page the 5 parts then I pasted back the 5 parts and here is the result: https://fr.wikipedia.org/wiki/Manuscrits_bibliques.

En:Biblical manuscript#Earliest%20extant%20manuscripts

en:Wikipedia:Sandbox

Fr:Manuscrits bibliques#Les%20manuscrits%20les%20plus%20anciens%20qui%20existent%20encore

En:Wikipedia:Sandbox Speltdecca (talk) 22:06, 21 March 2019 (UTC)

Translation

I want to create templates by translation from french wikipedia to the haitian wikipedia. How to do , please? I know only content translation. 90.44.11.151 (talk) 18:21, 21 March 2019 (UTC)

Hi!

I need some more detail to understand what you are trying to do. Please confirm whether you are doing one of the following or something else:

a) You are trying to translate a Wikipedia page from French to Haitian. The original article in French contains a template that is not transferred to the translation when you try to add the paragraph.

b) You want to provide a new template for Haitian editors to use in their articles, and you want to create such template based on a template available in French Wikipedia. Pginer-WMF (talk) 13:05, 22 March 2019 (UTC)

case b; I want to create Haitian templates based on templates available in French Wikipedia. Gilles2014 (talk) 22:12, 22 March 2019 (UTC)

In particular, we want to refresh the homepage of the haitian wikipedia and have the same presentation as the french portal on Haiti : https://fr.wikipedia.org/wiki/Portail:Ha%C3%AFti. This French portal is structured with templates that don't exist in the Haitian wikipedia... Gilles2014 (talk) 22:35, 22 March 2019 (UTC)

Content translation is not supporting the creation of a new kind of template, but there are considerations that will help support better such templates when found in a translation. For the new template you may want to:

• Connect the templates on Wikidata, for Content translation to know which is the equivalent template.
• Add TemplateData information to the new Haitian template. In particular, add aliases with the French name for each parameter. In this way, Content translation knows which parameter to copy the information into.

This process is a bi complex, and we are working on improving the documentation about it. Hope this helped a bit. Pginer-WMF (talk) 18:12, 29 March 2019 (UTC)

Restricted to extended confirmed editors on the English Wikipedia?

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'd like to translate a Chinese wiki entry into English. When I use the content translator tool, on the top of the page it warns me that "Translate page - Note: This utility is currently restricted to extended confirmed editors on the English Wikipedia, see WP:CXT for more information."

I am not an extended confirmed editor on the English wikipedia; I got an account only a week ago. However, it seems that I am able to use the translation tool in the same way when I used it to translate an English wiki entry to Chinese a couple days ago, except that the machine translation is turned off, but my understanding is that machine translation is turned off for everybody. So what does that warning on the top of the page mean? Would I be unable to submit my translation once it's done? SomeNeutrinos (talk) 00:52, 22 March 2019 (UTC)

The message means, You cant publish the translation. Hans Haase (有问题吗) 00:54, 22 March 2019 (UTC)

Opps. Thanks for clarifying, Hans Hasse. A long way to go before I get to translate a Chinese page into English, it seems =( SomeNeutrinos (talk) 00:57, 22 March 2019 (UTC)

You need 500 edits in the EN-WP. Hans Haase (有问题吗) 01:01, 22 March 2019 (UTC)

@SomeNeutrinos You can translated into English, but you have to first publish to a draft by clicking the gear icon. After the article is good, you can move it to the article space. Amir E. Aharoni {{🌎🌍🌏}} 07:15, 22 March 2019 (UTC)

Huh, I am getting mixed responses here, but it seems like you work at Wiki, so I am gonna believe you & give it a go, perhaps with a shorter entry than the one I planned to translate at the beginning. Thanks! Will update the post when I complete my first Chinese to English translation. SomeNeutrinos (talk) 18:27, 22 March 2019 (UTC)

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

Mathematics

In general, the tool doesn't provide a full support of mathematical formulas.

At least, this is my experience with the use of the tool from French, English and Spanish to Galician. Julrivas (talk) 12:28, 22 March 2019 (UTC)

Thanks for the feedback, @Julrivas.

Support for math formulas is not optimally supported currently. We have plans to improve support for math and other kinds of specific content such as chemical notation, music scores, poems, timelines and more. However, we are currently giving priority to supporting general elements that appear in all kinds of articles such as references or templates, as opposed to those elements that are used on a more specific knowledge area.

Meanwhile it is very useful for us to better understand which specific elements are most frequently translated, and which kind of support users need. So feel free to share any particular example that helps us to identify the needed improvements.

Thanks! Pginer-WMF (talk) 12:59, 22 March 2019 (UTC)

Hit Abuse filter 233, saying inappropriate interlanguage links

Green hand here.

Translation from English to Chinese.

The page is The Young Person's Guide to the Orchestra. The translated but unable-published draft page is here.

Is this a problem? 107.182.187.201 (talk) 14:11, 23 March 2019 (UTC)

Sharing

Is it or could be possible to share Context translation with other wikipedists? So we can work together on one page that need to be translated into another language. Thank you. Ivanhoe2012 (talk) 15:15, 23 March 2019 (UTC)

Unable to publish a translation

Hello! Finished translating an article about OK gesture from eng to ru, but unable to publish it.

Error message says: "Автоматические фильтры правок выявили проблемы в содержимом вашего перевода. Информация: Hit AbuseFilter: Запрет на редактирование Template CSS"

Please help. EgorKanov (talk) 20:04, 23 March 2019 (UTC)

Search the article for the blacklisted reference, then enter the CXT with Your translation. Mark the reference [x] als delete it. Make sure, it is used once or delete all other used of this reference. In the CXT You can copy any reference the form source in the left column and paste into the translation. Hans Haase (有问题吗) 00:24, 24 March 2019 (UTC)

thanks, but what exactly is CXT? EgorKanov (talk) 14:22, 24 March 2019 (UTC)

Terribly sorry, but I'm hopeless at such things. Can I just pass the draft to somebody to fix the tech details?) I cant even save it as a draft! it keeps giving the same mistake...

I also apparently have fixed all the errors in references, but it didn't fix the problem. Could you please have a look at the source code of the translation? Do you have means to do so? Can I somehow share the work with others?

https://ru.wikipedia.org/wiki/Special:ContentTranslation?page=OK+gesture&from=en&to=ru&targettitle=OK+%28%D0%B6%D0%B5%D1%81%D1%82%29&version=2

that's the link, if it is of any value. I apologize in advance for the inconvenience.. Could you help me out, mate? EgorKanov (talk) 17:09, 24 March 2019 (UTC)

spanish to english

The  translate tool/ wikipedia's add on, is not working in the Spanish to English language.

Article in Spanish: [2] needs translation into English. Gankeame (talk) 20:35, 23 March 2019 (UTC)

You need 500 edits in the EN-WP. Or publish as personal draft. Hans Haase (有问题吗) 00:11, 24 March 2019 (UTC)

Raw formatting

We would like to see raw wiki formatting, if possible. Thank you. BiotronikaJZ (talk) 06:06, 24 March 2019 (UTC)

Not possible. You can fix it later, when published. You can copy and paste references manually. You also can used hot keys for formatting text. But, You cant insert stuff like formulas of mathematics, tables are difficult. Source editing is possible after publishing. You also can publish as common draft or personal draft. Hans Haase (有问题吗) 08:04, 24 March 2019 (UTC)

Temporary Solution to Uppercase Letters Error

Hey!

I'm translating to portuguese a page about the BTU (British Thermal unit), but it doesn't let me publish giving an error in multiple paragraphs that states "Translation only contains uppercase letters".

Haven't found any button that enables me to change the code for the tables or the titles, which I believe could be the problem. Making a guess, I'll say that it could be something broken with portuguese. StarFighterEAMTS (talk) 17:02, 24 March 2019 (UTC)

The title to "External Links", for exemple, is translated as "Links externos" or "Ligações externas", but none of these forms is accepted, returning the error that it has only uppercase letters. StarFighterEAMTS (talk) 17:06, 24 March 2019 (UTC)

Okay. It surely was a bug.

I tried changing the translation in "External Links" once more leaving the title in lowercase letters only. After the page saved my alterations it was still showing the error, so I reverted to "Ligações Externas" again. The error then disapeared. It worked for all other paragraphs.

Hope it helps someone :) StarFighterEAMTS (talk) 17:13, 24 March 2019 (UTC)

Unable to publish a page

Hey!

The error I get is saying that there's a improper statement about body parts. I verified it and found nothing. Translated the whole page and saw nothing about it.

I'm translating a page about BTU. StarFighterEAMTS (talk) 17:21, 24 March 2019 (UTC)

Translation contains code rather than templates

Spotted a problem with this translation in that it included lots of <code> type entries rather than generating an appropriate call to a cite template. Keith D (talk) 00:33, 25 March 2019 (UTC)

Specifying the right Infobox to use in the translated language

Hi,

using the Content Translation tool from EN to FR to translate https://en.wikipedia.org/wiki/Sad_Hill_Cemetery

One part that I'd find convenient to be automatically formatted is the Infobox.

On this page, the Infobox_cemetery would find its equivalent as Infobox_Cimetière in French, but the tool does not (seem to) provide a way to specify which Infobox is to be used in the target language.

- Is there a way to tell the tool what Infobox to use in the translation?

- If not, is there a way to add the FR Infobox manually while staying in the tool (and without interfering with its "work")?

Thank you. Zenkutsu (talk) 02:18, 26 March 2019 (UTC)

Thanks for the feedback, @Zenkutsu. I'll reply to your questions below:

> - Is there a way to tell the tool what Infobox to use in the translation?

Yes. Right now is a bit complicated, but we'll work to improve documentation in this area.

For Content Translation to successfully transfer a template into another language it needs the following:

1. Templates need to be connected in Wikidata in order to find the corresponding template in a different language. In the case of the Infobox cemetery template you can see that French appears in the list of languages, and you can check this in Wikidata.
2. Template parameters need to be mapped for Content translation to copy the information of each parameter into the equivalent one. For this, unless parameters have exactly the same name, Content translation relies on metadata. In this case, the French template needs TemplateData information to be added. In particular, each parameter needs an alias with the corresponding name in English.

Templates were not build to work across languages, and we rely in this metadata to connect the dots.

> - If not, is there a way to add the FR Infobox manually while staying in the tool (and without interfering with its "work")?

You can add any template. In the edit bar on the right sidebar you'll find a "..." menu that allows to add templates among other elements.

Please let us know if further information is needed. Pginer-WMF (talk) 01:07, 28 March 2019 (UTC)

I'll try that, thank you. Zenkutsu (talk) 05:49, 28 March 2019 (UTC)

Translation of Sources

Hi, I noticed the Content translation tool has a hard time with references - I was working on German to English (via Simple English) for the article wikipedia:The Party of Moderate Progress Within the Bounds of the Law, and I noticed that it often had a hard time dealing with translating references. Would the team be open to having some sort of separate view for sources, or to having the option to import references untranslated? Furicorn (talk) 03:00, 26 March 2019 (UTC)

Absolutely agree, translating sources is seriously painful. In fact, I'm not even willing to do it. If the source is in english, how am I going to translate that? Seems like a bug more than anything to do with translation. 193.166.253.150 (talk) 06:53, 26 March 2019 (UTC)

Thanks for the feedback.

Currently reference contents are translated when they should not be. There is a ticket capturing the issue and we'll be changing the default behaviour. If you have more details about this issue feel free to share them.

Currently different templates on each wiki are used to structure different kinds of references. This makes it hard for the tool to find the corresponding templates for each language and determine which parameter to copy into which one. As a result some information is lost in the process. We plan to make several improvements related to references to make this process more solid.

@Furicorn, regarding the "separate view" for sources, do you refer to a view that shows side by side the information from the source and target reference to map it (copy, translate, etc.) more easily? As we refactored the tool to use Visual Editor in the new version, we integrated many of their tools as they are, but we can consider further adjustments for adapting some to the specific needs of translation. Such a view would require some effort to build and would rely on our capability to find equivalent parameters. Once we make more solid the parameter mapping process, which will improve the automatic transfer of templates we'll reevaluate how much a custom editor may still be needed. Pginer-WMF (talk) 00:56, 28 March 2019 (UTC)

So I'd point you to this diff. In this diff, I have a huge chunk of text that I imported via the translation tool, and have been doing a bunch of cleanup on the sources. Most of these sources were not in any kind of template, they were just freehand sources between <ref> tags. One example in reference 40 is that the ref name of "Riff S. 68" was translated to "Reef S. 68", as though the last name were itself a translation target. Or, reference 25, 34, or 37 start with an abbreviation (such as German "z.B." for "e.g.", or "S." for "p.") but the translator seems to ignore anything after the first period.

I think the best behavior for now is for the tool to avoid translating anything between <ref> tags, because beyond even what I've encountered, you've said, there are a lot of complications with inter-language citation template differences. And actually, even if all the parameters are mapped, maybe the correct behavior there is to only use translation for citation templates, but then have a distinct UI for dealing with freehand references. Furicorn (talk) 03:50, 28 March 2019 (UTC)

Cann't publish translation

HI!

Translate article

Annie van der Meer (NL) -> Енні ван дер Мер (UK)

Chrom browser; like use v.2 of CT

After corrected article - clicked on PUBLISH, button is Gray and nothing happening more.

Reload - all saved, but no errors messages, article not published. Do again - and again Gray button and nothing more...

With respect

Всевидяче Око Всевидяче Око (talk) 11:21, 27 March 2019 (UTC)

Do this translation by hands. Why don't pub from CT - don't konow(

With respect

Всевидяче Око Всевидяче Око (talk) 12:04, 27 March 2019 (UTC)

Unknown unrecoverable error has occurred. Error details: You do not have permission to create new pages.

Could have received this message before actually letting me create a whole translation. NebuchadnezzarIII (talk) 06:33, 31 March 2019 (UTC)

Into which language are you trying to translate? Amir E. Aharoni {{🌎🌍🌏}} 18:24, 31 March 2019 (UTC)

English. Translated an article from French. NebuchadnezzarIII (talk) 22:05, 1 April 2019 (UTC)

Publish as personal draft, using the gear button. You need 500 edits in the English Wikipedia to skip this workaround. Hans Haase (有问题吗) 06:52, 31 March 2019 (UTC)

Tried this, but I'm still struggling when it comes to publishing the article as a new page. NebuchadnezzarIII (talk) 22:06, 1 April 2019 (UTC)

How can I change machine translation language setting

Hi. In meny case, machine translation from other langagge to Japanese outputs unusable/incomprehensible. Is there a way to change language translate to? I would like change translate language to in a translation. thanks. Suisui (talk) 07:51, 31 March 2019 (UTC)

Yes, in the CXT main menu, You see "Start new Translation", click the on the language and change it. You need another click to expand the list. Not all languages are supported.

https://en.wikipedia.org/w/index.php?title=Special:ContentTranslation&campaign=contributionsmenu&to=en

Click the "All›All" as from and to language to translate from and into. Hans Haase (有问题吗) 13:46, 31 March 2019 (UTC)