Talk:Content translation/V2

This is feedback page about the next version of Content translation tool.

Also, 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. When reporting issue, please add CX2 in topic.

See also:

• More details about Content translation Version 2
• Report an issue about Version 2 in Phabricator

translate

hi please add translate to other wikimedia projects example wiktionary wikibooks and many more Amirh123 (talk) 17:59, 20 May 2018 (UTC)

Thanks for the feedback, @Amirh123. Enabling the tool for other projects beyond Wikipedia is not in the immediate plans for version 2, but having a more solid editing surface as version 2 provides we'll be in a better position to support other projects better. We'll consider this for our future plans. Pginer-WMF (talk) 12:39, 30 May 2018 (UTC)

Feedback

I tried the new version of Content Translation, translating en:1936 Cansiglio earthquake > it:Terremoto del Cansiglio del 1936.

worked well: importing references (even if CT still doesn't recognize dates/months)

Didn’t work: impossibile to import the template:infobox_earthquake; if there is a note, I can't select the entire phrase (I can select only from the beginning to the note); wikidata was not upgraded with the new page translated Holapaco77 (talk) 12:18, 11 June 2018 (UTC)

Thanks for the positive feedback, @Holapaco77.

I filled several Phabricator tickets for the issues you mentioned about the infobox issues, text selection, and date adaptation on templates. Feel free to check these tickets for tracking their progress or adding details.

Regarding Wikidata updates, in some cases it takes some time until the interlanguage links are visible, but we'll investigate this particular case.

Thanks for using version 2 and providing useful feedback. Feel free to keep using the new version fo the tool to translate more articles. We plan to deliver improvements for the new version every week, and we always appreciate useful feedback. Pginer-WMF (talk) 12:45, 12 June 2018 (UTC)

Commento

Salve, mi è stato scritto in discussione cosa mi piace e cosa non mi piace del Content translation.

Quando le note devono essere convertite in lingua diversa per esempio inglese-italiano, in cui appare solo l'url. Quello che deve essere fatto è che oltre all'url ci sia anche il titolo. Cataldo01 (talk) 14:09, 11 June 2018 (UTC)

@Cataldo01 quello era il "vecchio" Content Translator. Adesso c'è la seconda versione "Content Translator/V2" e non c'è più il problema dele note (o almeno io l'ho provato ieri e il problema sembra essere risolto). Devi tradurre partendo da questo link: https://it.wikipedia.org/wiki/Special:ContentTranslation?version=2 Holapaco77 (talk) 07:31, 12 June 2018 (UTC)

Feedback

Hello!

I was invited to test the new version of the tool, and so I have tried it a little. I have been using it for almost three years now, and first of all I would like thank the developers: you all are great!

Editing templates seems easier now. But that's the only point where the new version is better than the older one. Unfortunately I can't quickly put the link to another wiki page by clicking the necessary word at the left side (maybe one should do it some other way, but I haven't figured out how). That slows down the process of translation considerably. There are also some minor flaws: headlines begin with a space and you have to edit interwiki links by yourself (but all that sometimes have happened before, and that's not of much inconvenience, but well, maybe I should mention it as well), some unnecessary categories are added: "Articles with hCards"?

Did w:en:Die Streuner -> w:ru:Die Streuner

Thank you for your work on the tool! Roman Puzin (talk) 17:41, 12 June 2018 (UTC)

Thanks for the useful feedback, @Roman Puzin.

Based on your comments I created a ticket to support adding links from the source articleas well as use the source paragraph as initial suggestions when adding a link, which can be convenient when using a keyboard shortcut (ctrl+k). I also added a note on the ticket about the extra space in headings. Feel free to track the progress of these tickets or add any further comments.

Regarding the addition of interlanguage links and avoiding irrelevant categories, those are supposed not to happen and we'll investigate them further to find the underlying issue.

Version 2 is in an early stage of development. It can be used to create articles right now but there are many aspects to polish since replacing the underlying editing surface requires to rewrite many of the tools. We are making improvements on the new version every week and we always appreciate useful feedback. So feel free to keep trying the new version after some time and keep reporting feedback.

Thanks! Pginer-WMF (talk) 10:18, 13 June 2018 (UTC)

Feedback

Bonsoir,

Je viens de tester l'outil en traduisant Clara of Brunswick-Wolfenbüttel en français. L'interface est visuellement plus agréable. J'ai l'impression que la traduction automatique est peu meilleure, même s'il reste des marges d'amélioration. Le seul vrai problème est que l'outil n'a pas créé automatiquement le lien entre l'article dans la wikipédia en français et l'élément wikidata. J'ai été obligé de le faire manuellement. La possibilité d'ajouter une autre catégorie est une évolution positive. Authueil (talk) 20:29, 12 June 2018 (UTC)

Thanks for the positive words about the tool, @Authueil.

I'm happy to hear that you appreciate the improvements on categories and the general design improvements. Regarding the Wikidata links not being added automatically, I added a note to the corresponding ticket to investigate further.

We are making improvements on the new version every week and we always appreciate useful feedback. So feel free to keep trying the new version after some time and keep reporting feedback.

Merci! Pginer-WMF (talk) 10:34, 13 June 2018 (UTC)

Feedback

Bonjour,

J'ai testé l'outil avec la traduction de l'anglais vers le français pour créer cet article https://fr.wikipedia.org/w/index.php?title=Johann_Michael_Ackner&oldid=149471189. Le modèle "Authority control" n'a pas été ajouté et traduit dans l'article en français. Idem pour le modèle "DEFAULTSORT". L'infobox est incomplète. Mario93 (talk) 06:39, 14 June 2018 (UTC)

Thanks for your feedback, @Mario93.

The support for templates still has to improve in future iterations. Based on your comments, I created tickets about authority control and alternative sorting. Feel free to track their progress or provide further details.

Thanks! Pginer-WMF (talk) 09:43, 15 June 2018 (UTC)

Suggestions

First of all, thanks for your work, it is faster and more powerful. My thoughts:

1. When inserting a template, I want it to allow the selected text to be filled (transferred) to a field (template parameter).
2. When choosing a link - Edit, it should provide two fields to allows modify the existing text and target instead of just entering a new target to replace it.
3. I want a button within right panel to remove the native text from an existing blue link, i.e. remove piped text from a link, for the local article name is appropriate.
4. One icing on the cake, if you allow one-click to mark all gray (does not exist for local wiki) links to missing (red links). It can be for the section or the article, and better if it supports placeholders (used to fill in Translink).
5. Bug: I see the "Mark as missing" has no effect, and no network requests or errors are triggered. It happened when I translate the Receiver_autonomous_integrity_monitoring to Chinese, and I see the link was marked as missing in the final submitted article.
6. If the toolbar buttons and menus are customizable / sort by frequency, it will be more flexible but obviously complex.
7. A little awkward, the inserted template be capitalizing the first letter of template name. YFdyh000 (talk) 17:06, 14 June 2018 (UTC)

Thanks for the feedback, @YFdyh000. I'll provide some comments below:

1-3. Template insertion and link editing mostly reuse the standard behaviour provided by Visual Editor (VE). Regarding (1), it makes sense for inline templates (especially those with one parameter to have a way to quickly reuse the selected text. @Deskana (WMF) may be interested in the suggestion for VE. Regarding (2), Visual Editor team is exploring some options (more details in this ticket) which may help also with (3).

4. Makes sense, I created a ticket to capture the idea.

5. Since the new version uses a new editing surface, some tools still need to be rewritten to work with the new surface. The "Mark as missing" action is still in the works but expected to be completed soon (more details in this ticket).

6. For the case of Content Translation it would be good to investigate which are the specific editing tools that are used more often since the translation case (where the format is often inherited from the source content) may be different than regular editing, and we may consider reordering the options based on that.

7. This is expected to work like in VE. I'll check if there is anything causing an interference on the Content Translation side. Pginer-WMF (talk) 10:23, 15 June 2018 (UTC)

Thank you for your detailed answer. YFdyh000 (talk) 14:19, 15 June 2018 (UTC)

Sometimes caret is not available

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Just now I saw a earlier draft that was sections upset and some missing (I encountered this issue many times in V1), I tried to open it with &version=2, it looked a bit better, but the caret cannot be moved using the mouse or keyboard.

Page: https://zh.wikipedia.org/w/index.php?title=Special:%E5%86%85%E5%AE%B9%E7%BF%BB%E8%AF%91&page=SIM+Application+Toolkit&from=en&to=zh&targettitle=SIM%E5%8D%A1%E5%B7%A5%E5%85%B7%E5%8C%85&version=2&revision=835488406

Error messages in web console:

05:47:12.256 [CX] Section 8349086ba9f141b3c46d903baa6ed7 not restored load.php:2226:864

   mw.cx.dm.Translation.static.getSourceDom https://zh.wikipedia.org/w/load.php:2226:864

   MwCxDmTranslation https://zh.wikipedia.org/w/load.php:2225:1

   mw.cx.init.Translation.prototype.init/< https://zh.wikipedia.org/w/load.php:2233:659

   mightThrow https://zh.wikipedia.org/w/load.php:49:590

   resolve/</process< https://zh.wikipedia.org/w/load.php:50:269

05:47:12.257 [CX] Section b515e6806294a59a15c5a879998db6 not restored load.php:2226:864

   mw.cx.dm.Translation.static.getSourceDom https://zh.wikipedia.org/w/load.php:2226:864

   MwCxDmTranslation https://zh.wikipedia.org/w/load.php:2225:1

   mw.cx.init.Translation.prototype.init/< https://zh.wikipedia.org/w/load.php:2233:659

   mightThrow https://zh.wikipedia.org/w/load.php:49:590

   resolve/</process< https://zh.wikipedia.org/w/load.php:50:269 YFdyh000 (talk) 21:52, 14 June 2018 (UTC)

Thanks for the feedback, @YFdyh000.

Versions 1 and 2 use a different editing surface, which makes the content not compatible between them. To try the new version we recommend to start with a new translation since it is not intended to support continuing an old translation that were started with the older version. The backwards compatibility plan includes more details about it. Pginer-WMF (talk) 10:27, 15 June 2018 (UTC)

Thank you for your answer. YFdyh000 (talk) 14:09, 15 June 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

feedback

First of all, thanks for your work, it seems now a more powerful tool. I observe the possibility to add categories, don‘t lose the references and  mark some errors (your translation title contains invalid characters). To improve/comment:

An important problem: the tool don’t create automatically the link between the article of the wikipedia original and the element wikidata. It’s necessary to do it manually

Before, if in the original text, there was an internal link, and in the destination did not exist the article, the tool deleted the link. Now it leaves the red link. I prefer the solution in version 1

In reference to the templates, I prefer that only remained the name of template, without parameters. You know, in the catalan Wikipedia, we have worked this question.

It doesn’t translate well the dates, but I think that it is a problem of the original structure in texts in French. Pallares (talk) 12:13, 15 June 2018 (UTC)

Thanks for the feedback @Pallares.

Links in Wikidata not being automatically created is a regression we need to fix (more details in this ticket).

Based on your comment, I proposed a new ticket to adjust the behaviour of the missing links. Feel free to share more details or track the progress.

Regarding templates, can you provide an example of the original template you were translating, the result you got for the translation, and the expected result you'd prefer?

Regarding the dates we can consider some improvements (e.g., in the context of templates), but the improvement of the external translation services is out of the scope of Content Translation. Pginer-WMF (talk) 09:31, 18 June 2018 (UTC)

1.Based on your comment, I proposed a new ticket to adjust the behaviour of the missing links. Ok. Així funciona la wiki anglesa. Penso que és millor.

2 can you provide an example of the original template you were translating? Pau, en la wiki catalana s'ha treballat molt en el tema de les plantilles, i aquestes beuen directament de wikidata, sense haver d'afegir paràmetres. Per exemple, ho pots veure i provar a, per exemple, <nowiki>{{infotaula persona}}</nowiki>. Per exemple: amb l'article ''Denise Richards''. A la catalana, no afegim res més. A l'anglesa, francesa....tots els paràmetres que vulguin. A nosaltres no ens cal. Ho "bevem " de wikidata.

3 En relació amb els serveis externs de traducció, segueixo en la batalla amb/junt a/ Apertium. Les coses són lentes...

Gràcies per posar-vos, una salutació també a la noieta d'origen xinès, ho sento no recordo el nom. Vam coincidir a la Hackathon. L'endemà, no vaig poder anar Pallares (talk) 10:32, 20 June 2018 (UTC)

Moltes gràcies pels comentaris, com sempre.

Respecte al suport a plantilles que beuen de wikidata, he creat un tiquet específic. Imagine que la complexitat estarà en distingir quines plantilles beuen de Wikidata i quines no per tractar-les de manera diferent. Però ho investigarem. Pginer-WMF (talk) 11:01, 11 July 2018 (UTC)

Sugerencias

Buenas noches, Pau.

He probado el nuevo traductor en el artículo

• en:Viewing frustum
• es:Campo de visión (gráficos)

Trabajo sobre Android en una tableta Samsung, con la correspondiente versión del navegador Chrome.

He notado notables mejoras en el editor, especialmente en las referencias a otros árticulos (ventanas azules) y en la traducción de las referencias intercaladas en el texto.

Sugerencias

• Referencias a otros artículos: La aplicación traduce por defecto la etiqueta original del artículo inglés. Esto puede ser un inconveniente, especialmente si existe el correspondiente artículo en español. Por ejemplo, si en el artículo en inglés existe una referencia a Vincent van Goghg, en la ventana azul del traductor aparecería Vincent furgoneta Goghg. Sugerencia: sugiero que se pudiera elegir utilizar diectamente el nombre con el que se creó el artículo en español...
• Referencias a libros o páginas de internet: aquí la aplicación traduce al español los títulos de libros y artículos. En mi opinión, debería dejarse la posibilidad de elegir si se taducen o no. Al traducir el artículo que cito al principio, no he visto la manera de conservar los títulos en inglés de las referencias (si miras el capítulo de las Referencias del artículo en cuestión, verás un horrible "Qué Es una Vista Frustum?", que debería figurar en inglés). Sugerencia: permitir elegir si cada referencia se deja en inglés o se traduce al español.

Nota:

• Todavía no he probado el nuevo traductor con un artículo que contenga fórmulas matemáticas (con los códigos <math></math>). En la versión anterior de la aplicación, la traducción de estas fórmulas era un verdadero desastre.

---

Agradeciendo el interés que te tomas en mejorar esta herramienta:

Saludos:@Wiki LIC

---

Pd: por cierto, acabo de ver que la aplicación no había enlazado el nuevo artículo traducido a la base de de datos de wikidata. Lo he hecho yo mismo manualmente.

---

Más sugerencias:

• Añadir contenidos traducidos a artículos existentes: por ejemplo, la entrada de es:Pierre de Fermat en español, tiene una biografía muy corta, que me gustaría ampliar traduciéndola del inglés. Sugerencia: sería muy útil que también se pudieran añadir traducciones parciales a un artículo existente. Se me ocurre que estos nuevos párrafos traducidos se localizaran al final del artículo existente (para que el editor pudiera luego recolocar el texto a su gusto) o incluso utilizar el taller del editor para almacenar temporalmente estos textos. Eso sí, en estos casos la herramienta debería chequear la consistencia de las referencias del tipo <ref name=Miref />, para no dejar ninguna descolgada.
• Listas negras: no es infrecuente encontrarse que no es posible grabar una traducción porque una llamada a un elemento de una lista negra lo impide. Esto también pasa con algunas plantillas obsoletas. Sugerencia: en el mensaje que avisa de la presencia de un elemento de una lista negra, debería darse el nombre o la localización del elemento que causa el problema. Buscar estos elementos por prueba y error es un auténtico trabajo detectivesco, que en ocasiones hace perder mucho tiempo.
• Plantilla Traducido de: ya puestos (esto me preocupa menos), sería de agradecer que la aplicación añadiera a la página de discusión de la entrada creada en español, la plantilla {{:es:ep|Traducido de}}, convenientemente rellenada.

---

Saludos de nuevo:@Wiki LIC Wiki LIC (talk) 21:02, 16 June 2018 (UTC)

Hola @Wiki LIC,

Muchas gracias por tus sugerencias y todos los detalles aportados. Algunos comentarios a continuación:

En primer lugar, me ha sorprendido leer que utilizas una tableta. Pese a que la herramienta no está principalmente enfocada al uso de tabletas, recientemente hicimos algunas mejoras para dispositivos táctiles y pantallas reducidas. Nos interesa conocer más sobre el uso de la herramienta en estos dispositivos y los problemas específicos que en ellos encontráis. Así que cualquier detalle será bienvenido.

Respecto a las referencias a otros artículos, uno de los problemas subyacentes es que las traducciones erróneas producidas por los servicios de traducción deben ser corregidas repetidamente para cada instancia (cambiando "furgoneta" por "van" en tu ejemplo cada vez). Una idea para ayudar con este problema está descrita en este ticket. El caso de las referencias a artículos, sería un caso particular del anterior (y más sencillo de implementar) en el que se podría ofrecer el texto alternativo para utilizarlo. He creado un ticket para este caso específico. Puedes añadir cualquier comentario sobre la idea y seguir el progreso del ticket.

En cuanto a las referencias a libros o páginas de internet, miraré con más detalle algunos ejemplos para explorar posibles soluciones en la línea del caso anterior o on una aproximación diferente. En cualquier caso, la sugerencia tiene mucho sentido.

Sobre enlazar automáticamente en Wikidata los artículos publicados, se trata de una regresión de la nueva versión que tenemos previsto solucionar (más detalles en este ticket).

Respecto al resto de sugerencias, son también aspectos que tenemos previstos para el futuro de la herramienta, aunque puede que tarden algo más en completarse ya que nuestra prioridad es poder reemplazar la versión antigua del editor con la nueva lo antes posible. En cualquier caso, enlazo a los tickets relacionados para que tengas más información sobre nuestras ideas iniciales para expandir páginas existentes, comunicar mejor los errores mostrando los elementos afectados (incluidos las listas negras), y proporcionar más opciones de publicación para el artículo (incluyendo opción para que las distintas comunidades puedan añadir la plantilla que comentas o equivalente marcando una casilla)

Un saludo y muchas gracias por usar la herramienta de traducción. Pginer-WMF (talk) 10:59, 19 June 2018 (UTC)

No se que tan difícil sería esto para los desarrolladores o no se si lo pueden hacer pero esto ya se planteó en phabricator y en la discusión de la primera versión, se trata de agregar google traslate como opción porque honestamente la traducción con Apertium y Yandex es pésima, he probado la nueva versión y sigue este problema, otra cosa que noté es que allí no me funciona ell gadget de Google Traslate que programó Endo999 y que lo uso en todas las traducciones, esto es una sugerencia para mejorar Content Traslation Ignacio2403 (talk) 19:57, 3 August 2018 (UTC)

The new version

Thank you for your efforts in developing the translation features. But I think the first version is better than the new version where I have translated two articles with the new version (second) and noticed good additions but there are some disadvantages (the translation can not be saved in a user's draft page) and also But on the other hand, the translation page is generally good. It can add templates and portals as well as the options on the top left of the page, but frankly I can not do without the first version because it is easier - and maybe this is only in Arabic - thanks again for your good efforts. I apologize if I can not communicate my thoughts in English. --~ أبو هشام (talk) 22:10, 16 June 2018 (UTC)

Thanks for the feedback, @أبو هشام السوعان.

The new version is still in active development and there are many aspects of version 1 that have not been added yet. If you can indicate which are the aspects you find missing, and why are those important to you, that would be very useful to improve the tool.

Currently in version 2 it is possible to select the destination where the article will be published. You can select it from the cog icon next to the "publish" button. Please, let us know if you find any particular issue in that process.

Thanks! Pginer-WMF (talk) 09:45, 18 June 2018 (UTC)

I will try the tool again and messages you soon.

Thanks أبو هشام (talk) 10:37, 18 June 2018 (UTC)

Hi, I still think that using the first version of the translation tool is better. I have a page in the domain of the user I use to translate the articles and translate each article to this page, then make edits to the article before publishing it. This property is not available in the second version of the tool. If it is not understood, you can read the history of this page. Thanks. أبو هشام (talk) 17:49, 19 June 2018 (UTC)

Thanks for the details, @أبو هشام السوعان.

From your comment it seems you are referring to the limitations of the namespace that can be used when selecting the source article to translate. We plan to improve this, and there is a ticket capturing the details. Feel free to track the progress of the ticket and add any comment.

Thanks! Pginer-WMF (talk) 09:15, 2 July 2018 (UTC)

Sugerencias 2 >> Error con los codigos ${\displaystyle }$

Buenas tardes otra vez, Pau.

Te escribo para comentarte que he intentado traducir al español con la nueva versión de la aplicación el artículo en inglés en:Steiner inellipse, muy cortito, pero con varias líneas de símbolos matemáticos, como por ejemplo:

$a^2{x}^2+b^2{y}^2+c^2{z}^2-2abxy-2bcyz-2cazx=0$

En este caso, he utilizado un PC con W7, y con el navegador Chrome.

El resultado ha sido que al intentar traducir las citadas líneas de símbolos matemáticos, la aplicación indica un error, y se niega a hacer nada con estas líneas.

Puedes hacer la prueba tú mismo (he dejado sin publicar el artículo...)

Saludos: @Wiki LIC

PD: ojo, que acabo de traducir el artículo en cuestión (con mi aplicación casera, que tira del google translator) Wiki LIC (talk) 18:09, 21 June 2018 (UTC)

Muchas gracias por los detalles, @Wiki LIC.

He intentado reproducir el problema y parece que se trata del problema descrito en este ticket. Hasta el momento hemos identificado el fallo técnico en el editor visual causante del problema, y el equipo correspondiente ya está trabajando en resolverlo.

En cualquier caso, el soporte a tipos específicos de contenido cómo formulas presenta algunas complejidades, que todavía no nos hemos metido a fondo a desentrañar. Pero en los próximos meses trabajaremos en ello, al menos seleccionando los casos más habituales en nuestro contenido.

Un saludo y muchas gracias. Pginer-WMF (talk) 11:54, 29 June 2018 (UTC)

Adding words?

It sounds also to me as sci-fi, but it seems that the new verson ginving words into translated text. Sometimes the authomatic translator uses inappropriate word, which appeares again after deletion. Is it possible? Meszaros Miklos (talk) 08:36, 22 June 2018 (UTC)

Hi @Meszaros Miklos,

Machine translation is provided by the different translation services the tool integrates. So the translation may be more or less precise depending on the quality of the service for a given language pair. From your description it is not clear to me in which circumstances are the problematic words appearing. If you can describe a more specific example with steps to reproduce, that would be very useful for us to identify and solve any associated issue.

Thanks! Pginer-WMF (talk) 11:29, 29 June 2018 (UTC)

Translating a section

The tool works very well when translating a whole article. In my experience, it also happens that an article exists in languages A & B and that only a few sections need translating. There are only two options available now : 1) not using the tool 2) creating an article with a new name B+, translating the necessary sections in B+, merging B & B+, deleting B+. It would be great to be able to use the tool to translate a section directly into an existing article AnTeaX (talk) 16:22, 27 September 2018 (UTC)

Thanks for the positive comments about the tool, @AnTeaX.

As you mentioned, the main focus of the tool is to start an initial version of a new article. Currently, as you described, there are some workarounds that can be made to expand existing articles but the workflow is not very fluent. We plan to improve this process in the future (check this ticket for more details).

Having said that, our main focus right now is to complete the work on version 2 for the translation editor. we want to replace the previous version of the editor before adding additional capabilities such as expanding existing articles. In this way we can bring the updated version to all translators and no longer need to maintain two different versions of the editor. Pginer-WMF (talk) 07:37, 1 October 2018 (UTC)

Reference problem

I'm working on translation from English to Japanese. Since V1 I had a problem that the reuse reference style such as <ref name="name" /> disappears when I publish an article. Only the first defining refs survives. Actually English ref syntax and Japanese ref syntax are same so I'm fixing refs by copy & paste after the article is published, but this is too troublesome work. I saw the V2 solved some reference trouble so I tried it, then found that reuse refs just disappear before translating (when I touch the right field). Is there any way to reserve reuse refs? McYata (talk) 15:02, 8 October 2018 (UTC)

Hum with Google Chrome I get this https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:Doc_James/Opioid_overdose

With Firefox it works better and I get this https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:Doc_James/Urinary_tract_infection Doc James (talk) 21:56, 8 October 2018 (UTC)

Would recommend that you use firefox at this point. Doc James (talk) 21:57, 8 October 2018 (UTC)

I tried firefox but nothing have changed...(please see the bottom of the article)

https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:McYata/%E3%83%95%E3%82%B4%E3%83%BB%E3%82%B3%E3%82%A6%E3%82%A9%E3%83%B3%E3%82%BF%E3%82%A4/firefox

You will find many of refs have disappeared from original;

https://en.wikipedia.org/wiki/Hugo_Ko%C5%82%C5%82%C4%85taj McYata (talk) 15:34, 9 October 2018 (UTC)

Yes I tried aswell and got the same thing https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:Doc_James/Hugo_Ko%C5%82%C5%82%C4%85taj Looks like this needs fixing. Doc James (talk) 21:54, 9 October 2018 (UTC)

Thanks for reporting the issue with such detail, @McYata, and thanks for helping with the diagnosis, @Doc James.

Using these examples, I created a ticket for the specific case of this style of reference. This fits in our immediate plans to improve references support, so we may be able to work on it in a few weeks.

Thanks! Pginer-WMF (talk) 11:44, 11 October 2018 (UTC)

I confirm that the problem have solved. Now I'm free from the troublesome works to fix refs manually.

https://ja.wikipedia.org/wiki/%E5%88%A9%E7%94%A8%E8%80%85:McYata/%E3%83%95%E3%82%B4%E3%83%BB%E3%82%B3%E3%82%A6%E3%82%A9%E3%83%B3%E3%82%BF%E3%82%A4/test

Thank you very much! McYata (talk) 04:59, 6 November 2018 (UTC)

Thanks for confirming the problem is solved, @McYata.

Please, keep using the new version of the tool and reporting any issue you may find! Pginer-WMF (talk) 17:08, 7 November 2018 (UTC)

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. McYata (talk) 01:30, 8 September 2019 (UTC)

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. Doc James (talk) 11:12, 8 September 2019 (UTC)

Trouble Deleting an Old Translation and Starting Over

Having trouble deleting a translation and starting over. I started https://ja.wikipedia.org/wiki/Special:ContentTranslation?page=Opioid+overdose&from=en&to=ja&targettitle=Opioid+overdose&version=1 and now want to delete it to start over. But when I go back to all translations and delete it, and than reopen it does not bring me back to the normal starting point but continues were I left off. Doc James (talk) 22:01, 8 October 2018 (UTC)

Thanks for the feedback, @Doc James.

If the problem happens with a translation that you have published before, this may be the issue described in this ticket. This issue is related to a limitation with our current data model which we plan to address once the work on version 2 is completed. So the fix may still be a few months ahead, but it is in our roadmap.

Meanwhile, making a copy of the source article to your user namespace or using a different user account could be some workarounds that, although inconvenient, may be of some help. Pginer-WMF (talk) 11:11, 11 October 2018 (UTC)

Okay thanks. Just want to be able to delete and start over to make trouble shooting bugs easier. No worries, work around is fine. Doc James (talk) 11:56, 11 October 2018 (UTC)

Абзацы со сносками не переводятся

В новой версии абзацы со сносками не переводятся, вставляется только сноска без текста. При выборе "Исходный текст" текст появляется, возвращение "Использовать Yandex.Translate" снова оставляет только сноску. Igel B TyMaHe (talk) 09:31, 19 October 2018 (UTC)

На какой странице это произошло? Amir E. Aharoni {{🌎🌍🌏}} 19:16, 20 October 2018 (UTC)

А, смог воспроизвести. Спасибо.

https://phabricator.wikimedia.org/T207570 Amir E. Aharoni {{🌎🌍🌏}} 19:32, 20 October 2018 (UTC)

I can't translate wikipedia essays from English to Marathi

I tried to take Wikipedia:Wikipedia does not need you and similar essays for translation from en to mr but I couldn't input the same. So probably it's a problem of namespaces. And this tool is trained to take input from article namespace only. But I am sure this can be extended to wikipedia:XXX namespace too. QueerEcofeminist (talk) 07:49, 24 October 2018 (UTC)

Thanks. To solve it in time, have a temporary copy of the pages source text in your user namespace, translate it. When published, order to delete the temporary source and move the translation for Your destination languages project user namespace to its target namespace. Hans Haase (有问题吗) 17:02, 24 October 2018 (UTC)

thats what i do now a days... QueerEcofeminist (talk) 08:26, 26 October 2018 (UTC)

Thanks for the feedback @QueerEcofeminist,

Currently the search for articles is only limited to the main namespace, but it is possible to access other namespaces using the URL. For example, you can translate "Wikipedia:No climbing the Reichstag dressed as Spider-Man" by accessing the following link: https://en.wikipedia.org/wiki/Special:ContentTranslation?page=Wikipedia:No_climbing_the_Reichstag_dressed_as_Spider-Man&from=en&to=fr&version=2 (you can change the "page" parameter to translate a different page)

Expanding the search to pick articles from other namespaces is in our plans (more details in this ticket). As part of that process we need to identify which namespaces have types of contents that the tool is not able to deal with. Pginer-WMF (talk) 07:44, 26 October 2018 (UTC)

@Pginer-WMF

Thanks a lot, This is something I wanted. It would be really helpful for me and my friends too. As there is much content on the guidelines, simple procedures, and much more is in the form of essays on enwiki and local and small wikis like mrwiki lacks it badly....

thanks and regards. QueerEcofeminist (talk) 08:37, 26 October 2018 (UTC)

Section titles trigger "article is too small" filter

Even with all paragraphs fully translated I see ukwiki abuse filter notification next to the section titles. (It doesn't prevent page creation.) Ата ^(talk) 12:18, 20 November 2018 (UTC)

Hi,

Thanks for the report.

I have passed it on to the developers, however I see at least one issue with the filter itself. Its code says (article_articleid == 0), and according to the AbuseFilter user manual, article_articleid is deprecated. Can anyone who maintains AbuseFilter in the Ukrainian Wikipedia check this? This may have to be updated.

Tagging this filter's maintainers: @Sergento, @Dim Grits, @Yakudza, @NickK, @Ilya.

Thanks! Amir E. Aharoni {{🌎🌍🌏}} 12:51, 20 November 2018 (UTC)

I just received a very similar complaint about the Russian Wikipedia from @Раммон. The filter definition in the Russian Wikipedia also uses (article_articleid == 0). Even though I'm not sure that this is the thing that causes the problem, it should be corrected. @Q-bit array, @OneLittleMouse, can you please take a look?

In any case, I'm passing this on to Content Translation developers. Amir E. Aharoni {{🌎🌍🌏}} 11:50, 26 November 2018 (UTC)

This problem raised again. Please, resolve it. Раммон (talk) 11:38, 29 November 2018 (UTC)

The problem has not been resolved yet. Раммон (talk) 09:37, 10 February 2020 (UTC)

The tool should not be translating references...

but it is :(

In articles with many references, the amount of work this entails to fix is so out of the park, that it simply isn't feasible.

In Hebrew - the link button is also exactly as far as it can be from the working text, which seems like a pretty severe usability issue. Also, I can't remove links, and for some reason if I do "copy/paste" to any text, it inserts a link to ENWIKI (which is also a big NO).

Too much of the additional functionality is hidden behind menus, entailing additional clicks (like italics and bold).

Those are my main issues so far.

Details: Translating Cinema of Africa from English to Heberw

Using Chrome. TMagen (talk) 15:42, 22 November 2018 (UTC)

Thanks a lot for the feedback.

In articles with many references, the amount of work this entails to fix is so out of the park, that it simply isn't feasible. -> What do you mean exactly by "translating references"? Can you please give an example?

In Hebrew - the link button is also exactly as far as it can be from the working text -> When you say "the link button", do you mean the "chain" button in the toolbar? Or the panel that shows the title of the target article? Or something else? By the way, in the old version there is no link button at all, and in both versions linking is automatically suggested if you select some text (although there are some bugs with it in the new version, which we will soon fix). Also, you can use Ctrl-K to add a link, like in Visual Editor, Microsoft Word, Gmail, and Google Docs (Command-K if you are on a Mac computer).

Too much of the additional functionality is hidden behind menus, entailing additional clicks (like italics and bold). -> This works almost the same way as it works in Visual Editor. You can use Ctrl-B and Ctrl-I for bold and italic, like in Visual Editor, Microsoft Word, Gmail, and Google Docs (Command-K if you are on a Mac computer). The idea is to allow most of the actions that are available in Visual Editor also while translating—not only Bold and Italic, but also adding references, templates, math, etc. Perhaps our designer @Pginer-WMF may want to add something about this. Amir E. Aharoni {{🌎🌍🌏}} 18:33, 22 November 2018 (UTC)

Also, I can't remove links -> This is supposed to be possible. If you click on a link, a panel appears in the sidebar. This panel has a "trash can" icon. If you click, the link is supposed to turn into plain text. Does it work?

for some reason if I do "copy/paste" to any text, it inserts a link to ENWIKI (which is also a big NO). -> I confirm, thanks. Reported at https://phabricator.wikimedia.org/T210173 Amir E. Aharoni {{🌎🌍🌏}} 18:46, 22 November 2018 (UTC)

Thanks for the quick response!

1) References that are not links are being translated - they look like this:

Gugler, ג ' וזף (2003). אפריקה הסרט: לדמיין מחדש את היבשת.

or -

2. Diawara (1992). אפריקה קולנוע, עמ ' 23-24. ראה גם הנלי, פול (2010),הרפתקה של ממש: ג 'ין Rouch וכלי הטיס אתנוגרפי קולנוע, שיקגו: הוצאת אוניברסיטת שיקגו, עמ' 310-337.
3. לקפוץ מעלה^Diawara (1992). אפריקה קולנוע, עמ ' 23-24. ראה גם הנלי, פול (2010),הרפתקה של ממש: ג 'ין Rouch וכלי הטיס אתנוגרפי קולנוע, שיקגו: הוצאת אוניברסיטת שיקגו, עמ' 310-337.

The references are not in the text, and so I don't translate them when I translate the text, and anyway, they shouldn't be translated :)

you can see this in the article "הקולנוע האפריקאי" on hewiki, I've fixed most already, I'll leave the rest for the time being.

2) Links - not the chain icon, when you highlight text and it recognizes the link, there is a button "הוספת הקישור" - it's to the far left at the top of the panel section. I will probably adjust to this, it isn't a show stopper, but I do notice it while working. Thanks for the shortcut tip!

I'll continue to work with the tool, I appreciate all the work that has clearly gone into it, and let you know if I find anything else.

Cheers TMagen (talk) 19:27, 22 November 2018 (UTC)

Oh, I see. This reference is not in a template, which is quite rare in the English Wikipedia :)

If it's in a template, then it's not auto-translated.

I filed this as a bug: https://phabricator.wikimedia.org/T210205 Amir E. Aharoni {{🌎🌍🌏}} 20:40, 22 November 2018 (UTC)

Report bugs ?

Could you add an easily visible link to report bugs in Phabricator in the page describing V2 ? It seems that V2 has been activated on some wikis (like frwiki), but the link on the tag brings to this page, without an obvious mean to report the problems in Phabricator. NicoV (talk) 10:36, 23 November 2018 (UTC)

In fact, it's activated in all languages in an opt-in mode. Every user who enabled the beta feature can enable and disable CX2 from the dashboard using the link "Try the new version". However, we do gradually ping some of the larger wikis and ask for detailed comments.

We read both this page (Talk:Content translation/V2) and the usual talk page (Talk:Content translation) every day, and both pages are acceptable places for bug reports.

If you want to report a bug in Phabricator, you can use the same tag, #ContentTranslation. You can add "CX2" to the title to emphasize that the task is about the new version. Amir E. Aharoni {{🌎🌍🌏}} 14:48, 23 November 2018 (UTC)

I understand that I can do everything manually myself, but wouldn't it be simpler for volunteers reporting bugs to have a direct link doing all of that rather than letting them do it manually ? For example, this link lets you report a bug with the tag already added and with the title beginning by CX2 : https://phabricator.wikimedia.org/maniphest/task/create/?projects=ContentTranslation&title=CX2 NicoV (talk) 14:53, 23 November 2018 (UTC)

Oh, I see what you mean. Good idea. I'll pass it on. Amir E. Aharoni {{🌎🌍🌏}} 16:37, 23 November 2018 (UTC)

Thanks for the feedback @NicoV.

We want to keep this page as the main feedback entry point to support a wider audience, supporting users that can share their experience but are not familiar with Phabricator and bug reporting. Having said that, I agree that we can make it easier for those users that are familiar with Phabricator. I added the link for ticket creation to Phabricator in the information sidebar of this page. It is also present in the "Provide feedback" section of the page. Pginer-WMF (talk) 10:51, 28 November 2018 (UTC)

Překlad citačních šablon do češtiny (Czech)

Překládal jsem Haarova míra do češtiny z angličtiny a asi nejhorší bylo, že se nepřeloží citační šablony. A anglické nefungují. Buď by se měly ty anglické zprovoznit i na české wiki, nebo by je nástroj měl správně překládat. Jan Spousta 194.228.23.145 (talk) 09:00, 28 November 2018 (UTC)

Пераклад на беларускую (тарашкевіца)

…does not work at all. The only error it returns after clicking any parapgraph to translate is «Automatic translation failed!» I tried to translate «Трыстан-да-Куньня» from be-wiki. Taravyvan Adijene (talk) 10:09, 17 December 2018 (UTC)

See other topics of this talk, how to install the Translator script, and You will be lucky. Hans Haase (有问题吗) 10:18, 17 December 2018 (UTC)

Searching talk page doesn't return any result about «Translator script», can You be more specific? Taravyvan Adijene (talk) 10:22, 17 December 2018 (UTC)

Sorry, go for installation of automatic translation these topics: The script from Endo999, required on the user side, see Topic:Udmnnnrjpzq5dbe0 or how to install in Topic:Uj61e2fkvlf5qy5o and Topic:Uas7z3lf379cp60t. Then mark the text section and to hold down CTRL and ALT key to translate the marked text inside the CXT. Hans Haase (有问题吗) 10:28, 17 December 2018 (UTC)

I have not vector but modern skin installed. Should I try to do instructions provided into modern.js file? Or CT2 doesn't working on it and I shouldn't even try it? Taravyvan Adijene (talk) 12:03, 17 December 2018 (UTC)

The potential risks are described there. You first may try to copy and paste Google Translator, with some text from the article to see what You will get. Hans Haase (有问题吗) 12:16, 17 December 2018 (UTC)

Prenvented publishing because of "unmodified machine-translated text"

When I tried to publish new translated article, the tool said "Your translation cannot be published because it contains too much unmodified machine-translated text". However it can't be, because first of all I chose "Use source text" instead of using "Automatic translation", which is contained in Content translation tool. Therefore the sentences which I translated contains 0% machine-translation.

Every time I translate article get warning about "unmodified machine-translated", and I have avoided it by choosing "Mark as resolved". Now this is the first time I cant find any way to avoid it. What can I do? McYata (talk) 15:29, 21 December 2018 (UTC)

Thanks for the feedback, @McYata.

This issue has been fixed in the code recently, and the fix will be available to users during the next weeks. You can read more details in this ticket. If the error persists after a couple weeks, please let us know and we'll investigate the issue further. Pginer-WMF (talk) 08:49, 26 December 2018 (UTC)

I waited a few days and tried again. I could publish the article and haven't seen the same error until now. Thanks! McYata (talk) 09:11, 30 December 2018 (UTC)

Well, I got the same error again...the first article the error emerged was "Gunpowder Empires", and this time "Serica". It might happen when I try to translate some articles which contains <blockquote>, which can't be rewritten in Contents Translation at present. (though I haven't confirmed it at all.) McYata (talk) 11:06, 4 February 2019 (UTC)

Sometimes a different error appears, which says "detected spam contents. See "cs.com". " (I don't know the real original English message. Japanese message is 「あなたの翻訳にスパムの可能性のあるコンテンツを検出しました。詳細：.cs.com」.) What is cs.com? How can I deal with it? McYata (talk) 08:39, 11 February 2019 (UTC)

Thanks for the development

Thank you now I can publish the translation on the personal domain pages in this version, and I have one note is the references template at the end of the translation. Thanks again. أبو هشام (talk) 09:08, 30 December 2018 (UTC)

Attribution required

Hi there! The content of Wikipedia is licensed under a CC BY-SA license which requires attribution (and sharing alike). This tool should provide attribution using templates made for this use, e.g. https://en.wikipedia.org/wiki/Template:Translated_page --Palosirkka (talk) 14:48, 31 December 2018 (UTC)

Users are required to order a en:Wikipedia:Requests for page importation, if not done by a bot. Hans Haase (有问题吗) 15:07, 31 December 2018 (UTC)

The creators of the source article are credited in a link to the revision of the source article from which the translation was made, which is added automatically to the edit summary of the published version. This is compatible with the CC BY-SA license and with Wikimedia's Terms of Use, which require you as the re-user to give attribution "through hyperlink [...] to the page or pages that you are re-using". Amir E. Aharoni {{🌎🌍🌏}} 17:57, 31 December 2018 (UTC)

In production, but many problems

I see you have put V2 in production in frwiki for about a week. I checked the last 5 translations done with the new version, and not one is free of problems... I've reported the problems in Phabricator : T213255, T213256, T213257, T213258, T213259.

I checked a few more edits: T213262, T213273, T213275, T213276, T213277.

Has it been really tested before being put in production? NicoV (talk) 11:04, 9 January 2019 (UTC)

Thanks for the reports, @NicoV.

Version 2 is an opt-in feature that is available for Content translation users. We are making version 2 more visible for existing Content Translation users as it gets improved in order for them to transition from version 1 to version 2.

Version 2 uses the Visual Editor editing surface which provides a more solid experience editing wikitext compared to version 1. Version 2 is still in active development, and we have processes to test, get feedback and improve.

Given the diversity of the content, the number of languages supported and the many templates that exists on each wiki (that were not designed to be transferred across languages), it is not feasible to anticipate all the problematic combinations, and we appreciate the reports to identify such issues.

I know that similar issues about the quality of the wikitext produced were reported in the past for version 1. Those were hard to fix in version 1 without making a big architectural change. Version 2 represents such change, many of those have been already fixed, and it is in a better position to get more fixed. Pginer-WMF (talk) 11:56, 10 January 2019 (UTC)

@Pginer-WMF

I do understand this should be an opt-in feature, but as it is still beta (and still generating a lot of problems in the results), why do you advertise it so much?

For example, I've disabled CX in my preferences (beta tab), but I still get popups messages to use it whenever I end up on a page that was deleted because it's not admissible... Why don't you only give notifications to users that have explicitly requested to receive them, rather than forcing them on users who requested not to have them?

Also, why don't you give more prominent message to explain that CX and CX2 is "beta" software and that users opting in should check the result of their translation, especially if they create translations in the main namespace?

CX has been creating buggy articles in production for 3 or 4 years now, and it keeps doing so: when will something really be done about this? NicoV (talk) 12:37, 10 January 2019 (UTC)

And when you say "it is not feasible to anticipate all the problematic combinations": I would agree if the problems were on a small number of edits, but they appear on a vast majority of articles. For example, I just checked 1 translation, and I reported T213419... NicoV (talk) 12:44, 10 January 2019 (UTC)

Handling of templates

Can we get CX2 to handle templates better? All the spacing goes missing when the template is brought over which makes it difficult to parse.

https://es.wikipedia.org/w/index.php?title=Usuario:Doc_James/Gastroschisis29&action=edit Doc James (talk) 03:59, 23 January 2019 (UTC)

Supported language pairs for MT

I was eager to see if the new machine translation services provide more support for German (e.g. to or from English). But I still get "Translation services not available for the selcted languages" (de->en). Should I be patient, or is there any config, tweak, cached pages that I overlook? (URL ends on "&version=2") Aeroid (talk) 09:55, 30 January 2019 (UTC)

Thanks for the feedback, @Aeroid.

Machine translation support for English and German as target languages is not enabled yet. Support for new languages is expanded gradually, and I captured your comment in this ticket to keep track of the different requests in this area. Feedback from the community is very important to expand the support.

Meanwhile, an alternative could be to translate from German to Simple English, for which machine translation is available.

Thanks! Pginer-WMF (talk) 10:10, 5 February 2019 (UTC)

Content translation/V2

Can this version be compatible with old versions like Content translation 1 ??? Cause months ago I tried to translate with CT/V2 and i can't publish an article, it's also is very slow. Thank you. 190.234.57.221 (talk) 15:03, 24 February 2019 (UTC)

Version one and version two of the translation editor are not compatible with each other. Nikerabbit (talk) 10:09, 27 February 2019 (UTC)

File name prefix: pls unlimit adding "Wikipedia:" on jawiki

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. Omotecho (talk) 17:45, 10 March 2019 (UTC)

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? Xaosflux (talk) 18:40, 10 March 2019 (UTC)

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. Omotecho (talk) 19:14, 10 March 2019 (UTC)

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 Xaosflux (talk) 21:21, 10 March 2019 (UTC)

Would you try CX2 with a Wikipedia: prefix page please? Omotecho (talk) 23:40, 10 March 2019 (UTC)

I created it as "Wikipedia:Sandbox3" already, not sure what else to look at? Xaosflux (talk) 23:42, 10 March 2019 (UTC)

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 ? Omotecho (talk) 00:18, 11 March 2019 (UTC)

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. Xaosflux (talk) 00:23, 11 March 2019 (UTC)

You are right, normal pages can be renamed to Wikipedia:yyy name. I agree with you we are unable to translate FROM Wikipedia:xxx pages, a type of special page. Cheers, Omotecho (talk) 01:00, 11 March 2019 (UTC)

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 (履歴継承). McYata (talk) 00:52, 11 March 2019 (UTC)

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. Omotecho (talk) 12:35, 22 March 2019 (UTC)

this tool is apparently broken

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... Trappist the monk (talk) 19:07, 25 March 2019 (UTC)

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 Xaosflux (talk) 19:57, 25 March 2019 (UTC)

"Automatic translation failed!"

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? McYata (talk) 08:25, 9 April 2019 (UTC)

Wikidata links aren't automatically created

I review new pages in the portuguese Wikipedia, and I always have to link articles manually. Just letting you all know. Bageense (talk) 15:05, 4 September 2019 (UTC)

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 (有问题吗) 15:26, 4 September 2019 (UTC)

@Hans Haase, the complaint is about something different.

@Bageense, I also heard from other people. We'll look into it. Amir E. Aharoni {{🌎🌍🌏}} 16:26, 4 September 2019 (UTC)

@Hans, I'm just an average editor, I don't have the capacity to do all of that you suggested. Thanks, Amire. Bageense (talk) 16:47, 4 September 2019 (UTC)

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 Bageense (talk) 22:12, 6 September 2019 (UTC)

I've translated an article from portuguese to english., Same thing. en:Feminism in Brazil Bageense (talk) 19:32, 21 September 2019 (UTC)

Sick of this tool

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. 2804:14C:5582:1285:E061:F1D7:6522:189B (talk) 12:34, 19 October 2019 (UTC)

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. Hans Haase (有问题吗) 13:48, 19 October 2019 (UTC)

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. Jeblad (talk) 14:08, 19 October 2019 (UTC)

"suggestions" in the content translation tool

What is the source for the suggestions page in the tool? Sai kiranmai (talk) 07:01, 25 February 2020 (UTC)

I believe they are coming from the various Content translation/Machine Translation engines, depending upon which language pair someone is going between. Quiddity (WMF) (talk) 20:05, 25 February 2020 (UTC)

Yes. But, is there any particular page which displays the list of articles that are displayed in the suggestions page? Sai kiranmai (talk) 08:54, 27 February 2020 (UTC)

Oh! Sorry, I misunderstood the question. For that, see Content translation/Documentation/FAQ#What are the "Suggestions" in the dashboard? Quiddity (WMF) (talk) 18:18, 27 February 2020 (UTC)

The overused must be stopped: low quality translation

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)

Include "translated page" template

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. 1Veertje (talk) 12:44, 28 July 2022 (UTC)

Agree would be nice. One does get attribution in the first edit that creates the translation in question.[1] We have had 750 medical translations as part of our relaunch.[2] 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? Amir E. Aharoni {{🌎🌍🌏}} 19:26, 28 July 2022 (UTC)

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, Omotecho (talk) 01:50, 29 July 2022 (UTC)

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? Amir E. Aharoni {{🌎🌍🌏}} 17:46, 29 July 2022 (UTC)

@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, Omotecho (talk) 11:17, 30 July 2022 (UTC)

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. Amir E. Aharoni {{🌎🌍🌏}} 12:20, 30 July 2022 (UTC)

@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, Omotecho (talk) 13:36, 30 July 2022 (UTC)