Help talk:Content translation/Translating/Initial machine translation

Recently, Google announced that the contribution feature was turned off.

ref. What’s new in Google Translate: Changes to Contribute - Google Translate Help - https://support.google.com/translate/answer/14754103?sjid=4013565532041901992-AP

It'd be nice that the description about the contribution for Google Translate is updated. It seems that they still accept the bug reports other than the contribution about the translated text.

Thank youǃ

@TAKAHASHI Shuuji, appreciate flagging, and can you give the link to where in Wikimedia side you find update-needed please? Or it sounds as if you are suggesting non-Wikimedia update (~_~)?

Followed the first link I found in the message about deploying whatever tool you crazies have in mind by default "if there are no objections" by March 4.

You're creating a disaster: There will be no feedback on most smaller wikis, and after that, all sorts of well-meaning morons will go ahead and dump junk and gibberish onto the pages without anyone even recognizing that it is junk.

This should only be deployed after an active "yes, please" and not after crickets. Ah well... I warned you. Seb az86556 (talk) 06:13, 15 February 2024 (UTC)

Google does excellent translations between these two languages.

Hi, can’t you provide the article link that humpered you to output en-de translation to dewiki? That way, your query be better answered I suppose. Cheers,

https://en.wikipedia.org/wiki/Quadruple_glazing

Hi, Alek14, I test-translated en-ja for the same enwiki article, but limited sections into my sandbox: I imagined three points which could possibly cause to reject CX2 output in dewiki. No past experience on en-de CX2 output, though, only based on my personal hunch working with CX2 with 200+ output pages;

1. no infobox;
2. multiple images before the "top section";
3. could be any footnote problem caused by citation template mismatch.

Thus, I translated only the top section, with References and External links only. The outcome was fine, that en-ja CX2 output for w:en:Quadruple_glazing was successful.

• In stead of applying four images at page top, I grouped them per two images;
• I did not finish translating all sections, but

• top;

:* Special features of ultra-low U-value glazed buildings; :* Multipane glazing engineering;

• See also;
• References;
• External links.

Not sure if your problem links with my test case, and I would need to finish those two longer sections which I have skipped this time. Cheers,

Hi, Omotecho-san :-)

The problem is EN to DE (German) language initial-translation is disabled. Problem goes here:

https://phabricator.wikimedia.org/diffusion/GCXS/browse/master/config/Google.yaml

Here says;

https://phabricator.wikimedia.org/rGCXSe1205ec092dd1273a3c4e24fa94fb2d0de8a87c4

  - de

  - en

  - it

"notAsTarget" cannot be selected as target language. Which makes EN/DE initial translation inaccessible from the menu.

It is not a translation problem pre-se, rather function inaccessibility.

Regards,

Ahh, I see ! So that means dewiki does not approve CX2 output as their article. Too bad... but I suspect that jawiki community has also escalating the negative evaluation against CX2 output as articles, not because it malfunctions, but rather human factor and the threshold of how far an editor will edit raw CX2 output before saving it as on page namespace. I will continue and use CX2 to prove how it will help us share human knowledge which is the best idea I resonate with wiki projects. Wish you keep your spirit up q(^o^)p ! Cheers,

Hi @Omotecho do you know who decided to not accept CX2 output / machine translation for dewiki? I can not find any discussion. regards --Cepheiden (talk) 22:30, 13 August 2022 (UTC)

Cepheiden, hello, please read through this thread over 700 days ago, as we were talking about https://www.mediawiki.org/w/index.php?title=Topic:W1frvwcuknf0duqn&topic_showPostId=w1gdsh54w63cy3a4#flow-post-w1gdsh54w63cy3a4. If you know dewiki better than me, I wish you always point me to links, not thoughts. Cheers,

@Omotecho Hi, thank you for pointing this out again. The link refers to a specific change. However, my question was not about the technical reason, but about why CX2 support is blocked. It looks like someone or some group wants to actively prevent. The question is why and how to reach these people. I assume you don't no either. regards --Cepheiden (talk) 20:59, 18 August 2022 (UTC)

No biting, @Cepheiden, and I wish to point you to read Phabricator as I did down this thread: when you need actual resolution, it's my habit to try and find who can help me solve issues which means "technically" on wikis.

Talking about the link to previous report/discussion on CX2 and de, kindly roll down and see input by @Alex42.

I stand with you that sometimes it is a sad fact weeks/years(!) are invested to mend one-sided obstacle like the one you point out, because that involves philosophy or mindset. May CX2 be applicable to very active wikis...

Yes, I thought that might be a problem. Thanks for looking into it. :-)

Hello Omotecho, Alek14, Pginer-WMF.

The list in T86700 points out how much german (and english) users are craving for machine translation.

Has working on support for german stalled since Phabricator T228289 is set to lowest priority?

What work has to be done to integrate de?

hmmm, can't access the statistics ): response details at: T86700, <quote> Maniphest Unhandled Exception ("AphrontQueryException") > #1290: The MariaDB server is running with the --read-only option so it cannot execute this statement.<unquote>

@Alex42, any hint how I can read Maniphest statistics please? I failed to open the page per:

> >The list in T86700 points out how much german (and english) users are craving for machine translation.

> <quote> Maniphest Unhandled Exception ("AphrontQueryException") > #1290: The MariaDB server is running with the --read-only option so it cannot execute this statement.<unquote>

Hi User:Omotecho, i was talking about the quotes in T86700, i have no actual statistic.

This has worked before when translating articles or parts of articles from French to English, though when I tried this again last week, it is bringing over the original content still in French, even though I have it selected to go from French to English. I know the machine translation needs to be fixed in English, though it is often enough to help me get going. Can you please help me with this?

why cant i do it?

I have reported this problem 5 months ago at Topic:Vi3tnoorf1w5ijd9, and it still has not been fixed.

I can't translate articles from Arabic to English ? Why? who I can do it ?

This document does not reflect the January 2019 GOOGLE translation agreement between the Wikimedia Foundation and GOOGLE. --HaussmannSaintLazare (talk) 04:53, 21 April 2020 (UTC)

Hi @HaussmannSaintLazare,

Can you detail what is missing in the page from your perspective?

This is a user documentation page, and provides detail on which are the services integrated, the languages they support, how to improve their support and additional considerations. Specific details about Google can be found here.

This document does not reflect the January 2019 contract between GOOGLE and Wikimedia foundation about GOOGLE translate, but it is in line with its predecessor status. This page and its translated version are directly linked from each Wikipedia and are actually part of the manuals when users use content translation. So the current situation is inappropriate as a manual.

--HaussmannSaintLazare (talk) 06:19, 22 April 2020 (UTC)

I know that MediaWiki are used on sites other than the Wikimedia foundation. However, content translation is a function specialized for Wikimedia foundation sites such as wikipedia. This can be proved from the fact that the current text is supposed to be used on the Wikimedia foundation site.

--HaussmannSaintLazare (talk) 06:31, 22 April 2020 (UTC)