Talk:Content translation/V2

Jump to navigation Jump to search

About this board

This is feedback page about the next version of Content translation tool.

Also, 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. When reporting issue, please add CX2 in topic.

See also:

Prenvented publishing because of "unmodified machine-translated text"

McYata (talkcontribs)

When I tried to publish new translated article, the tool said "Your translation cannot be published because it contains too much unmodified machine-translated text". However it can't be, because first of all I chose "Use source text" instead of using "Automatic translation", which is contained in Content translation tool. Therefore the sentences which I translated contains 0% machine-translation.

Every time I translate article get warning about "unmodified machine-translated", and I have avoided it by choosing "Mark as resolved". Now this is the first time I cant find any way to avoid it. What can I do?

Pginer-WMF (talkcontribs)

Thanks for the feedback, @McYata.

This issue has been fixed in the code recently, and the fix will be available to users during the next weeks. You can read more details in this ticket. If the error persists after a couple weeks, please let us know and we'll investigate the issue further.

McYata (talkcontribs)

I waited a few days and tried again. I could publish the article and haven't seen the same error until now. Thanks!

McYata (talkcontribs)

Well, I got the same error again...the first article the error emerged was "Gunpowder Empires", and this time "Serica". It might happen when I try to translate some articles which contains <blockquote>, which can't be rewritten in Contents Translation at present. (though I haven't confirmed it at all.)

McYata (talkcontribs)

Sometimes a different error appears, which says "detected spam contents. See "". " (I don't know the real original English message. Japanese message is 「あなたの翻訳にスパムの可能性のあるコンテンツを検出しました。詳細」.) What is How can I deal with it?

Reply to "Prenvented publishing because of "unmodified machine-translated text""
Aeroid (talkcontribs)

I was eager to see if the new machine translation services provide more support for German (e.g. to or from English). But I still get "Translation services not available for the selcted languages" (de->en). Should I be patient, or is there any config, tweak, cached pages that I overlook? (URL ends on "&version=2")

Pginer-WMF (talkcontribs)

Thanks for the feedback, @Aeroid.

Machine translation support for English and German as target languages is not enabled yet. Support for new languages is expanded gradually, and I captured your comment in this ticket to keep track of the different requests in this area. Feedback from the community is very important to expand the support.

Meanwhile, an alternative could be to translate from German to Simple English, for which machine translation is available.


Reply to "Supported language pairs for MT"
Doc James (talkcontribs)
Reply to "Handling of templates"
NicoV (talkcontribs)

I see you have put V2 in production in frwiki for about a week. I checked the last 5 translations done with the new version, and not one is free of problems... I've reported the problems in Phabricator : T213255, T213256, T213257, T213258, T213259.

I checked a few more edits: T213262, T213273, T213275, T213276, T213277.

Has it been really tested before being put in production?

Pginer-WMF (talkcontribs)

Thanks for the reports, @NicoV.

Version 2 is an opt-in feature that is available for Content translation users. We are making version 2 more visible for existing Content Translation users as it gets improved in order for them to transition from version 1 to version 2.

Version 2 uses the Visual Editor editing surface which provides a more solid experience editing wikitext compared to version 1. Version 2 is still in active development, and we have processes to test, get feedback and improve.

Given the diversity of the content, the number of languages supported and the many templates that exists on each wiki (that were not designed to be transferred across languages), it is not feasible to anticipate all the problematic combinations, and we appreciate the reports to identify such issues.

I know that similar issues about the quality of the wikitext produced were reported in the past for version 1. Those were hard to fix in version 1 without making a big architectural change. Version 2 represents such change, many of those have been already fixed, and it is in a better position to get more fixed.

NicoV (talkcontribs)

@Pginer-WMF I do understand this should be an opt-in feature, but as it is still beta (and still generating a lot of problems in the results), why do you advertise it so much? For example, I've disabled CX in my preferences (beta tab), but I still get popups messages to use it whenever I end up on a page that was deleted because it's not admissible... Why don't you only give notifications to users that have explicitly requested to receive them, rather than forcing them on users who requested not to have them?

Also, why don't you give more prominent message to explain that CX and CX2 is "beta" software and that users opting in should check the result of their translation, especially if they create translations in the main namespace?

CX has been creating buggy articles in production for 3 or 4 years now, and it keeps doing so: when will something really be done about this?

NicoV (talkcontribs)

And when you say "it is not feasible to anticipate all the problematic combinations": I would agree if the problems were on a small number of edits, but they appear on a vast majority of articles. For example, I just checked 1 translation, and I reported T213419...

Reply to "In production, but many problems"
Palosirkka (talkcontribs)
Hans Haase (talkcontribs)
Amire80 (talkcontribs)

The creators of the source article are credited in a link to the revision of the source article from which the translation was made, which is added automatically to the edit summary of the published version. This is compatible with the CC BY-SA license and with Wikimedia's Terms of Use, which require you as the re-user to give attribution "through hyperlink [...] to the page or pages that you are re-using".

Reply to "Attribution required"
أبو هشام السوعان (talkcontribs)

Thank you now I can publish the translation on the personal domain pages in this version, and I have one note is the references template at the end of the translation. Thanks again.

Reply to "Thanks for the development"

Пераклад на беларускую (тарашкевіца)

Renessaince (talkcontribs)

…does not work at all. The only error it returns after clicking any parapgraph to translate is «Automatic translation failed!» I tried to translate «Трыстан-да-Куньня» from be-wiki.

Hans Haase (talkcontribs)

See other topics of this talk, how to install the Translator script, and You will be lucky.

Renessaince (talkcontribs)

Searching talk page doesn't return any result about «Translator script», can You be more specific?

Hans Haase (talkcontribs)
Renessaince (talkcontribs)

I have not vector but modern skin installed. Should I try to do instructions provided into modern.js file? Or CT2 doesn't working on it and I shouldn't even try it?

Hans Haase (talkcontribs)

The potential risks are described there. You first may try to copy and paste Google Translator, with some text from the article to see what You will get.

Reply to "Пераклад на беларускую (тарашкевіца)"

Section titles trigger "article is too small" filter

Ата (talkcontribs)

Even with all paragraphs fully translated I see ukwiki abuse filter notification next to the section titles. (It doesn't prevent page creation.)

Amire80 (talkcontribs)


Thanks for the report.

I have passed it on to the developers, however I see at least one issue with the filter itself. Its code says (article_articleid == 0), and according to the AbuseFilter user manual, article_articleid is deprecated. Can anyone who maintains AbuseFilter in the Ukrainian Wikipedia check this? This may have to be updated.

Tagging this filter's maintainers: @Sergento, @Dim Grits, @Yakudza, @NickK, @Ilya.


Amire80 (talkcontribs)

I just received a very similar complaint about the Russian Wikipedia from @Раммон. The filter definition in the Russian Wikipedia also uses (article_articleid == 0). Even though I'm not sure that this is the thing that causes the problem, it should be corrected. @Q-bit array, @OneLittleMouse, can you please take a look?

In any case, I'm passing this on to Content Translation developers.

Раммон (talkcontribs)

This problem raised again. Please, resolve it.

Reply to "Section titles trigger "article is too small" filter"
NicoV (talkcontribs)

Could you add an easily visible link to report bugs in Phabricator in the page describing V2 ? It seems that V2 has been activated on some wikis (like frwiki), but the link on the tag brings to this page, without an obvious mean to report the problems in Phabricator.

Amire80 (talkcontribs)

In fact, it's activated in all languages in an opt-in mode. Every user who enabled the beta feature can enable and disable CX2 from the dashboard using the link "Try the new version". However, we do gradually ping some of the larger wikis and ask for detailed comments.

We read both this page (Talk:Content translation/V2) and the usual talk page (Talk:Content translation) every day, and both pages are acceptable places for bug reports.

If you want to report a bug in Phabricator, you can use the same tag, #ContentTranslation. You can add "CX2" to the title to emphasize that the task is about the new version.

NicoV (talkcontribs)
Amire80 (talkcontribs)

Oh, I see what you mean. Good idea. I'll pass it on.

Pginer-WMF (talkcontribs)

Thanks for the feedback @NicoV.

We want to keep this page as the main feedback entry point to support a wider audience, supporting users that can share their experience but are not familiar with Phabricator and bug reporting. Having said that, I agree that we can make it easier for those users that are familiar with Phabricator. I added the link for ticket creation to Phabricator in the information sidebar of this page. It is also present in the "Provide feedback" section of the page.

Reply to "Report bugs ?"

Překlad citačních šablon do češtiny (Czech)

1 (talkcontribs)

Překládal jsem Haarova míra do češtiny z angličtiny a asi nejhorší bylo, že se nepřeloží citační šablony. A anglické nefungují. Buď by se měly ty anglické zprovoznit i na české wiki, nebo by je nástroj měl správně překládat. Jan Spousta

Reply to "Překlad citačních šablon do češtiny (Czech)"