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.
Topic on Talk:Content translation/V2
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,