Google does excellent translations between these two languages.
Help talk:Content translation/Translating/Initial machine translation
Jump to navigation Jump to search
Reply to "Why is it not possible to translate English to German?"
Reply to "simpleWiki is in the yandex list. i machine translate."
Reply to "Why can't I automatically translate anything to English?"
Reply to "translate from Arabic to english"
Reply to "update"
Why is it not possible to translate English to German?
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,
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;
- no infobox;
- multiple images before the "top section";
- 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
:* Special features of ultra-low U-value glazed buildings;
:* Multipane glazing engineering;
- See also;
- 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:
"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.
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,
Yes, I thought that might be a problem. Thanks for looking into it. :-)
simpleWiki is in the yandex list. i machine translate.
why cant i do it?
Why can't I automatically translate anything to English?
I have reported this problem 5 months ago at Topic:Vi3tnoorf1w5ijd9, and it still has not been fixed.
translate from Arabic to english
I can't translate articles from Arabic to English ? Why? who I can do it ?
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.
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.
There are no older topics