# Talk:Content translation

We suggest checking the Frequently Asked Questions page first.

When reporting a bug, 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.

## It stopped saving the page

5

Hi. I don't have much time for doing translation, so I do it paragraph-wise. I've been translating a couple of paragraphs of an article just now, but it stopped automatically saving the page (20 min since the last save now). As far as I remember, there should be some shortcut to save the page manually, but I cannot recall what it was. And I cannot find any info about it. Is there any?

Do you see any error in browser console? Also, provide language pair and article name so, we can debug the issue also. Thanks!

After I wrote this post, it said that it had saved the translation. But now I opened it and it appears I'll have to translate the small paragraph for the third time already, and a bigger one for the second time. Still it doesn't save automatically.

The article is en:Swatting, en > uk, no machine translation being used. The browser console shows this error:

```Uncaught TypeError: load.php?debug=false…&version=19lyfvl:52 \$(...).wikiEditor is not a function ```

```    at HTMLDocument.<anonymous> (index.php?title=Кори…xt/javascript:12193)

Are you using any user Javascript related to wikiEditor/Editor?

No, afaik. I've been using a script for translation of some US towns' articles. I tried to remove it, but it seems that's not the case. That saving feature used to work like a charm until yesterday. Idk what could cause this. I have almost all the article translated, so I can simply publish the translation and finish it in the regular mode, but would appreciate if this issue got fixed.

There is a message above the article that says that the article in enwiki had been changed. It might be relevant in some way.

Reply to "It stopped saving the page"

## It does not translates text inside columns

5

It does not translates text inside columns

No, it shows interwiki for it

If you use the GoogleTrans gadget translation feature you can select the table and then press CTRL-ALT and then all the nodes in the table will be translated. This is very good, for instance, for track and field results, since the city and then the event will be correctly translated. For many tables, which have uncomplicated, repetitive text within them, machine translation is very good.

Reply to "It does not translates text inside columns"

## Traduction of notes and references

2

Hi,

When translating a page from a foreign language, the references and notes are lost after publication towards the translated language.

Given that the sources, references and notes from the original article are the same that in the translated article, it is necesarry to help in the traduction of the references.

I cannot see a solution rather than editing the sources and refs one by one in the source code of the page.

For any persons encountering a similar problem when wishing to translate notes and refs from a page in other language, I would be happy to hear how they do it.

Thanks

Yes this is a big issue and one I hope will be fixed soon.

2

Não devemos traduzir nomes próprios em artigos.

Thanks for the feedback @OliveiraM.autora, and sorry for replying in English.

It seems that you refer to an issue on the way machine translation works for proper nouns, where these may get translated when they should not. Currently Content Translation uses the translations as they are provided by the external translation services. Content Translation has no direct control on the initial translations provided, but it may be possible that some of those services provide a way to propose corrections directly to them.

Content Translation currently exposes the corrections that users make to the initial translations though our APIs, which can help external translation services to improve their systems in the long term. In addition, we plan to support user corrections to avoid cases where users have to repeat the same correction again and again, which should help in many cases.

## The cursor bug

2

After some time working on translating Eng to Georgian the cursor for some reason selects a letter and i can't undo it. When there's a typo i have to correct, instead of going into middle of the word, the cursor selects one of the letters and when i type it makes me re-write the whole sentence (or paragraph)(i hope this makes sense). I know that its not a laptop/windows problem because i've had this difficulty on multiple devices. It's almost impossible to work with it, takes so much time. How can i fix it?

Thanks!

Thanks for the feedback, @Lemon134340.

Content Translation uses the default editing surface that browsers provide which has many limitations when dealing with complex content and wikitext. Currently the Language team is working on a new version of Content Translation which provides a more solid editing surface.

The new version is still in development, but it is expected to solve these kind of issues. In the above link you can find instructions on how to try the new version. Feel free to test the new version and report if the issue with the cursor position is still present there. This feedback would be very helpful for us.

Thanks!

## Support for translations into non-Mandarin Chinese languages

2

Currently the translation tool does not support the non-Mandarin Chinese languages (NMCL) such as Cantonese and Wu. Because these languages share some similarities with Mandarin Chinese, it would save quite some hassle if the tool can translate it into Mandarin instead of copying the original text. So, I have a suggestion. Is it possible to make the tool translate, say English articles, into Mandarin Chinese, when there is still no support for (NMCL)? Like to change some kind of default settings you might have, so that the tool treats translation of all the languages (except the Chinese family ones) into NMCL as translation into Mandarin?

Thanks for the feedback, @Roy17.

Regarding machine translation support we normally expose the languages that each service provides, but it makes sense to expose similar languages when there is not an alternative. We did a similar customization to use English translations for Simple English Wikipedia.

The proposal for non-Mandarin Chinese languages makes sense, and I created a ticket to capture and discuss the idea further. I'm not familiar with the connections among the Chinese languages and variants, so feel free to add further details or correct any imprecision I may have made.

Thanks!

Reply to "Support for translations into non-Mandarin Chinese languages"

## ⧼cx-error-page-not-found⧽

3
Summary by Etonkovidova

I was on the Japanese wikipedia article ja:星に願いを。 and clicked the grey button on the left sidebar, to translate the article into Cantonese. The content translation tool displayed ⧼cx-error-page-not-found⧽ on top and could not load any Japanese contents, hence failing to translate.

An unrelated query. I asked a few days ago but received no attention, about defaulting non-Mandarin Chinese languages to Mandarin in the content translation tool before they are supported. Please see Topic:Ufql499r14wh9xre .

Thanks!

I just tried translating that article to Chinese or English, and CT also displayed ⧼cx-error-page-not-found⧽.

Thanks for the feedback, @Roy17.

I checked that the article ja:星に願いを。 is not loading in Content Translation. Currently the Language team is working on a new version of the tool that improves several aspects, including the process of loading article content. I tried the new version and the article loads.

The previous link includes instructions on how to access the new version. You can try to translate the article using this link to the new version.

The new version is still in development, but can be used already to translate articles. We are prioritizing the work on the new version in order to replace the current one as soon as possible. Please, share any issues you find with the new version.

Thanks!

## Feedback on version 2

6

The infobox does not add which is not a big deal. ES does not have that infobox. The first two paragraphs add but not the subsequent two paragraphs.

Further bad news. It totally messes up the references in the two paragraphs it does bring over. For a single reference it gives "[1]"

1. Hubbard, MJ; Hildebrand, BA; Battafarano, MM; Battafarano, DF (junio 2018). "Tejido Blando común Desórdenes de Dolor Musculoesquelético". "Common Soft Tissue Musculoskeletal Pain Disorders." (June 2018). Primary care 45 (2): 289-303. doi:10.1016/j.pop.2018.02.006. PMID 29759125.  "Common Soft Tissue Musculoskeletal Pain Disorders." (June 2018). Primary care 45 (2): 289-303. doi:10.1016/j.pop.2018.02.006. PMID 29759125.  (2): 289@–303. doi:10.1016/j.Pop.2018.02.006. "Common Soft Tissue Musculoskeletal Pain Disorders." (June 2018). Primary care 45 (2): 289-303. doi:10.1016/j.pop.2018.02.006. PMID 29759125.   "Common Soft Tissue Musculoskeletal Pain Disorders." (June 2018). Primary care 45 (2): 289-303. doi:10.1016/j.pop.2018.02.006. PMID 29759125.

Thanks for the detailed feedback, @Doc James. Some comments below:

Regarding the infobox, it is possible that some templates are not available in the target language. One aspect we plan to work on is to better communicate what happened to the user.

Regarding the translation paragraphs not being added it is a known issue that is related to references shared across different paragraphs. This is caused by a problem in the Visual Editor libraries that took some time to investigate, and we are looking forward to get solved since it has a big impact for Content Translation.

The issue with references being messed up where the content appears repeated several times, may be also related to the previous issue, but to be sure I created a specific ticket to verify it. Please, feel free to add further details there if anything is missing.

Thanks @Pginer-WMF. Can you let me know when the reference issue is fixed. Waiting on this before pushing forwards the medical translation efforts.

Since the fix depends on a different team I don't have a clear estimate yet, but I added a comment to get more information about it. Considering the review and deployment cycles, and the proximity of Wikimania, I'm afraid the fix may still take more than two weeks.

Reply to "Feedback on version 2"

## Copy paste of maths

2

Hi, it seems that if I cut/paste a math formula inside a paragraph translation, the paste is downgraded into raw tex code.

I I copy something that looks like ${\displaystyle X_{m}}$ , the paste looks like X_m

Thanks for the feedback, @TomT0m.

Content Translation uses the default editing surface that browsers provide which has many limitations when dealing with complex content and wikitext. As a result only plain text pasting was allowed, which is very limiting when moving content around by copy and pasting it.

Currently the Language team is working on a new version of Content Translation which provides a more solid editing surface (with reliable support for copy&paste, undo/redo and more). The new version is still in development, but it is expected to solve these issues. In the above link you can find instructions on how to try the new version. Feel free to test the new version and report any issue you find, which is always very helpful for us.

Thanks!

Reply to "Copy paste of maths"

## Translation not working

2

I'm translating articles from Spanish to German, but the automatic translation doesn't work, so it takes a lot longer for me. Anyone else with that problem? Or is it just some kind of setting that you can turn off? The weird thing is that I've already translated an article (but from German to Spanish) and it worked.

Thanks for the feedback, @Horchatamivida.

Machine translation services are not always enabled for all the language pairs. Due to concerns with machine translation quality and the potential misuse of the tool, automatic translation was not enabled when translating into English or German.

We believe that it is possible for Content Translation to support and encourage good use of machine translation in all languages. As part of the work on the new version of Content Translation, we plan to improve the way the tool deals with excessive unmodified machine translation, by showing warnings at a paragraph level, mark those articles that are published despite the warning for editors to review, and prevent publishing when the percentage of unmodified machine translation is too high.

We expect these improvements, the associated measurement of article survival, and the users who share their experiences with the tool to help in the process of expanding the good use of machine translation. I captured your comment in a related ticket about machine translation requests. Feel free to add any other comments, and keep sharing your experience with the tool.

Thanks!