Pginer-WMF

Pginer-WMF

Previous discussion was archived at User talk:Pginer-WMF/Archive 1 on 10 July 2015.

Please help me

I thought the twitter log belonged to Pginer for wall interfacing of travel, categories; emergency device, or just summary talk? Kathi

https://phabricator.wikimedia.org/T102460 NehalDaveND (talk) 05:44, 13 July 2015 (UTC)

Interfacing

I have a hole in the wall, made it the other day. I have not had phone, don't do banking with one; others might and use them to steal. Notify the manager of the device? They would like to disable emergency communication for (by marraige) themselves, in my house... 68.7.244.2 (talk) 09:32, 16 July 2016 (UTC)

No puedo acceder al traductor de artículos

Buenos tardes, Pau.

Desde ayer no me aparece la opción para poder utilizar el traductor de artículos en la pestaña "Contribuciones". Tampoco la encuentro en la lista de utilidades en "beta". No sé si puede tener algo que ver con que el contador de traducciones haya superado el número mil (es una hipótesis bastante esotérica... pero no se me ocurre otra cosa).

Tampoco he encontrado en internet referencias a este problema. ¿El servicio está temporalmente interrumpido por cuestiones de mantenimiento?

Agradecería una respuesta que pudiera solucionar mi actual situación de desconcierto...

Un cordial saludo:

Wiki LIC (¿Aquí cómo demonios se firma?) Wiki LIC (talk) 18:48, 20 April 2017 (UTC)

Hola @Wiki LIC,

Como comentas, el servicio está temporalmente interrumpido. Se trata de problemas relacionados con el failover test que los encargados de la infraestructura técnica han llevado a cabo recientemente. Se espera que a lo largo del día de hoy quede resuelto.

Lamentamos el desconcierto. Al no tratarse de un mantenimiento específico de la herramienta de traducción ha sido complicado anticipar los posibles problemas. En cualquier caso, puedes estar al tanto de todo lo relacionado con la herramienta a través de la página de discusión del proyecto y en esta cuenta de twitter.

Un saludo y muchas gracias por tu interés en el proyecto. Pginer-WMF (talk) 08:03, 21 April 2017 (UTC)

Need Help

Ping .. need help .. see

• https://de.wikipedia.org/w/index.php?title=Benutzerin_Diskussion:Itti&diff=prev&oldid=174585840#boah_nu_is_ma_gut_mit_bl%C3%BCmchen,_rollatoren,_schnaps,_und_sonstwas_..._%E2%80%9EWikipedia:Technik/Skin/Beta/ContentTranslation/Checkliste%E2%80%9C_ist_angesagt_;-)
• https://de.wikipedia.org/wiki/Benutzer_Diskussion:Matthiasb#Hattu_G%C3%BCck_oder_Pech_..._%E2%80%9EWikipedia:Technik/Skin/Beta/ContentTranslation/Checkliste%E2%80%9C
• Talk:Content translation

Cheers Ｔｏｍ (talk) 19:07, 3 March 2018 (UTC)

Hello

I want to use Universal Language selector to implement in my wiki works, how i can do it? Thank you very much! Naturista2018 (talk) 10:03, 13 June 2018 (UTC)

Hi @Naturista2018,

The project page for Universal Language Selector (ULS) includes details about the product, if you are looking for technical details the extension page can be useful. To configure multilingual wikis, a package of useful extensions named MLEB can be also of interest. Some of the libraries used by the ULS, are also available as javascript libraries to be used in any web project (wiki or not). These pages have an associated talk page where you can share specific questions and get additional information.

I hope this is useful. Pginer-WMF (talk) 14:12, 19 July 2018 (UTC)

Complaint

Hello, I would like to request the removal of machine translation feature in Content Translation only for the Indonesian Wikipedia. I've complained here two times before about the horrendous quality of Yandex Translate. Since then, nothing has changed and more and more people are making articles using Yandex Translate without any adjustment. This results in me deleting dozens of articles, and this is not good for our community. Look at this: https://id.wikipedia.org/w/index.php?diff=14505397&oldid=14505388&title=Pembicaraan_Pengguna:Febri_muhnas As I have predicted, someone will eventually come and say "then why did you provide for such feature in Content Translation?" Please, please, please, please, please, we can't put up with this Yandex nonsense anymore, so could you please kindly remove or disable it from the Indonesian Wikipedia? Thank you. Danu Widjajanto (talk) 07:49, 29 November 2018 (UTC)

Thanks for sharing your feedback, @Mimihitam.

I'm sorry to hear that the machine translation support provided is causing additional clean-up work for the Indonesian community. We have been making improvements in different areas that are relevant for this. Although those improvements are not visible at the moment, they will become visible soon.

Currently we are working on a new version of Content translation. The new version provides new mechanisms and more control to avoid machine translation to be left unreviewed: warning when there is too much unmodified text at a paragraph level so editors know which parts need review, a category for keeping track of those articles published despite the warning (this is the tracking category for Indonesian), and prevent translations from publishing when the amount of unmodified machine translation is really high.

We think that these mechanisms are a better option than disabling machine translation, since they provide access the tools to those users that use them properly, while preventing others from creating low-quality translations. We can adjust the thresholds, setting the percentage of unreviewed machine translation allowed in each case, but we need the community to be able to use the services and provide feedback for that.

The new version of Content Translation will become the default at the end of December. I'd propose as the next steps to evaluate if the problems persist with the new version, and increase the thresholds if there are still problems. Meanwhile we'll keep an eye on the Content translation statistics for Indonesian to keep track of the amount of deleted translations. For example, last week there were 3 deleted translations of 119 articles created with Content translation. This week the deletion rate seems to have increased so far to about 8% (90 published, 8 deleted) which we want to improve but does not look alarming.

In addition, we are always exploring ways to improve the machine translation support by integrating better services, and your feedback about the translation quality is very helpful for us. Apart from adding new services, using the existing ones also helps them to improve since user corrections made to the initial machine translation are exposed through a public API where anyone (including Yandex) can access them to improve their services or create new ones.

Thanks! Pginer-WMF (talk) 10:31, 29 November 2018 (UTC)

Unable to work on current translation, page keeps loading source article

Hi,

can you look the topic “Unable to work on current translation, page keeps loading source article” please? Many people have this problem.

Thanks:) Lzcjames (talk) 23:12, 5 June 2019 (UTC)

Thanks for pinging, I provided a reply and triaged the associated ticket. We'll investigate further the issue. Pginer-WMF (talk) 10:45, 6 June 2019 (UTC)

Une étoile pour vous !

<figure-inline></figure-inline>	L’étoile originale
	Merci DRIS92 (talk) 04:00, 30 June 2019 (UTC)

Request or question about the "Talk: Content translation" specification.

(English)

Request or question about the "Talk: Content translation" specification.

Hello Pginer-WMF !!!

I feel Talk:Content translation is difficult to use.

That's because the user interface of this page is different from the normal talk page, as you know.

There are several points that make it difficult to use, but I will write only one in this message.

It turns out that each section was split on a separate topic page, and was responded to by my post because it wasn't loaded into Talk: Content translation in a relatively short time. It is difficult.

For example, the reply that you wrote at 10:52, 20 March 2020 in Topic:Viqzu45sfzi3cdr4 is not displayed in Talk: Content translation even though it has not been a week yet, and I recently notice that you were responding when I checked my post history.

A similar mechanism is used in ja:Wikipedia:井戸端 etc., but it is displayed for a longer time.

Therefore, "request" is to make it displayed for a longer time.

Also, if there is another place to make this suggestion, where is it? That is the "question."

Please answer me.

Thank you !!!

HaussmannSaintLazare (talk) 15:42, 25 March 2020 (UTC)

(Original in Japanese)

「Talk:Content translation」の仕様についての要望あるいは質問です

Hello Pginer-WMF !!!

私は、Talk:Content translationは非常に使いにくいなと感じています。

それは、このページのユーザーインターフェースがご存じの通り通常のtalkページと異なっているからです。

使いにくいなと感じる点は、何点かあるのですが、このメッセージでは一つだけ書きます。

それは、それぞれのセクションが別のトピックページに分けられていて、しかも比較的短い時間でTalk:Content translationへの読み込みがされなくなるために、自分の投稿に対する応答があったことが分かりにくいことです。

例えば10:52, 20 March 2020にあなたがTalk:Content translation/2020/03#Proposal for the "publish" featureに書かれた返事は、まだ1週間も経過していないのも関わらずTalk:Content translationで表示されず、私は最近自分の投稿履歴を確認するまであなたが返答していることに気づきませんでした。

ja:Wikipedia:井戸端などでも同様の仕組みが使われていますが、もう少し長い期間表示されるようになっています。

そこで、もう少し長い期間表示されるようにしてほしいというのが「要望」です。

また、この提案をする場所が他にあるなら、それはどこですかというのが「質問」です。 よろしくご回答ください。

Thank you !!!

HaussmannSaintLazare (talk) 15:42, 25 March 2020 (UTC)

Thanks for the input, @HaussmannSaintLazare.

For Content translation discussion we enabled Structured Discussions. It is true that it is different from regular talk pages, but we think it also has some advantages, and we have observed higher participation from less experienced users. Some aspects that can be useful when using this system:

• You can subscribe (star) individual topics to get notifications when those have new replies. Unlike regular talk pages where you can only star the whole page.
• A filter (in the top-right area above the discussions) allows to sort the conversations to show at the top either the new ones or those with new activity.

I hope this helps. Pginer-WMF (talk) 08:57, 27 March 2020 (UTC)

Unable to publish translated page. Categories are hidden to be removed

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.

---

I have problem with publishing "Nancy Drew" translated from English to Vietnamese (tiếng Việt), posted on Talk Content Translation

I follow your instruction in Talk: Content Translation "remove the categories that the user added to the translation and try to publish again." but now, no category is shown for adding/removing, maybe its error loading this part, isn't it? (Without knowing it may troubled, I had added some more categories before)

How do I proceed to publish it?

Thanks& Regards Lcsnes (talk) 04:02, 26 March 2020 (UTC)

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

question about Pavanaja's report

15:04, 31 March 2020 (UTC)

Hello Pginer-WMF !!!

I have a question about User:Pavanaja's report.

Pavanaja reported in Talk:Content translation/2020/03#h-Collaborative_translation_a.k.a._multiple_users_translating_same_article-2020-03-22T04:58:00.000Z that when trying to do a new translation in Content Translation, the translation could not be started if another user had already started the same translation.

I did the same test and found the same symptoms.

I asked a question because I felt wondering at that time.

During the follow-up test, the message "Critical error: Content translation failed to load due to internal error." was displayed and translation could not be started.

However, this message does not tell whether the translation could not be started due to a bug in the content translation tool or the specification of the content translation tool.

So, please tell me whether this symptom is due to a bug or a spec.

Thank you !!!

--HaussmannSaintLazare (talk) 15:04, 31 March 2020 (UTC)

(original in Japanese)

Hello Pginer-WMF !!!

User:Pavanajaのレポートについての質問です。

PavanajaはTalk:Content translation/2020/03#h-Collaborative_translation_a.k.a._multiple_users_translating_same_article-2020-03-22T04:58:00.000Zで、コンテンツ翻訳で新しい翻訳をしようとしたときに、他の利用者が既に同じ翻訳を開始していると翻訳を開始できないことを報告しました。

私も、追試験をしてみたところ、同じ症状が発生しました。

その際に疑問に感じたことがあるので質問します。

追試験をした際に、「Critical error: Content translation failed to load due to internal error.」というメッセージが表示されて翻訳を開始することができませんでした。

しかし、このメッセージでは、翻訳を開始できないのがコンテンツ翻訳ツールのバグによるものなのか、それともコンテンツ翻訳ツールの仕様によるものなのかが分かりません。 そこで、この症状がバグによるものなのか仕様によるものなのかをおお教えください。

Thank you !!! HaussmannSaintLazare (talk) 15:04, 31 March 2020 (UTC)

question about bug report Topic:Virkxk0741k38j8l

Hello Pginer-WMF !!!

This is a question about bug report(Talk:Content translation/2020/03#bug report - originally called "Topic:Virkxk0741k38j8l") which I reported on 16:04, 17 March 2020 (UTC).

How is Talk:Content translation/2020/03#bug report handled in Wikimedia Phabricator now ? If the process has already started, please write it into Talk:Content translation/2020/03#bug report. If the process has not been started yet, please write the reason or situation in Talk:Content translation/2020/03#bug report.

Thnak you !!!

--HaussmannSaintLazare (talk) 08:36, 3 April 2020 (UTC)

Hi!

If I understand correctly, the problem is that Japanese Wikipedia abuse filter number 13 triggers a warning in Content translation.

It seems (based on what I understood form automatic translation) that filter 13 is intended to warn about short articles being created. Content translation tries to check early the contents against abuse filters for each paragraph in order to surface issues as early as possible and be able to tell where the problems are. This approach is beneficial in many cases, for example the source article may have a youtube link which is ok with the source wiki but is prevented in the target one. By warning early and showing the specific paragraph we can help the user know where to look for such link and fix it. However, some abuse filters expect to evaluate the whole article, and checking just a paragraph can result in a false positive. In your case, the filter considers that the evaluated text is too short for an article, but it was actually just a paragraph. Unfortunately, the edit filter infrastructure does not allow to differentiate both kinds of filters.

I'll bring this to discuss with the team again to see if there is something actionable we can do. to improve the situation.

Thanks! Pginer-WMF (talk) 09:28, 3 April 2020 (UTC)

Hello Pginer-WMF !!!

I understand how the error occurs. I can avoid this error.

I will write this error and its workaround in Content translation/Documentation/FAQ#Please write solution to the "supposed" bugs.

However, it seems that resolving this error requires coordination with the filter team.

Don't hesitate to work with the filter team.

Thank you !!!

--HaussmannSaintLazare (talk) 02:44, 4 April 2020 (UTC)

A cupcake for you!

Charminku (talk) 14:41, 4 April 2020 (UTC)

A cupcake for you!

<figure-inline></figure-inline>

Best Wishes My side.... From India !!! Charminku (talk) 14:41, 4 April 2020 (UTC)

About the specifications of MediaWiki

Hello Pginer-WMF !!!

Recently I posted my opinion on Talk:Communication#About the specifications of MediaWiki about how to decide the specifications of MediaWiki.

So, please write your opinion.

Thank you !!!

--HaussmannSaintLazare (talk) 07:12, 11 May 2020 (UTC)

Please join the discussion on my proposal

Hello Pginer-WMF !!!

I have made a proposal related to the phab:T215403 you are currently participating in. So please join the discussion on my proposal.

Thank you !!!

11:03, 19 May 2020 HaussmannSaintLazare (talk) 11:03, 19 May 2020 (UTC)

Hello Pginer-WMF !!!

Please write your impressions about my proposal that I introduced the other day.

Thank you.

HaussmannSaintLazare (talk) 11:32, 23 May 2020 (UTC)

A barnstar for you!

<figure-inline></figure-inline>	The Technical Barnstar
	Many thanks for implementing https://phabricator.wikimedia.org/T199523 ! I've tested yue and it's great!

RoyZuo (talk) 19:01, 14 August 2020 (UTC)

আপনার জন্য একটি পদক!

<figure-inline></figure-inline>	রোজেত্তা পদক
	For working at Content Translation Project.

RIT RAJARSHI (talk) 19:44, 13 September 2020 (UTC)

About the enablement of Section translation in Wikipedia

Hello Pginer, i have a question, ¿when Section translation could be enabled for Spanish Wikipedia? Thanks. Rodney Araujo (talk) 01:30, 25 February 2021 (UTC)

Thanks @Rodney Araujo for your interest in the tool and your help on the project.

We just enabled Section Translation on Bengali Wikipedia as an early release, and we plan to improve the tool further before considering other wikis. There are several areas of the tool that need improvement and we want to hear from a smaller group of editors first to iterate and make the tool better. So it may still take several weeks until we can move to the next stage.

Hearing about the interest on the tool is very encouraging for us, and it is very useful to know where there are users interested in the tool that can help us make it better. So we'd definitely consider Spanish Wikipedia as we plan for enabling more wikis.

Thanks! Pginer-WMF (talk) 09:31, 25 February 2021 (UTC)

@Pginer-WMF: You can announce and communicate to Spanish Wikipedia community about the Section translation, his features, and deployment on w:es:Wikipedia:Café/Archivo/Noticias/Actual. Thanks. Rodney Araujo (talk) 12:53, 25 February 2021 (UTC)

@Pginer-WMF: Are you going to communicate with Spanish Wikipedia community about Section translation? Rodney Araujo (talk) 22:53, 25 February 2021 (UTC)

Right now the tool is in a very early stage with several important aspects still missing. Once we complete a few cycles of development we'll be doing wider announcements.

Currently we have just announced the enablement on Bengali Wikipedia. Once we get feedback from this community to improve the tool we'll consider expanding (and communicating) to other wikis. Pginer-WMF (talk) 09:42, 26 February 2021 (UTC)

Bonjour, Je vois que la traduction de es à fr est possible. DRIS92 (talk) 08:21, 26 February 2021 (UTC)

Our tools integrate multiple translation services. You can get a list of the services and the supported languages in the documentation. Due to limitations of the test instance for Section Translation, only those languages supported by Apertium, Matxin and OpusMT are available. However, all services will be available when the tool is available on a real wiki. Pginer-WMF (talk) 09:46, 26 February 2021 (UTC)

@Rodney Araujo Section translation is now available on Test Wikipedia. This is a test environment better integrated with our infrastructure, where more machine translation services are available. Thus, you can try the tool using Google translate or Yandex in more languages and without the need to create a separate account. The results are still published in the test instance (not the real wiki) but you can copy the resulting content anywhere else.

I hope this is useful until we enable the tool in more Wikipedias. Pginer-WMF (talk) 11:03, 11 March 2021 (UTC)

Any news?

It has been 2 months. I want to know what's your solution to this, and what progress has been made to address the problem so far? Thank you! Nguyentrongphu (talk) 18:22, 23 March 2021 (UTC)

Hi @Nguyentrongphu. After receiving input from the Vietnamese community we adjusted the limits to the amount of unmodified Machine Translation allowed. I have also created a ticket to explore how to detect copied content out of Content Translation.

Right now the team is focused right now on the mobile support for Section Translation, but the whole area of Machine Translation limits is something we want to focus in the near future. Pginer-WMF (talk) 10:00, 24 March 2021 (UTC)

I just come up with a new idea that would be easier to implement. The current limit right now for Vi Wikipedia is 90%. If unmodified content is higher than 90%, copying is disabled. In other words, one can only copy if they meet the threshold % to publish. I don't think this solution would negatively affect good-faith users, or at least, its benefit outweighs its little inconvenience (one can always manual translate first before trying to copy things). Nguyentrongphu (talk) 10:24, 24 March 2021 (UTC)

Thanks for the suggestion. That's an approach we can consider. There are a couple of aspects that we need to consider in more detail:

• Initial and intermediate states. When adding the first paragraph users will be at a 100% Mt temporarily until they start editing the paragraph. Even users making a good use o the tool would have copying disabled initially which can affect their workflow. To reduce this issue we can apply this limitation only when the translation has already 2 paragraphs added.
• Feedback. Making copying disabled in some cases can result in working intermittently for the user. We may need to provide some feedback to clarify why the copy functionality was not working.

In general I think that including a tag into the copied text is a measure that is less intrusive while it can be effective, but this suggestion is an alternative to consider as part of the exploration. Pginer-WMF (talk) 10:51, 24 March 2021 (UTC)

"Initial and intermediate states. When adding the first paragraph users will be at a 100% Mt temporarily until they start editing the paragraph. Even users making a good use o the tool would have copying disabled initially which can affect their workflow. To reduce this issue we can apply this limitation only when the translation has already 2 paragraphs added." -> Now that I think about it, it's not a good idea because one can bypass it easily by copying each paragraph one by one.

Like I said, a little inconvenience is a good trade-off to prevent abuse. How hard is it really to translate 10% of contents before starting to copy things? Not really hard in my opinion. Nguyentrongphu (talk) 09:12, 25 March 2021 (UTC)

There are pro's and con's in both methods. Tag method is less intrusive, sure but, it also has multiple implications and serious consequences:

First: it leaves wide open for abusers to continue to abuse the CT system.

Second: it continues to place heavy work load on patrollers in recent changes or new pages. It's not clear at what % they start to cheat (copy and publish right away); for example, at 100%, 94%, or 99%...? It's very time consuming to determine this; one has to read each individual article to determine how good is the translation. It becomes impossible to do when many people are abusing this. Vi Wikipedia has caught many different users that have been abusing this loophole for years. The reason is that people didn't notice this loophole for years until recently. On average, each user has 5k of badly translated articles. Let's say there are 10 users like that. It would mean around 50k of badly translated articles! Nguyentrongphu (talk) 11:19, 24 March 2021 (UTC)

I agree there are pros and cons with each approach, and I think it is important to surface them as part of the exploration. Thanks for sharing your thoughts on this.

Regarding your first point, any approach is about adding barriers to make it hard for users to do the wrong thing, but there may always be a workaround. When the barrier is based on a generic mechanism that others may also use, it is more likely to have also generic solutions available such as this browser extension. However, including a more specific tag is something that requires a specific effort to detect.

Regarding your second point, the less intrusive solution allows to be more flexible about the percentage to catch. Maybe any content copied can result in the page being added to a category but those with higher percentages of unmodified MT are blocked directly.

This is a complicated space. I think we need to explore different options in detail. Pginer-WMF (talk) 12:06, 24 March 2021 (UTC)

I doubt many people know about that browser extension. Sure, there are always ways to cheat regardless of barrier. However, a barrier is good enough when it can stop most of the abusers. We (Vi Wikipedia) can deal with 1 or 2 remaining abusers that find a way to cheat the barrier. Currently, the barrier we have is not sufficient, so we need a better barrier.

"Regarding your second point, the less intrusive solution allows to be more flexible about the percentage to catch. Maybe any content copied can result in the page being added to a category but those with higher percentages of unmodified MT are blocked directly." -> I like this idea. However, I'm not sure how feasible this is (technical aspect). Also, a tag is sufficient, no need to add to a category. And if this method is too hard or impossible in technical aspect, my method is a sound alternative. Nguyentrongphu (talk) 13:43, 24 March 2021 (UTC)

Feedback: you guys can put a "warning" somewhere in CT, easy to see, saying: "you have to translate at least 10% contents before able to copy". Nguyentrongphu (talk) 11:24, 24 March 2021 (UTC)

communication issues

Hi, as the listed product manager for the Wikimedia Language team I would like to make an complaint. UOzurumba has several times now tried to get community permission for deployments by posting on user pages. This is in clear violation of WMFs own policy at wikitech:Wikimedia site requests and meta:Requesting wiki configuration changes. The proper way is to use an Village pump of each project in question. Snævar (talk) 17:34, 14 April 2022 (UTC)

Thanks for flagging this @Snævar. While most of the communications were done through the village pumps, there were some problems in a few cases resulting in the publication on the wrong place. UOzurumba is reviewing those and will publish then in the corresponding Village pumps.

Navigating a cross-language environment can be often a complex task. Thanks for understanding, and for helping catch these glitches. Pginer-WMF (talk) 13:24, 20 April 2022 (UTC)

Content Translation

Hi, I'm mohamed from arabic content. report bugs in the (Content Translation), let me assign you the task of fixing them, please:

- First Problem: the problem is that diacritics are isolated with spaces that are not combined with the word, eg (مرحبًا كيف ، حالك ؟) while the correct ones should be (مرحبًا، كيف حالك؟). These are the diacritics and letters that must be fixed: (( . ، ؛ : ؟ ! و () {} [] /\ ~ - ٪ % × + ÷ $)) ...I don't know if there are other signs!.

- The second problem: when a translated text is shown to me using the "Content translation" tool, some words will appear that lead to links, and among these links there are links that lead to arabic articles that have already been translated into arabic, and links that lead to articles that have not been translated into Arabic After that, it will appear in red. therefore, I ask to develop the tool and make it automatically put such links to non-translated articles in this template Template:Interlanguage link. Mohmad Abdul sahib Mohmad Abdul sahib 22:36, 27 April 2022 (UTC)

Thanks for the feedback, @Mohmad Abdul sahib.

Regarding the first issue, is the problem occurring for the initial machine translation provided or when typing contents you try to write directly? If it is about the machine translation, is it occurring when using Google translate or also with other services?

Regarding the second request, we need to explore how to better support the practices of different communities. One challenge with adding the interlanguage links template is that it is available in 89 languages from the 300+ the tool supports. In addition, we need to consider the additional backlog of links to update that is generated once the corresponding articles are created. Pginer-WMF (talk) 10:43, 29 April 2022 (UTC)

Pginer-WMF

1. The problem occurs inside the tool, when the tool does an automatic translation, I have recorded a video for you documenting the problem for you to understand well: here
2. Yes, the problem occurs with Google Translate and Microsoft Translate. I don't know what other types of translation services this tool supports, so you should check it out, as most likely the same problem will happen with those other types of translation services.

• Regarding the template: There is no need to update the link name, if an article has been created with a title different from the link name.
  • That is, the link name will remain and will not be subject to automatic updating, even if its name is different from the title of the article that will be created.
  • This is because usually, when referring to an article (even when this template is not used)'' the link name is often syntaxed differently than the article title. ‏
• If there are other matters that need to be considered, I think it is better to launch the template update in the tool, and then post an advertisement inside the tool, where the advertisement appears within the tool in the form of a notification to any user in all languages ​​to report any errors regarding the update of this template.thanks!. Mohmad Abdul sahib 19:43, 10 June 2022 (UTC)

I need help

I need your help Surcox (talk) 17:49, 11 August 2024 (UTC)