Wikipedia talk:LLM-assisted translation
| This is the talk page for discussing improvements to the LLM-assisted translation page.
|
|
Template Question
editShouldn’t the template for “this needs translation” reflect the rules stated here? I see it fairly often when reading the Wiki and it still states that accessing the citations in the original language is optional. Not to mention there is no requirement to speak the language of the original article.
For what it is worth, this template appears unfolded by default on the app, where all tables and infoboxes are hidden by default. For individuals who are using the app, the template instructions are far more visible than these guideline pages. ExtantRotations (talk) 19:30, 15 March 2026 (UTC)
- For the record: these templates are what I mean. There are over 200 of them used across hundreds of thousands of articles. In mobile, the notice appears folded up and requires you to click “show” to see more, but in the app all the instructions appear by default. They appear immediately under the lead and are vastly more prominent than the infobox. ExtantRotations (talk) 18:43, 16 March 2026 (UTC)
Clarification on allowed scope of prompting
editRight now, this guideline is a bit vague on exactly what one is allowed to ask an LLM to do in the course of translation. For example, I assume a prompt like "Translate the following paragraphs to English from Portuguese" is allowed. I also assume that a prompt like "write an English Wikipedia article using the text of the corresponding Portuguese article" should be disallowed, because now one is asking the LLM in a more open-ended way to construct or augment an article, which is disallowed more broadly by WP:NOLLM. However, the guideline as currently written does not make this explicit and I suspect that some cases at WP:AINB are the result of this disconnect. Should the guideline be clarified? Einsof (talk) 03:19, 31 May 2026 (UTC)
-
Agree, that definitely needs to be clarified. If all you are doing is asking the LLM to do a strict translation of a high-quality article that already exists in another language and you've checked the sources yourself, then in my opinion that's no different from using Google Translate, which is not an LLM and should be taken into account. Gommeh (talk! sign!) 03:31, 31 May 2026 (UTC)
-
Perhaps a reminder: "Machine translation tools, including LLM-based tools, may be used only to produce close translations of non-English text. Using an LLM to otherwise add or alter material in an article is prohibited by Wikipedia's LLM guidelines." Einsof (talk) 12:16, 31 May 2026 (UTC)
- Agreed- the only problem is dealing with hallucinations, or things getting lost in translation. You should be familiar enough with the source language and/or the topic at hand to be able to detect those and deal with them accordingly. Gommeh (talk! sign!) 13:20, 31 May 2026 (UTC)
-
Perhaps a reminder: "Machine translation tools, including LLM-based tools, may be used only to produce close translations of non-English text. Using an LLM to otherwise add or alter material in an article is prohibited by Wikipedia's LLM guidelines." Einsof (talk) 12:16, 31 May 2026 (UTC)
-
Cross-wiki translation is complicated when it comes to attribution and responsibility for source-text integrity. For this reason, best practice is to always start with a very close (word-for-word) translation of the source article, adding nothing and removing nothing, and clearly attributing the source article in the edit summary. This is true regardless of whether the translation is assisted by machine translation tools. Any further revision beyond a direct translation of what the source article says should happen in additional, subsequent edits, so attribution and responsibility remains clear. If LLMs are used in that first step, WP:LLMTRANSLATE imposes additional verification requirements. LLMs cannot be used at all for subsequent revision except for the narrow exceptions permitted by WP:NOLLM. Maybe the right place for clarification would be upstream of WP:LLMTRANSLATE by clarifying the expectations for attribution and responsibility in WP:TRANSLATE? -- LWG talk (VOPOV) 15:48, 31 May 2026 (UTC)
-
-
- I think that we could attempt to solve this problem by merging WP:LLMTRANSLATE into WP:LLM. At this point, I struggle to see the benefit of having a separate page for translation. Yours, &c. RGloucester — ☎ 22:16, 31 May 2026 (UTC)
-
-
A recent AI noticeboard discussion has brought to my attention that Google Translate has recently changed its "Advanced" model (described as
"Improved accuracy, built with Gemini"
) to make even more extensive use of Google's Gemini LLM than it used to. The model selector only appears when a source langage is specified instead of "Detect language".
In some cases, Google Translate's "Advanced" model now adds Markdown and extra em dashes to the original text. For example, the lead section and first subsection of the current revision of the "Chaniers" article from the French Wikipedia have the following text (see page history for attribution):
|
Lead section and first subection of the current revision of the "Chaniers" article from the French Wikipedia
|
|---|
|
Chaniers est une commune du Sud-Ouest de la France, située dans le département de la Charente-Maritime (région Nouvelle-Aquitaine). Ses habitants sont appelés les Chagnolais et Chagnolaises[1]. Si Chaniers est parfois surnommée la commune aux cent villages, elle bénéficie d'un certain nombre d'atouts qui lui permettent d'en faire une commune attractive aux portes de Saintes. Bordée par la Charente, sur sa rive droite, Chaniers est devenue une commune suburbaine particulièrement recherchée, étant de plus située dans la première couronne résidentielle de l'aire urbaine de Saintes. Géographie Localisation et accès La commune de Chaniers se situe dans le centre-est du département de la Charente-Maritime, en région Nouvelle-Aquitaine, dans l'ancienne province de Saintonge. Appartenant au Midi atlantique[2], au cœur de l'arc atlantique, elle peut être rattachée à deux grands ensembles géographiques, le Grand Ouest français et le Grand Sud-Ouest français. La commune de Chaniers est entièrement située sur la rive droite de la Charente, à environ 6 km à l'est de Saintes et à 20 km à l'ouest de Cognac. Cette commune fut longtemps la plus importante du canton de Saintes-Est, canton créé en 1985. Malgré son poids démographique, elle n'avait pas le statut de chef-lieu de canton. En 2015, la création du canton de Chaniers lui permet d'occuper le rôle de bureau centralisateur (c'est-à-dire de chef-lieu). La commune est traversée d'ouest en est par la route départementale 24 (avenue des Deux-Charentes, puis avenue Charles-de-Gaulle dans le centre), qui est bordée par la voie ferrée Saintes-Angoulême (et Saintes-Bordeaux), sans arrêt à Chaniers (les trains du TER Nouvelle-Aquitaine de la ligne Saintes-Angoulême desservent la gare de Beillant, à Saint-Sever-de-Saintonge, à quatre kilomètres au sud-est du bourg central de Chaniers). La D 24 entre à Saintes par les Arcivaux. La route nationale 141 entre Angoulême et Saintes, maillon occidental de la route Centre-Europe Atlantique, qui rejoint la rocade de Saintes et donne sur l'avenue Jourdan, traverse la commune au nord. Chaniers dispose du dernier bac motorisé encore en service sur la Charente, qui permet d'accéder à la commune de Courcoury au sud. Le bourg central, situé près du fleuve, s'organise autour de la place Saint-Pierre où se trouve l'église, et autour des rues Aliénor-d'Aquitaine et Saint-Antoine. La mairie, la salle des fêtes et la médiathèque occupent la place Jean-Pourcelet (du nom d'un maire de Chaniers). La place du Communal, sur la rive nord de la Charente, est bordée à l'ouest par une peupleraie, et à l'est par un camping. Au XXe siècle, l'urbanisation a progressé le long de la rue des Sables vers l'ouest, et a surtout progressé au nord de la voie ferrée, où ont été construits de nombreux lotissements, l'école et le bureau de poste. |
Here is a side-by-side comparison of the Google Translate's "Classic" (also known as "Basic") and "Advanced" translations of the above text into English, obtained by pasting the text into the Google Translate website:
|
English translation outputs from Google Translate website (emphasis added)
|
||||
|---|---|---|---|---|
|
The "Advanced" model is selected by default in the Google Translate website and mobile app, although your most recent model selection is remembered. However, if you select "Detect language" as the source language, which is the default option, Google Translate always uses the "Advanced" model with no option to select the "Classic" ("Basic") model. — Newslinger talk 11:30, 25 September 2026 (UTC)
-
The model selector only appears when a source langage is specified instead of "Detect language".
-
Where is this selector on the Google Translate website? I can't find it. ‑‑gurkubondinn 11:42, 25 September 2026 (UTC)
-
Someone shared a screenshot of the website's model selector in this GitHub comment. On Google Translate's mobile website, it's also at the bottom-right corner of the text input box. — Newslinger talk 12:22, 25 September 2026 (UTC)
-
That selector box does not show up for me for some reason. ‑‑gurkubondinn 12:27, 25 September 2026 (UTC)
-
I'm not sure what's happening. Maybe try opening the site in a private browsing window or another web browser and then clicking another language at the top left? — Newslinger talk 12:31, 25 September 2026 (UTC)
- Hm yeah I get it in a private browsing session, not logged into a google account. Maybe it's because I'm logged into an workspace account.. wonder which Google Translate version that is using.. ‑‑gurkubondinn 13:29, 25 September 2026 (UTC)
-
I'm not sure what's happening. Maybe try opening the site in a private browsing window or another web browser and then clicking another language at the top left? — Newslinger talk 12:31, 25 September 2026 (UTC)
-
That selector box does not show up for me for some reason. ‑‑gurkubondinn 12:27, 25 September 2026 (UTC)
-
Someone shared a screenshot of the website's model selector in this GitHub comment. On Google Translate's mobile website, it's also at the bottom-right corner of the text input box. — Newslinger talk 12:22, 25 September 2026 (UTC)
- Thanks for sharing this. I noticed this week that it had started adding markdown in answers but hadn’t had the time to dig into it yet. Ugh. Suðurhafsljósæta (talk) 12:13, 25 September 2026 (UTC)
Laundering LLM-generated content through translation
editTo date, I have encountered three instances of editors using an LLM to generate content on another language edition of Wikipedia and then using an LLM to translate it to English, before claiming that the English translation is "LLM-translated" and allowed per WP:LLMT.
While English LLM translations of non-English LLM-generated articles are technically "LLM-translated", the use of such translations is against the spirit of the WP:LLM guideline, as these translations retain all of the issues associated with the originally LLM-generated content. Using WP:LLMT as a loophole to submit LLM-generated content in this way is a form of gaming the system.
To make it absolutely clear that such translations are unacceptable, I propose adding a fifth bullet point to the list of requirements in WP:LLMT:
You are reasonably certain that the origin language article is not LLM-generated
(This proposed point does not have to be the final entry in the list, which I believe should be reserved for the attribution requirement.) — Newslinger talk 15:44, 3 October 2026 (UTC)
-
Support.
Only have a minor suggestion, to replace origin language with source languagefor consistency. ‑‑gurkubondinn 16:12, 3 October 2026 (UTC)-
Bullet point #3 already uses
"origin language article"
, but I would support any equivalent phrasing as long as it is used consistently. — Newslinger talk 16:17, 3 October 2026 (UTC)- You're right. No suggestions then! ‑‑gurkubondinn 16:22, 3 October 2026 (UTC)
-
Bullet point #3 already uses
- Support, good idea (and I assume uncontroversial?). Tbh this guideline is a big pain for cleanup, I know it saves responsible translators a lot of time but people appear to frequently publish LLM translations without following this, and at a very high rate, and you need to do spotchecks for WP:V to prove they don't adhere to this. OTOH I've seen some editors strictly follow this, but it's difficult to gauge what's more common. There's also the argument that what's the point of allowing LLM translations when readers can just translate other wikis' articles using the LLM-powered translator built into their browser. Idk Kowal2701 (talk, contribs) 16:25, 3 October 2026 (UTC)
- Support, thank you for proposing this. Suðurhafsljósæta (talk) 06:17, 6 October 2026 (UTC)
Implemented in Special:Diff/1379860537. I placed the new bullet point in the #2 position, as it is something that should be checked after the editor considers their own language ability (#1) and before they start the translation and revision process (#3). — Newslinger talk 08:43, 12 October 2026 (UTC)
Questions regarding presumptive removal and WP:LLMT
editI posted my questions regarding applicability of presumptive removal to contents based on LLM-assisted translation at Wikipedia_talk:Presumptive removal of AI-generated content#Questions:_Presumptive_removal_and_LLM-assisted_translations_(WP:LLMT). Feedback would be appreciated. Zhenqinli (talk) 04:28, 14 October 2026 (UTC)
Editors' familiarity with the topic and its relevance here
editI had a shower thought recently: If an editor is very familiar and knowledgeable about a certain topic area and is engaging in LLM-assisted translation, they can likely verify the accuracy of some information based on their knowledge of the subject area, even if their command of the source language is more shaky. If this is the case, how and to what extent does this guideline apply?
For instance, say I am a big Pokémon fan, and that I've played all the games and am deeply familiar with the lore, but I don't know enough Japanese to not rely on Google or ChatGPT to translate the source into English. One of the main aspects of this guideline is to prevent AI hallucinations from seeping into articles. If there was a Japanese-language source covering the topic in detail, would such an editor be able to detect a hallucination or other translation error based on their own knowledge of the subject area? Should we add something clarifying whether the guideline allows for this? Interested in hearing others' thoughts here. Gommeh (talk 🎮 sign) 14:20, 14 October 2026 (UTC)
- Hm. I think it's relevant here that WP:LLMTRANSLATE is not about translating sources, but rather about translating other Wikipedia articles. It's my understanding that using machine translation to read a source, and then writing an article in your own words, is already considered acceptable subject to relevant "competence is required" guardrails. When translating articles, WP:MACHINE still applies even if hallucinations are removed as a possible problem; hallucinations are not the only reason that a machine translation is worse than nothing unless someone with relevant language skills has reviewed it. So for someone with subject expertise but not language expertise, I think the better approach would be to use the sources from the other wiki's article directly to write a new article, working carefully. ~ le 🌸 valyn (talk) 22:09, 16 October 2026 (UTC)
- Not a conclusion but just an observation:
- I was reviewing a (probably LLM) article about a Japanese magazine. It cited a source as saying that the Imperial office had demanded that this magazine retract something. I machine-translated the source, and from the machine translation it did not sound like a demand to retract but like a polite request to correct. But--I don't speak Japanese beyond a handful of words, but I did a Japanese martial art for a while and learned that Japanese politeness is quite different from American politeness. (As a splendid example, we learned the word for "yes" on day 1 and used it constantly. But in 15 years I never learned the word for "no": there were workarounds, often nonverbal.) So...was this a preemptory demand couched in Japanese politeness? Or an everyday request for a correction?
- This has left me more wary of evaluating machine translated sources. M kuhner (talk) 19:01, 21 October 2026 (UTC)
RFCBEFORE
editHi, please see WT:AIC#LLM exemption for translation, trying to workshop the options for an RfC on changing or repealing WP:LLMTRANSLATE, all input welcome Kowal2701 (talk, contribs) 18:25, 21 October 2026 (UTC)
Machine translators that do not use AI
editI used to rely on Google Translate in the past to do translations for articles, but now they've gone and started integrating Gemini into Google Translate pretty extensively, which makes me a little hesitant to use it. That being said, does anyone know of any good machine translation tools that do not use LLMs (similar to how Google Translate used to work)? 🎮Gommeh (📖/💬) 20:10, 2 November 2026 (UTC)