Talk:Content translation/V2

I'm a bit surprised that the Template:Translated page (Q5615431) isn't yet appended when articles are published. Wikipedia's content is CC-BY-SA, meaning the attributions on the article that's being translated should be referenced as well.

Agree would be nice. One does get attribution in the first edit that creates the translation in question. We have had 750 medical translations as part of our relaunch. Will need to look at adding this. Would be nice if it would take mdwiki.org as a "language" Doc James (talk) 14:39, 28 July 2022 (UTC)

The edit summary is the credit reference. It's in the FAQ: Content translation/FAQ#How are the writers of the source article credited?

It's a sidetrack input here. If we could automatically add tl:translated_article on its talk page, then IMHO we could prevent lengthy dispute over the reliability of any article whenever I see one on jawp. It's not the quality of the original article picked inter-language. A heated debate is almost to conclude that jawp request ban on CX2 output to jawp.

• I sense a type of allergy editors react on jawp, as they get irritated more than often when they find very low quality output of "machine translation";
• Its not blamable on CX2, but on ethics of users applying CX2 but publish without due editing/naturalize expressions or links, and inspecting ref tags/templates working as expected;
• we encourage new-to-editing users applying CX2 and start editorship, but there is no place on jawp where you will be guided to Dashboard or newbies' mentors (do we have CX2 Dashboard anyway?);
• Putting a template on its talkpage earmarks a page produced via CX2, and one way to rescue both translation watchers/menders and the reputation of CX2. We could verify the ratio of pages via CX2 and well translated against low quantity output, so that it will be easier to see CX2 is not a tool for justified "vandalism/test editing". Is it a wrong way to use that template or an educational effect it would promote CX2 on jawp or other communities skeptical of using CX2? Cheers,

First, vandalism is never justified, certainly not by CX.

Applying a template is complicated, because every Wikipedia has different templates. CX does apply a tag in all languages, which is easy to find in recent changes: click "タグ" and then select "コンテンツ翻訳". Does that help?

@Amire80, Hi, yes, CX does apply a tag, and I am a fan to use it finding new CX output; a watch group utilizes the tag and screening the quality of new pagenamespace entries.

Then, could we add that workflow to the how-to documentation, don't you think? For ex in the case of jawp,

• 翻訳拡張機能を使って作成された記事を探すには、recent changes: click "タグ" and then select "コンテンツ翻訳".

I wish to make it clear to anybody, who submits multiple pages in low quality or deceives the aims of CX2 by not doing due endeavour to reach natural/localized writing, then they can be screened > warned > suspended. To do that , we'd need written rules or regulation or advice on Meta, and mirror/link i I hate to see the irritation among translation proofreaders that they are so inclined to ban the output from CX2: it's moral issue, not to blame on extensions, IMO.t on jawp.

Maybe the subject I suggest does not fit to the scope of this page? A Wishlist Survey subject for 2023? (; Cheers,

Thanks a lot for this attitude. It makes a lot of sense.

Warnings about machine translation already appear several times in the user interface of CX itself, in the FAQ, and in the user manual. If you have any ideas about making it even more prominent and, more importantly, more efficient, the designers would love to hear it.

The threshold for acceptable machine translation in Japanese can be adjusted, too. It was already done in several languages, and as far as I know, it works well. If you think that Japanese is somehow special in this regard, please let me know.

@Amire80 Thank you for the thorough insight, I appreciate very much. Actually I was lost how the fume among jawp ppl would be channeled into positive steps.

> The threshold for acceptable machine translation in Japanese

Right, I was hoping to talk about that when ppl will get a bit calmer and find some space to discuss the issue further. I'd talk about it with the volunteer compiling use cases on jawp, and with data, I guess the discussion Mediawiki be much productive. You know, coming to Mediawiki is a higher wall compared to Meta... Cheers,

Hello, I am from Vietnamese Wikipedia (viwiki). I am not sure where I can give my concerns to this tool. The tool can not prevented the overused or abused actions of editors in some cases.

When you translate a short article, '''this tool allows editors to publish the low-quality content regardless they have no efforts to translate''', only use automatically translated content from Google Translation. That is such a '''nightmare''' for small-and-medium projects where there are not enough administrators to patrol new content. In viwiki, we have thousands of articles like this, and the community can not follow and correct the writing style. I demand a method to prevent this.

I suggest 2 main things:

1. An option that prevent editors to publish the content if it has only a single problem or a threshold of the number of problems.
2. A configuration where local admins can set the usage right to certain users or user groups.

Thank you!

Alphama (talk) 22:43, 7 September 2020 (UTC)

What is the source for the suggestions page in the tool?

I believe they are coming from the various Content translation/Machine Translation engines, depending upon which language pair someone is going between.

Yes. But, is there any particular page which displays the list of articles that are displayed in the suggestions page?

Oh! Sorry, I misunderstood the question. For that, see Content translation/Documentation/FAQ#What are the "Suggestions" in the dashboard?

The problem has not been resolved yet.

Sick of all the endless bugs. Here I go again translate something manually because for some completely unknown reason, the tool decided not to automatically translate again. Thanks for nothing.

And the Wikidata links still aren't being created automatically, and the new articles in the portuguese wikipedia are still going to be alone, disconnected from the others.

When not possible getting an automatic translation, just mark a smaller section and retry. This is a work around, I often use, most times with success. Sorry for the inconvenience.

Automatic translation is not available for all languages, and machine translation may also be turned off by default for some languages. I believe you must also be a contributor at the target language, not sure if this is turned on or not.

I review new pages in the portuguese Wikipedia, and I always have to link articles manually. Just letting you all know.

That should not be necessary. The CXT also supports autotranslation. Check if installing Endo999's script is still required. Mark the text section and to hold down CTRL and ALT key to translate the marked text inside the CXT. See Topic:Udmnnnrjpzq5dbe0 or how to install in Topic:Uj61e2fkvlf5qy5o and Topic:Uas7z3lf379cp60t. if it is still not functional, have us know.

@Hans Haase, the complaint is about something different.

@Bageense, I also heard from other people. We'll look into it.

@Hans, I'm just an average editor, I don't have the capacity to do all of that you suggested. Thanks, Amire.

I've just translated an article myself using the tool and again, it wasn't automatically linked to the articles in other languages through Wikidata. That confirms my complaint is true

I've translated an article from portuguese to english., Same thing. en:Feminism in Brazil

I want to inform a problem here again because almost same issue has appeared. I translated w:en:Adelaide of Susa with V2. However, many of refs disappeared and I had to refill them.

We had the problem occur when the meta data for the ref occurred within a template or infobox. I had a tool build for EN WP that moves the reference metadata out of the infobox to solve that part of the issue. Does not look like it played a roll in your current problem though.

When I tapped a section under offline state, it failed and a caution like above popped out (I don't use automatic translation at all as I've said in Prenvented publishing because of "unmodified machine-translated text", but it's not the matter this time.) The problem is, even after I came online, the section which said "Automatic translation failed" can't be edited anymore. Just saying the same caution. Is it possible to complete the translation in such situations?

This article at en.wiki was apparently created using this tool. If you look at the wikisource for that article you will see that all of the en:Help:Citation Style 1 templates are not stored as templates but are stores as raw html. This is wrong. There is a similar problem described at phab:T209493 though that phab task is about copy/pasting named references using the abomination that is ve, but since the symptoms are similar, perhaps if the translation tools share ve code...

FYI here is a link to the details of the page creation (and to note, the 'creation' was actually as a userspace draft, that was later moved to the article):

w:en:Special:AbuseFilter/examine/1138531679

For CX2, I worked on a page with prefix Wikipedia: on enwiki. When I tried to name the ja page title as starting with Wikipedia:, the CX2 does not accept so that I ended up naming it The_Wikipedia_Library/OABOT. It has been moved by a user anyway to Wikipedia:OABOT.

How can I name the translated page with "Wikipedia:" prefix when using CX2? Or, can you think of adding a button so that published translation is filtered as it needs to be moved/renamed? Or, I am concerned that we owe local community editors think as me repeating same unwise action, as page names are something each community is very specific about I guess.

When you tried to create the page w:ja:Wikipedia:OABOT did it not create? It appears at https://ja.wikipedia.org/w/index.php?title=Wikipedia:OABOT&action=history and doesn't seem to have been moved? When (date/time) were you trying to do these tasks?

No, my original publication of CX2 output was not named w:ja:Wikipedia:OABOT since the system rejected the title; so I named ":w:ja:The Wikipedia Libray/OABOT" instead. Then later a user moved it to the expected namespace, hence it is now at  :w:ja:Wikipedia:OABOT.

I'm not able to duplicate this. I was just able to create a page on jawiki from content translation:

2019-03-10T21:21:05 Xaosflux (talk | contribs) moved page Wikipedia:Sandbox3 to 利用者:Xaosflux/Sandbox3 (Test) (revert)

2019-03-10T21:20:17 Xaosflux (talk | contribs) created page Wikipedia:Sandbox3 (ページ「Indian River State College」の翻訳により作成)  Tags: ContentTranslation, ContentTranslation2

Would you try CX2 with a Wikipedia: prefix page please?

I created it as "Wikipedia:Sandbox3" already, not sure what else to look at?

I mean, did you use CX2 and put some Wikipedia:xxx page as the translation source, on your left pane? Then start translation actually? Unfortunately, reating a blank page on jawiki is out of the focus on my query. If you had done with "Wikipedia:Sandbox3", my appology. How do you translate a Sandbox ?

I started with a normal article from enwiki, and translated it TO a Wikipedia: page on enwiki. I was unable to translate FROM pages other than articles. I had no problem at all creating the destination page via the CX tool in the Wikipedia: namespace.

Please look at the left of "公開する"(publish), you'll see a gear button. By pressing this, You can create sandbox page for you. So just make the translated article in your sandbox, create "Wikipedia: -" besides Contents translation, then copy the translated source and paste it to new page. In this case, don't forget history inheritance (履歴継承).

Case closed for me, and very thankful for your inputs; I wish your instruction will be seen by those not-so-techy translators like me. Backlist might hopefully get shorter faster, and new editors will be supplied with time tested wisdom Wikipedians had spent time to mediate “what to does”. Domo arigatow gozaimasu.