Talk:Content translation/2019/02

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).
• Which version of Content Translation are you using. If you see "Try the new version" on the dashboard, it's version 1. If you see "Using the new version" on the dashboard, it's version 2.

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)

This tool is not user friendly

Very difficult to use, understand and save to a sandbox. Where are the buttons to explain all this? Especially since I didn't say I am a translator... the tool just asked me to upload an article to translate, so I found a notable subject that didn't exist on the site and I uploaded an English article and clicked into the translate. Then I had to delete a bunch of frames, etc. It says it won't publish, so why did I waste my time? Don't ask me to upload an article to translate, spending an hour trying to edit in a language I don't understand, and then say it's not good enough. Maybe you should have asked me if I'm a translator? Tokaria (talk) 05:12, 3 February 2019 (UTC)

What's the error? can you please post a copy of the error message? FF-11 (talk) 10:11, 3 February 2019 (UTC)

Sandbox: personal draft. Use the gear button. Hans Haase (有问题吗) 10:35, 3 February 2019 (UTC)

Can this tool be disabled partially for languages?

Hi kindly tell me if there is a way to disable direct translations / uploads to swwiki. Or who is it we have to talk to. We get again and again horrible stuff from someone who wants to be helpful and uses the content tanslation and uploads it. I have used the tool myself for swwiki and for certain kind of texts it can be seen helpful and can save some time. Generally the results for Swahili are bad, but if you work thru it, it can help on short texts with simple sentences. Else not.

We are a small wikipedia and we do not have the capacity to cope with long articles that are full of gibberish. I think it would be helpful if someone who uses that toll can not simply click "upload" but has to move it around a bit more. This being a wikimedia tool obviously makes it easier to click "go" and feel good about it. People who upload bad stuff have no bad intention but either do not really know the language (but feel they help us to get a new topic) and the direct upload helps the illusion that this is something different from other google or other machine translations which we discourage strongly in our welcome message for each new user. Or it is people who send a long article thru the too which tirs them too much to really read all. Also here the "wikimedia-tool-character" aids the illusion it is somehow okay to send it in. So how to switch the direct upload off for swwiki? Kipala (talk) 18:42, 3 February 2019 (UTC)

Thanks for the feedback, @Kipala.

As you mentioned, the purpose of machine translation is to serve as a starting point for users to review and create a good translation. In the new version of Content translation we have improved the mechanisms to encourage users to review the initial translations: warnings are shown for each paragraph that users don't edit enough, and if the user decides to still publish the article is added to a tracking category for the community to review (you can check the tracking category for Swahili). In more extreme cases, publishing is not allowed if the content remains mostly unmodified for the whole document.

We are happy to hear from the community experiences and identify how to better adjust these thresholds, or find new mechanisms we can support. We want to reduce the number of problematic articles without limiting those users that make a good use of the tools.

The current stats for Swahili show a low number of articles created with the tool (rarely more than one per week). We'll keep an eye on the number of translations created, the ones that need review and the deletion ratios.

Thanks for your feedback and for using the tool! Pginer-WMF (talk) 10:53, 5 February 2019 (UTC)

How do I turn those warnings off? I use this tool for wikilinks and then translate the article into a user draft, but after taking 10 minutes to accept all warnings, the tool prevents me from saving the articles in the user draft. Emanuele676 (talk) 18:34, 5 February 2019 (UTC)

Hi @Emanuele676

It makes sense not to apply some of these limitations when users are publishing into the user namespace. I created this ticket to capture the idea. Feel free to add further comments and track the progress of the ticket.

Currently, errors and warnings use different thresholds. The error that prevents from publishing is only applied when the content for the whole article is 99% unmodified. So making some small modifications anywhere should avoid this limitation.

I'm also curious to hear more details about why you prefer to do most of the editing outside the tool. With the new version, the editing surface used is based on Visual Editor which brings many of the tools for content editing and creation that were missing in the past. Have you given a try recently?

Thanks for your feedback! Pginer-WMF (talk) 11:21, 6 February 2019 (UTC)

I find it easier to translate without Visual Editor but by editing the wikitesto. Emanuele676 (talk) 12:02, 6 February 2019 (UTC)

An exemple of things that cannot be done with the Visual Editor is the clean up of the syntax of the references (no refnames, impossible ti suppress the "span" unuseful on french version of WP for instance)..

Although, some or most of the internal links have to be clean up (cf. [[The Times]] which has to be restitued in french ''[[The Times]]''. Using the VE, and adding italics, the result is [[''The Times'']] that is not satisfactory..

Here is a result using VE : The Times (code= [[The Times|''The Times'']].) Pa2chant.bis (talk) 18:27, 11 March 2024 (UTC)

Changes in the original article -> hours of work lost

Hello,

I have been translating this article: https://en.wikipedia.org/wiki/Ray_tracing_(graphics) into Bulgarian. Its structure has apparently changed in the meantime. Most of my translation is now aligned to the wrong paragraphs of the original and I have no way to move it where it should be or to reuse the translated text. Trying to cut and paste parts of the translation to the correct places works only partially, and completely breaks the alignment anyway. When I have this situation:

Segment A | Translation B

Segment B |

and try to cut and paste the incorrectly realigned Translation B to its correct location, the following happens:

- There is no way to copy the entire Translation B if it contains references. They are lost. I can copy only the parts between them.

- There is now no way to start a fresh translation for Segment A (which has been newly inserted in the original and has actually not been translated).

- There is no way to get correct alignment between Segment B and the moved copy of Translation B (even if it contains no references and has been pasted in its entirety).

I use Firefox under Windows 10. I think I'm already using the new version of the Translation tool since I see no prompt to try it. I have a long list of errors in the browser console but I don't know if they are relevant since the mixup has already happened when I re-opened the translation for the first time today and have closed and opened it again several times.

Is there a way to fix this without losing my existing partial translation? Mihail Balabanov (talk) 11:29, 4 February 2019 (UTC)

Thanks for your feedback, @Mihail Balabanov.

As you mentioned the origin of this issue seems to be that the original article changed significantly. Content translation is expected to detect these cases and provide the option to continue with the old version or start a new translation, but not to break the paragraph alignment in any case. Although this works in many cases, there are still some issues and we are working to make this process more solid (more details in this ticket).

Based on your comment it seems that the old version of content translation is used. With the new version, copying content across paragraphs should work much better (i.e., keeping references and other rich text elements). The new version was enabled by default recently, but translations started with the old version still use that one to avoid data conversion issues.

One way to get the content out of the translation is to publish it under your user namespace. Then deleting the translation and starting again with the new version could be a possible path forward.

Content translation was created to make editors more efficient, and it is sad to hear when some of the issues result in wasted efforts. We hope that the current improvements solve these issues. Thanks for trying the tool and providing useful feedback! Pginer-WMF (talk) 12:07, 6 February 2019 (UTC)

Hi, thanks for your reply.

What is meant by publishing in my user namespace? Is it selecting "personal draft" as a target from the gear menu and then clicking Publish?

Also, can I suppress automatic translation of the references? For the body of the article, MT is a very convenient starting point, so I don't want to disable it entirely, but when I reuse citations from the original article, their titles should stay in the original language of the citation (which may even be different from that of the article itself). Mihail Balabanov (talk) 13:19, 6 February 2019 (UTC)

Regarding the user namespace, you are right. You can select the "personal draft" option from the gear menu. In the future we plan to make these options more descriptive.

Regarding the control to apply the automatic translation to the references or not, is also in our plans but it may take some more time.

Thanks for the feedback! Pginer-WMF (talk) 13:59, 6 February 2019 (UTC)

I published the article to my user space, deleted the translation and tried to start a new one, taking care to specifically check that the new version of CXT is selected (I still think I was already using the new version when the above problem occurred). Rather than beginning with a free translation space though, I was presented with my broken partial translation again. Do I have to remove the published version from my user space? I don't want to delete the old text entirely because I want to use it as a source for copying, to avoid redoing all the work to this point. Nevertheless, I also want to have a clean slate for the new translation. I'm currently stuck with the broken translation. Any ideas how to proceed? Mihail Balabanov (talk) 15:54, 8 February 2019 (UTC)

Update: I found a way to continue from the misaligned translation by resetting the translation unit by unit using the drop-down translation options menu on the right. Then I copied the correct translation sentence by sentence from the version in my user space to avoid messing up the sentence-level alignment. This took care of 'importing' the existing translation to the correct paragraphs. Then I continued through the untranslated parts and I ran into some more glitches:

• Translating segments with mathematical notation in them is often impossible: all translation options (including the one for copying the original as-is) randomly result in an empty translation, or one with missing formulas, or one where formulas are replaced by closing </img> tags. It does not happen always but often enough to render the process unworkable.
• Translating image captions is difficult because the arrow keys and mouse clicks don't work in them as expected; it is nearly impossible to select text for replacement and some lines are entirely unreachable (both unclickable and untraversable by arrow keys).

Sorry if these are known problems. Mihail Balabanov (talk) 00:36, 10 February 2019 (UTC)

How do you reuse reference in content_translation/V2?

I could update later when I publish my translation, but what are my options? I find a particular reference used with different ref number (eg appearing as [2] and [3]) in an article I am working on CT ver2. but pointing to the same website, so I wish to reuse one particular ref instead of leaving the erroneous refs. Just as the standard editing. What is the basic idea, that translation comes first then editing comes later, on published namespace?

1) Do I edit the original /en page and perge, then go back to Content Translation and translate the updated English text? Would there be any time rug between the time I update English page and the translation original on CT perged?

2) Is it best/time saving to publish such translation with known edit error, then edit on translated and published page?

Omotecho (talk) 06:36, 5 February 2019 (UTC)

The CXT produced a copy of every named reference. Simplify those references after publishing.

• Master: ref name="refname" … /ref
• Slaves: ref name="refname" /

The CXT made each reference to a master.

Manually search for masters als make them slaves, but keep one necessary master alive. Then You can use up to 26 slaves per master, a the alphabet can assign a letters to it. Hans Haase (有问题吗) 08:18, 5 February 2019 (UTC)

Thank you for your crisp and timely advice, and yes, it sounds reasonable. Great to work with CXT, I enjoy using it, good to translate articles with terminology reused many times as in art history. Cheers, and case solved for me. Omotecho (talk) 09:08, 5 February 2019 (UTC)

Not sure how to use this

I only did a brief try on the English Wikipedia, but the tool seems to be paternalistic/restrictive to a degree that I cannot find any use for it. It doesn't allow me to write in wikitext (I can only work efficiently in wikitext). It doesn't allow me to use machine translation, although for me it would be quicker to edit machine translated text than to translate from scratch, with the same end quality. Still, it will apparently translate wikilinks, images, and references for me, and that would be a great help. Unfortunately, it doesn't allow me to view the wikitext, nor am I allowed to save the draft to my user account sandbox without having translated everything within the tool (by hand, without seeing wikitext). Do I miss something? Is there a hidden option to view the wikitext at least? Jens Lallensack (talk) 14:12, 6 February 2019 (UTC)

Thanks for the feedback, @Jens Lallensack. I try to add some details to your different points:

Wikitext

Supporting wikitext editing won't be trivial since the content is annotated for the translation process (e.g., to know which paragraph in the translation corresponds to in the original text). That makes it hard to include that metadata in wikitext without crowding the content, and keeping it in place after content is added or removed.

Machine translation

We are enabling machine translation on different languages gradually. Hearing from community requests will be useful to guide this process. I captured your comment in this ticket.

Saving to user namespace

You can select the "personal draft" option from the publishing settings menu (cog icon next to the "publish" button) to publish under your user namespace. The threshold for publishing is to have less than 99% of unmodified content for the whole document, so a few modifications may be enough to publish. The other warnings shown on a paragraph basis (when unmodified content is higher than 80% for that paragraph) but they do not prevent from publishing (although publishing content will be added to a tracking category for communities to review). We have plans for not applying these restrictions when publishing on the user namespace (more details in this ticket). Pginer-WMF (talk) 16:58, 6 February 2019 (UTC)

Thanks for the detailed answer, this is very helpful! Jens Lallensack (talk) 21:56, 6 February 2019 (UTC)

Hi i can’t save my translation.

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 Can’t save my translation.i have this error:Unknown unrecoverable error has occurred. Error details: You do not have permission to create new page. Amirsara (talk) 12:45, 10 February 2019 (UTC)

Publish as personal draft, using the gear button. If Your target language is English, You need 500 edits in the EN:WP due restriction. Hans Haase (有问题吗) 12:48, 10 February 2019 (UTC)

Thanks Amirsara (talk) 12:51, 10 February 2019 (UTC)

érosion altération? avec

tectonique des plaques

ou roche des naissances magmatique se que n’appelle 1er Roches sous action des mouvements du manteau supérieur

Appel Abdenour.abdelkader (talk) 13:48, 27 February 2019 (UTC)

??? Hans Haase (有问题吗) 13:50, 27 February 2019 (UTC)

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

descriptions and labels

this tool use description from wikidata in english, can it be in my lang? and I want the tool to suggest the label as a translation title. Mr. Ibrahem (talk) 15:49, 10 February 2019 (UTC)

On the source language click "edit links" under the offered languages. You will be redirected to Wikidata. When competed the translation, add the description there. Hans Haase (有问题吗) 16:04, 10 February 2019 (UTC)

it's already there Mr. Ibrahem (talk) 10:54, 13 March 2019 (UTC)

Is it offered to translate (grey) or does it already exist (blue). Well what article we are talking about? Hans Haase (有问题吗) 10:56, 13 March 2019 (UTC)

No way to annotate a suggested article as existant

My suggested-pages tab will often bring up pages that already have a well-fleshed-out article in the target language. I can't find any way to indicate that this translation page already exists, besides the "X" on the right side of the suggestion which just seems like a way to dismiss the suggestion. Is there a way to mark a translation as "already complete"? 73.129.158.144 (talk) 16:29, 10 February 2019 (UTC)

Thanks for the feedback. Suggested articles are intended to be articles that do not exist yet in the target language. Content translation relies on Wikidata to identify corresponding articles across languages. When we have found the issue you described in the past it has been because the language versions of the article were not connected through Wikidata. More details are captured in this ticket.

Feel free to add more comments or details there based on the specifics of your case. Thanks! Pginer-WMF (talk) 14:40, 13 February 2019 (UTC)

Tranlation failed

Gave the new CT a second chance - and it failed to translate at all. Trifles (play) from english to russian. Tried many times with Google and Yandex - "Automatic translation failed!". Old version is translating (and this article too). I will delete unfinished translation and keep this article untranslated for a while to reproduce error. Igel B TyMaHe (talk) 10:27, 11 February 2019 (UTC)

2 days passed. "Automatic translation failed!". This particular article can't be translated. Unusual that CT cant't see paragraphs in this article and tries to translate all the text. Igel B TyMaHe (talk) 10:30, 13 February 2019 (UTC)

Thanks for the feedback, @Igel B TyMaHe.

Content Translation divides content into paragraphs, but it is failing for this particular issue. The whole document is treated as a paragraph and that probably exceeds the character limit for translation service requests.

Dividing the articles into paragraphs has been working quite reliably, and I'm not sure what may be causing this particular article to fail. I created a ticket to capture this issue and do further investigation. Feel free to add further comments and track the progress of the ticket.

Thanks! Pginer-WMF (talk) 15:03, 13 February 2019 (UTC)

Permission to create new pages

How can I get permission to create new pages/translate articles from Russian into English? Now once I try to publish the translation I get the message "An error occurred while publishing the translation. Please try to publish the page again. Error: You do not have permission to create new pages." Mariaafp (talk) 13:15, 11 February 2019 (UTC)

Publish these as personal draft. Hans Haase (有问题吗) 14:33, 11 February 2019 (UTC)

"In Progress" translation will not delete

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 have a translation which was published almost 1/2 a year ago... Will not delete. Can you help me delete it?

Shirazeh Houshiary

Thanks! TMagen (talk) 15:31, 11 February 2019 (UTC)

See other topics in this talk, how to work around to translate a temporary copy. Hans Haase (有问题吗) 18:07, 11 February 2019 (UTC)

Don't see any... I don't know why I would need a temporary copy though. TMagen (talk) 07:15, 12 February 2019 (UTC)

See Talk:Content translation/2018/10#h-Impossible_to_erase_and_re-compile_a_translations_with_full_of_bugs-2018-10-25T16:33:00.000Z also used in Talk:Content translation/2018/09#h-I_want_to_translat_Dimash_Kudaibergen's_page_from_English_to_Portuguese-2018-09-06T19:29:00.000Z. Hans Haase (有问题吗) 07:55, 12 February 2019 (UTC)

Neither of these topics are relevant. TMagen (talk) 11:43, 12 February 2019 (UTC)

This is how You can start a translation again. All other can not be solved at this time. Hans Haase (有问题吗) 12:49, 12 February 2019 (UTC)

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

Can't add superscripts to units of area on translation tool

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,

I am translating this article: https://en.wikipedia.org/wiki/Kawamata,_Fukushima from English to Spanish.

I'm using Firefox and version 1 of the translation tool.

I try to copy the superscripts from the source text but it changes it to normal numbers. For example: km² to km2

I even tried copying the superscript from other web pages but it keeps changing it.

Am I doing it wrong? or is there a native way to add these symbols? Toneriko98 (talk) 15:30, 12 February 2019 (UTC)

Regarding the input, copy it from anywhere and paste it into the Editor. Maybe is the SUP-Tags are ignored, or the "²" is converted the "2" by CXT or Google Translator. If not possible to solve it else, fix it after publishing. Inside the template, it is just a parameter name, using "km2". Hans Haase (有问题吗) 15:41, 12 February 2019 (UTC)

Ok, no problem. Thank you! Toneriko98 (talk) 20:28, 12 February 2019 (UTC)

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

לחיצה לא מזהה תוכן ולכן לא יוצרת תרגום אוטומטי בנסיון לתרגם

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.

---

לחיצה על שדה לתרגום לא מזהה תוכן ולכן לא יוצרת תרגום אוטומטי בנסיון לתרגם. זה משאיר אותי עם שתי פסקאות מתורגמות בלבד ותסכול רב. Ehud Amir (talk) 07:11, 13 February 2019 (UTC)

Sorry, Hebrew is not supported at the moment.

It also does not help to insert the URL line manually, to enforce a translation. Hans Haase (有问题吗) 08:40, 13 February 2019 (UTC)

What do you mean when you say "Hebrew is not supported"? Hebrew is supported. Amir E. Aharoni {{🌎🌍🌏}} 12:30, 13 February 2019 (UTC)

Got this massage. But in can clearly the this talk. Browser? (Chromium and Linux Mint.) Hans Haase (有问题吗) 16:56, 13 February 2019 (UTC)

i did a refresh and the previous translation was saved and in addition i succeeded completing the translation. thanks :) Ehud Amir (talk) 09:37, 13 February 2019 (UTC)

אהוד, אני מבין שהבעיה נפתרה. עם זאת, תוכל לפרט קצת מה הייתה הבעיה? באיזה מקום בדיוק לחצת כשזה לא עבד?‏

ומה פתר את זה? פשוט רענון של המסך?‏ Amir E. Aharoni {{🌎🌍🌏}} 12:31, 13 February 2019 (UTC)

כן, זה נפתר. הבעיה היתה שלחצתי על השטח המקביל מימין למקור באנגלית, כדי ליצור תרגום ראשוני, וזה לא הגיב בכמה וכמה פסקאות. כך קרה שנוצרה לי הודעה לפיה התוכן קצר מדי ולא מספיק לשם ערך. חששתי שאם ארפרש, הכל יימחק. הייתי נואש. בניגוד לאינטואיציה שלי, לחצתי רפרש. להפתעתי התרגום הקודם שלי נשמר וגם הלחיצה מימין למקור אפשרה הוספת תרגום מכונה ראשוני. כך השלמתי את הערך. כך שהבעיה נפתרה. תודה! Ehud Amir (talk) 07:39, 14 February 2019 (UTC)

Mai I ask what browser are You using? Did You install a dedicated language support? Hans Haase (有问题吗) 11:07, 14 February 2019 (UTC)

Hans, this is not relevant. It's resolved. Amir E. Aharoni {{🌎🌍🌏}} 11:37, 14 February 2019 (UTC)

Ok, I tried myself, let reduce the question to keep privacy "Did You have installed any special Hebrew language support?" Hans Haase (有问题吗) 19:24, 16 February 2019 (UTC)

See above: not relevant, resolved. Amir E. Aharoni {{🌎🌍🌏}} 19:30, 16 February 2019 (UTC)

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

Bug with translation tool

English

When I translated the article on Lukas Jacobs from Dutch to French, there was a bug with the translation tool:

https://nl.wikipedia.org/w/index.php?title=Lukas_Jacobs&type=revision&diff=53198485&oldid=52731206&diffmode=source

The translation has replaced the dutch page and not been created on the french Wikipidia. I use Firefox.

I have canceled and made the creation manually. But where does the bug come from?

In the translation tool, when I see my published traductions, it is well written :

Nederlands -> français

Thank you.

Français

Quand j'ai traduit l'article sur Lakas Jacobs du néerlandais vers le français, il y a eu un bug avec l'outil de traduction :

https://nl.wikipedia.org/w/index.php?title=Lukas_Jacobs&type=revision&diff=53198485&oldid=52731206&diffmode=source

La traduction a remplacé le texte en néerlandais et pas été créée sur le Wikipédia en français. J'utilise Firefox

J'ai annulé ma modification et fait la création manuellement mais d'où vient ce bug ? Est-ce moi qui ai fait quelque chose de mal ou juste un bug informatique ?

Dans l'outil de traduction, dans l'onglet avec mes traductions publiées, il est bien noté :

Nederlands -> français

Merci d'avance. Huguespotter (talk) 10:39, 13 February 2019 (UTC)

Thanks for the feedback, @Huguespotter.

Long time ago we had some issues of this kind but those seemed to be solved. I updated the relevant ticket with your comment for further investigation.

Thanks! Pginer-WMF (talk) 15:07, 18 February 2019 (UTC)

Impossible to publish my translation 'Hit AbuseFilter: Liza Veniza / Willy on Wheels'

Hello,

I was translating 'Cieszyn Silesia' [1] (en) to French with the Content Translation tool version 2 and when I clicked on Publish my translation, a red message appeared saying 'Hit AbuseFilter: Liza Veniza / Willy on Wheels'...

I use Mozilla Firefox but I tried with Google Chrome and it's the same.

Here is the message I got on the browser console:

'Error while detaching the browsing context target front: Connection closed, pending request to server1.conn0.parentProcessTarget1, type detach failed

Request stack:

request@resource://devtools/shared/protocol.js:1384:14

generateRequestMethods/</frontProto[name]@resource://devtools/shared/protocol.js:1545:14

BrowsingContextTargetFront<.detach<@resource://devtools/shared/fronts/targets/browsing-context.js:84:24

destroy/this._destroyer<@resource://devtools/client/framework/target.js:800:17

destroy@resource://devtools/client/framework/target.js:775:24

eventSource/proto.emit@resource://devtools/shared/client/event-source.js:128:9

onClosed@resource://devtools/shared/client/debugger-client.js:900:5

close@resource://devtools/shared/transport/local-transport.js:154:9

close@resource://devtools/shared/transport/local-transport.js:150:7

close@resource://devtools/shared/transport/local-transport.js:150:7

cleanup@resource://devtools/shared/client/debugger-client.js:300:9

detachClients@resource://devtools/shared/client/debugger-client.js:325:9

safeOnResponse@resource://devtools/shared/client/debugger-client.js:519:14

listenerJson@resource://devtools/shared/client/debugger-client.js:542:26

emit@resource://devtools/shared/event-emitter.js:178:15

emit@resource://devtools/shared/event-emitter.js:255:5

emitReply@resource://devtools/shared/client/debugger-client.js:823:31

callFunctionWithAsyncStack@resource://devtools/shared/platform/stack.js:61:10

onPacket@resource://devtools/shared/client/debugger-client.js:825:9

send/<@resource://devtools/shared/transport/local-transport.js:64:11

exports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14

exports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14

browsing-context.js:86:7'

What can I do?

Thank you. EriottoSz (talk) 01:17, 15 February 2019 (UTC)

Thanks for the feedback, @EriottoSz.

Pages created with Content translation are subject to the same automatically checks as those created with other tools. Abuse Filters are automatic rules that try to identify potential vandalism, and they are defined on each Wikipedia community (i.e., French Wikipedia rules are different from Japanese wikipedia ones).

The translation you are trying to publish contains some content that is identified as problematic by this particular filter. The content can be something you wrote or something that was transferred from the original article into the translation (s it may be hard to spot). Given the name, this particular filter seems related to this historical case of vandalism, but only French Wikipedia admins can see the specific rules. You can contact the French Wikipedia community to get more details and identify which may be the problem (either in your content or the filter rules).

Alternatively, you can do some trial and error by trying to publish part of your content to identify which part is the problematic one.

Regarding Content translation we plan to work on better surfacing where problematic content is, but the current infrastructure of Abuse filters makes it hard to do so in many cases.

I hope the above has been of some help. Pginer-WMF (talk) 12:22, 15 February 2019 (UTC)

Thank you, I will contact the French Wikipedia community and maybe try to publish different part of it as you said and see what's going on. EriottoSz (talk) 13:19, 15 February 2019 (UTC)

Error with a 'publish' button

I’m not able to publish my translation from English into Ukrainian as it says “Your translation couldn’t be published as it consists of too much unchanged automatically translated text”.

UPD Finally, it has worked (after endless attempts and restarting the page) and probably the problem occurred because of the large translation size and loads of bullet lists. Alice Redhotroof (talk) 20:56, 15 February 2019 (UTC)

On the right column, work on the checklist, until compete, then try to publish as personal draft, using the gear-button. And fix any blacklisted references. Hans Haase (有问题吗) 19:26, 16 February 2019 (UTC)

I can’t publish my translation

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 I can’t publish my translation I have this error Automatic edit filters have identified problematic content in your translation. Details: Hit AbuseFilter: Content Translation Edits Amirsara (talk) 06:40, 16 February 2019 (UTC)

Try to publish as personal draft, using the gear-button. And fix the blacklisted references. Hans Haase (有问题吗) 19:22, 16 February 2019 (UTC)

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

Ошибка в публикации перевода

Перевела с английского статью об Альваро Хиль-Роблесе. Сначала показалось предупреждение о слишком коротком тексте, тогда я дополнила статью по источникам, однако она так и не публикуется, кнопка "записать" не работает.

https://ru.wikipedia.org/wiki/Special:ContentTranslation?page=%C3%81lvaro+Gil-Robles&from=en&to=ru&targettitle=&campaign=interlanguagelink&version=2 --~ 80.232.245.102 (talk) 09:57, 16 February 2019 (UTC)

Try to publish as personal draft, using the gear-button. Hans Haase (有问题吗) 19:19, 16 February 2019 (UTC)

Sandbox translations

I am missing two possibilities. In English Wikipedia, this tool is not working, but why it cannot be used to translate something to sandbox. I would also appreciate to translate some texts, which are not going to be saved. I am talking here about the literature I use. E.g. Google Translate is very bad in translating from German, but this translator is good. Could it be that you enable some randomm translation of the pieceses of text (like Google Translate) do which wont be saved?

By the way, why I cannot use it on en.wp even I have extend confirmend flag there? Juandev (talk) 18:57, 16 February 2019 (UTC)

Any page beside the sandbox, inside user name space will be possible. You seem to have enough contributions to use the CXT. Already translated articles appear to seem to remain in a linked connection each other. So when using the sandbox for the translation, it will remember the previous translation. Always use a next page. Hans Haase (有问题吗) 19:18, 16 February 2019 (UTC)

Table is failing to translate

Tracked in Phabricator
Task T216583

I tried to translate en:w:List of national emergencies in the United States to DE. No problem to do the flowtext, but the interface version 2 is failing with the table. Too big? Connection not fast enough? Using Firefox 65.0.1 w/ Win 10 Matthiasb (talk) 00:50, 17 February 2019 (UTC)

The article contains a standard wikitable, no special template. On each singe field of the tab, doubleclick and translate. Also https://translate.google.com/ the automatic translation is depending supports 5000 characters only. Hans Haase (有问题吗) 21:03, 17 February 2019 (UTC)

No, that is not the solution. The tool does not transfer the table at all, so there is no way to doubleclick into the cells. Worse,after returning to the translation today, the tool does not recognize the corrresponding sections anymore; and clicking does only reproduces the section standing on the left, with no regarding on the order in the text. Matthiasb (talk) 23:39, 17 February 2019 (UTC)

I can not test it on a copy due JD and He3nry. Hans Haase (有问题吗) 05:33, 19 February 2019 (UTC)

Traduire une citation

Durant une phase de traduction en français de l'article https://en.wikipedia.org/wiki/User_experience_design j'ai eu la désagréable expérience de voir que ma traduction d'un bloc "citation" restait en anglais après enregistrement du brouillon de traduction... Bref comment faire SVP pour traduire CORRECTEMENT ce bloc citation ? Korido (talk) 19:30, 17 February 2019 (UTC)

It might be point of view or a translated citation can catch a bias in the way translating it, simply by getting wrapped in the adequate grammar of the target language. You can edit the published article. But, an automatic translated section often does not save automatically until any manual change is performed. Hans Haase (有问题吗) 20:56, 17 February 2019 (UTC)

@Hans Haase you mean I should just publish the translated article without the quote bloc and then go to the article and edit it ? 176.175.109.253 (talk) 22:15, 18 February 2019 (UTC)

Yes, the CXT assists in a lot of translation tasks, but it never can complete all for You. Hans Haase (有问题吗) 05:28, 19 February 2019 (UTC)

Translation services unavailable for German to English

Hi, I'm testing out translating some paragraphs from Partei für gemäßigten Fortschritt in den Schranken der Gesetze but I'm getting an error message that translation services are not available from German to English. Furicorn (talk) 22:27, 17 February 2019 (UTC)

Thanks for the feedback, @Furicorn.

We have been following a gradual process for enabling machine translation on different languages. Getting community feedback is very useful to move this process forward, and I mentioned your comment in this ticket to capture the request.

Thanks! Pginer-WMF (talk) 09:01, 18 February 2019 (UTC)

I thought I had responded to my initial comment, but I think I forgot to submit. When I followed the link, it looks like English wikipedia has specifically disabled machine translation on purpose, although it would be nice if I could use the tool to save machine translations, or copy the source code of the translation to my sandbox to work on. Furicorn (talk) 10:20, 18 February 2019 (UTC)

If you access the settings icon next to the publish button you can select your user namespace as destination, and publish there. For this particular case we are working on better communicating the problem to the user in order to provide more clarity and avoid discovering the issue after making the effort of translating.

An alternative is to translate from German into Simple English. There machine translation is available and you can decide whether to publish in the main namespace (if the style aligns with "Simple English" principles) or in your user namespace if you plan to copy the contents somewhere else. Pginer-WMF (talk) 14:59, 18 February 2019 (UTC)

Why does it translate to Croatian when I have Serbian selected?

Same as title of my post it is translating to Croatian even though I am clearly translating to Serbian. What is happening, it worked fine yesterday. Karakondzula (talk) 19:55, 18 February 2019 (UTC)

Thanks for the feedback, @Karakondzula. In order to know which is the exact problem we need some more details. Can you confirm which of the following issues are you experiencing?

a) Started a translation to Serbian, and when publishing, the final result is an article created in Croatian Wikipedia.

b) Started a translation to Serbian, and when adding a paragraph to the translation, the initial automatic translation provided is in Croatian.

c) Something different?

Thanks! Pginer-WMF (talk) 12:47, 20 February 2019 (UTC)

Hi Pginer-WMF, it's situation b) when I add paragraph it's initial translation is in Croatian. For some reason this doesn't happen for every paragraph. Few days before it worked just fine. Now in my last two translations there have been 4 or 5 paragraphs that were translated into Croatian.

Hope this helps resolve this issue.

Thanks for you help with this. Karakondzula (talk) 11:15, 21 February 2019 (UTC)

Bugs from recent es-en translation

Hello! Wanted to report a few bugs after using the CXT for this translation. Hope it can be helpful.

• When inserting a comment (either through the ellipsis menu or starting to type <!--), the viewport scrolls to the top of the screen
• When a link is blue in the original language and red in the receiving language (the translation), it would be nice to have easy access to using the local language's title, e.g., with a single click, to avoid the mess of trying to edit within the VE to to the same.
  • Additionally, would be nice to have {{Ill }} accessible from a single click as well, when I want to preserve the link to an article in the original language while indicating that it's still red in the receiving language.
• I start to translate a heading and realize I don't want the heading at all but there is no way to delete that heading. I can only leave it blank.
• Had a major issue in which {{Harvnp }} (in eswp) did not convert to {{Sfn }} (in enwp) even though the two are associated in Wikidata. Reference support is a big deal. In the last article I translated with CXT, one of the refs was missing from the right-hand column (don't believe it was deleted from the draft, just never appeared) and was hard to restore—it was just poof, gone.
  • re: harvnp, I was afraid to delete the redlinks to the template, hoping that they still retained their parameters. They did, so I regex'd the correct template name in later.
• Would be nice if common headings automatically translated (Véase también→See also, Referencias→References, Bibliografía, Enlaces externos, etc.)
• {{Commonscat }} didn't translate properly from eswp to enwp either
  • CXT displayed the template as wikitext and when I went to delete the text, the section retained the bullet point, which I cannot delete
• would be useful when publishing if the tool's edit summary also wrote out the originating wiki, for posterity
  • ideally, could include the associated {{Translated page }} template on the talk page, since users are unlikely to fill out the oldids on their own czar 22:52, 18 February 2019 (UTC)

Thanks for the feedback, @Czar. This is very useful. I'm adding more details below:

> When inserting a comment...

There was a similar issue with links that got fixed. However, I tried to reproduce the problem with comments and there was no jump. Maybe that was a temporary glitch. If the issue persists, please let us know indicating the browser you are using.

> When a link is blue in the original language...

We have plans to improve the way the target links are determined for missing links, as well as providing more options for selecting between the different options for the link labels. The linked tickets have more details on the proposed approaches, feel free to share any comments or ideas in this area.

> Additionally, would be nice to have {{Ill }} accessible from a single click as well

That makes sense and is relevant for the context of translation, but has some additional complexity we need to evaluate. Although the template is relatively common (available in 59 languages), we prioritize for the tool generic features that do not depend on a specific template that a given community may or may not have. For now the ability to add any template should cover, and based on the data and observations we can consider facilitating the addition of specific types of templates for common cases.

> I start to translate a heading and realize...

The "Initial translation" card allows to make the content empty, which should be equivalent to just delete it. When publishing the content, empty elements should be skipped. If that is not happening, let us know and we'll investigate further.

> Had a major issue in which {{Harvnp }}...

Good catch! I created a ticket to investigate this case. If the templates are connected in Wikidata it is strange that the equivalent one was not picked.

> Would be nice if common headings automatically translated...

Machine translation is available but not enabled for English. We are expanding machine translation support to more languages gradually. I captured your comment in this ticket requesting machine translation support for more languages.

> {{Commonscat }} didn't translate properly

The issue seems to be that ihe contents for the template were already converted into wikitext for the source article (when displayed in Content translation). I expect that this won't be the case once we support for the source document an inspectable mode that presents content closer to Visual Editor edit mode. I created this ticket to check the status of the issue then.

> would be useful when publishing if the tool's edit summary also wrote out the originating wiki

The edit summary includes a link to the specific version of the article used for the translation, which includes the wiki in the URL. Are you thinking on any particular use where that won't be sufficient?

> ideally, could include the associated {{Translated page }} template on the talk page

We considered supporting this as part of the publishing options. Given that these are community-specific practices where each community may use also a different template, additional efforts of supporting such configuration is needed. As I mentioned before, our priority right now is on general features, but in some future stage we can consider this kind of customization.

Thanks for all the feedback!

Pginer-WMF (talk) 11:36, 22 February 2019 (UTC)

Years on, Polish still not supported

Talk:Content translation/2016/07#h-Yandex_enabled_at_Polish_Wikipedia,_but_only_in_one_direction-2016-07-07T00:47:00.000Z

Seriously, could this be disabled for languages not supported? Every now and then I will try to show it to someone and of course it is not working. From my end user perspective, this is worse than alpha, it's a feature that simply doesn't work. (FYI, I most recently tried it for Pl:Alfons Zgrzebniok. Further, it laughable considering how good Google translate and such are these days that we still don't have this working. WMF fail. Piotrus (talk) 03:37, 20 February 2019 (UTC)

Well, I have the same Problem. But I must admit, I cheated the URL to start the translation. The next problem to be not supported does not appear to caused the WMF or the CXT. I also closed the browser and reentered the CXT, without success. Hans Haase (有问题吗) 08:19, 20 February 2019 (UTC)

@Piotrus, what do you mean when you say that Polish is not supported?

The feature works there, as it does in any other language, and more than 1800 pages were published in the Polish Wikipedia using it. It also has built-in support for Google Translate.

What exactly are you trying to do, and what doesn't work? Amir E. Aharoni {{🌎🌍🌏}} 09:51, 20 February 2019 (UTC)

@Amire80: Let me replicate my steps so you can see what is not working. I am using Chrome, logged in.

1) I go to https://pl.wikipedia.org/wiki/Alfons_Zgrzebniok

2) I click on English button in the bottom left, then blue translate button on the pop up

3) the editor loads, but there is a blue dot '1 warning' in the top right corner. Expanding it produces the explanation "Translation services not available for the selected languages. Why?"

Copying original content works and I can probably edit the text, but machine translation part does not work. So as far as functionality, this only provides a two-versions view on one screen.

PS. I noticed you said 'on Polish Wikipedia'. And yes, that seems to work, I can get the extention to provide machine translation from English to Polish. My point is it does not work the other way round. Piotrus (talk) 08:33, 21 February 2019 (UTC)

Yes, machine translation into English is not enabled yet from any language. Polish is not special in this regard. Machine translation into English may be enabled in the future. Amir E. Aharoni {{🌎🌍🌏}} 11:21, 21 February 2019 (UTC)

One would think it would be a priority... Piotrus (talk) 02:01, 26 February 2019 (UTC)

warnings.. warnings

can you just hide the (right) side sections? specially "issues" section cuse i got alot of warnings everytime when i try to edit manually 😏😏 Amghari (talk) 00:00, 22 February 2019 (UTC)

Translation inside the col-* templates do not get saved

I've been translating w:Hovhannes Tumanyan into Hebrew, and the bullet list of his works inside the col-begin, col2, col-end templates cannot be translated. (The translation isn't getting saved. Making changes outside those templates does get saved. Ijon (talk) 14:30, 22 February 2019 (UTC)

I am also having this problem. It seems that edited template is not being saved. When I reopen saved translation, the template will be re-translated (by machine translator). William Surya Permana (talk) 03:41, 27 February 2019 (UTC)

Ping @Aaharoni-WMF Ijon (talk) 09:51, 9 June 2019 (UTC)

Unfortunately, col- templates in the English Wikipedia work as "begin" and "end" templates, and for technical reasons processing them in Visual Editor, and hence in Content Translation, is pretty much impossible. They should be replaced by the English Wikipedia editors, probably by {{Columns-list}}. Sorry I cannot provide a better solution. Amir E. Aharoni {{🌎🌍🌏}} 16:42, 17 June 2019 (UTC)

Hebrew Wikipedia footnote templates mishandled

Hebrew Wikipedia uses templates to insert footnotes (because of directionality) and they are not converted into footnotes in Ukrainian. Could this be automated please? アンタナナ 13:17, 23 February 2019 (UTC)

アンタナナ 13:21, 23 February 2019 (UTC)

j'ai toujours poser cette questions Abdenour.abdelkader (talk) 13:27, 27 February 2019 (UTC)

This was "summarized" without an answers from the development team. Has this been resolved? Asaf (WMF) (talk) 15:20, 30 March 2019 (UTC)

English to Chinese translation - not making use of machine translation

Hi,

Working with two students at the University of Edinburgh on the Translation Studies MSc. Both are translating from English to Chinese Wikipedia.

Both were using Microsoft Edge as the browser.

One student was able to use the Google Translate machine translation support to good effect.

The other will not use any machine translation option - Yandex, Google Translate, Youdao - doesn't seem to matter which is selected the entire article is returned in the original English on the right hand side of the screen.

This seems to be another issue - normally you can translate paragraphs by paragraph. Working with the article, Garden of Earthly Delights, from English Wikipedia seems to only allow the ENTIRE article to be selected or deselected. And no matter what, the original English text appears on the right hand side of the Content Translation window. Tried with Chrome and Firefox and same thing occurs.

Very strange to have two students working in exact same way - and one is prevented from using the machine translation option.

Any ideas or help would be gratefully received.

Many thanks, Ewan Stinglehammer (talk) 16:14, 25 February 2019 (UTC)

Can't edit

When I click translate for part of text that is in <blockquote></blockquote> it gets automatically translated but I can't edit that translation. Karakondzula (talk) 16:20, 25 February 2019 (UTC)

NBSP; Tag misinterpreted

The & nbsp ;-Tag is ignored or replaced by a beetle-character. Replacing the these characters disrupt the translation, making some existing characters temporary invisible. Hans Haase (有问题吗) 17:41, 25 February 2019 (UTC)

article link duplicated text

The wikilink points to same article if the first letter is in upcase of lowcase. However, the CXT duplicates the article and its alternative text for only difference the upcase and lowcase of the identical article name. Hans Haase (有问题吗) 18:53, 25 February 2019 (UTC)

Since four years references are cut by the first dot character

German references use dots in dates and behind headlines. The CXT still cuts after the first dot character, enforcing the user to fix it later. It cant be that difficult to ignore the dot and copy the reference including the closing /ref-tag.

I really get rid of this ground hog day game. The WMF owns several million of funds and cant order to fix this over years. Hans Haase (有问题吗) 03:23, 26 February 2019 (UTC)

Notification of new content/translations

I got a notification (from here or some unknown bot) that there were new translations (based on new content?) for 3 articles. I've seen 2 of those articles before, but had not contributed to them. I couldn't see the 3rd article because it was deleted on English Wikipedia. Please don't send me those notifications for article I didn't edit! ~ Smallbones (talk) 04:30, 28 February 2019 (UTC)

Which articles were these? I don't think that this comes from Content Translation, but it's possible that I am misunderstanding something. Amir E. Aharoni {{🌎🌍🌏}} 08:16, 28 February 2019 (UTC)

The notification came from https://en.wikipedia.org/wiki/Special:ContentTranslation

After I looked at the articles, the article names disappeared from the notification. I remember looking at some translations to see whether they were better than google translations, but not using them for an article in English, and 2 of the articles mentioned in the notice did seem to be somewhat familiar. Smallbones (talk) 15:09, 28 February 2019 (UTC)

OK, I'm starting to get a handle on where these came from: There is an article Tiina Elovaara mentioned in the notice as well as Educando a Nina and Affaire Empain

Others below that in the notice were Affaire du talc Morhange and Радиационная авария в бухте Чажма and I remember getting a translation (and not using it) for the 1st one. The 2nd is a topic I might be interested in, but don't remember having translated.

The bot seems to assume that if I translated an article for my own use, or to see if I wanted to write the English article then I'd be interested in seeing a new translation - [[it ain't necessarily so]]

Smallbones (talk) 15:21, 28 February 2019 (UTC)