Project:Village Pump/Flow/2022/07

This page is only for discussing issues related to MediaWiki.org website.

To get help with MediaWiki software, ask on Project:Support desk.

VisualEditor: menu item 'Cite V' never appears

When connected on → https://test2.wikipedia.org/wiki/American_English?action=edit for example, tab Cite (fr:'sourcer') is present when editing the test page with VE. IT calls the Citoid menu.

On the other side on Mediawiki menu 'Cite V' is not present for example in → https://www.mediawiki.org/w/index.php?title=Help:VisualEditor/User_guide/Citation_templates&action=edit

BUT the VE Help on MediaWiki describes the existence of this Cite menu (Cite with V) on page → https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide/Citation_templates#Re-using_an_existing_footnote

Inever see this menu; either Citoid is present and it corresponds to the 'button' case, or Citoid is not present and there is no menu 'Cite V' to describe!

I think this is to be clarified and section 'Cite V' must be deleted reinforcing informations on button 'Cite'. Advice @Matma Rex @Whatamidoing (WMF)? Thanks.

Christian 🇫🇷 FR (talk) 20:08, 1 July 2022 (UTC)

The mysterious dropdown is still sometimes used! For example, I was able to find it here: https://en.wikibooks.org/w/index.php?title=User:Matma_Rex/sandbox&veaction=edit

I see that another part of the guide, Help:VisualEditor/User guide#Editing references, describes both systems (although it probably should describe the Citoid one with the button primarily, and only mention the other ones).

Here on MediaWiki.org, the items that would normally appear in the  "Cite" dropdown are instead moved to the "Insert" dropdown, since citations are rarely used. This doesn't seem to be described anywhere in the guide.

For better or worse, all three of these are currently supported…

To summarize:

Location of citation features

	"Cite" button	"Cite" dropdown	"Insert" dropdown
Used when	Citoid is installed and configured: Citoid/Enabling Citoid on your wiki	Citoid is not installed or not configured	Citoid is not installed or not configured, and configuration setting $wgCiteVisualEditorOtherGroup is true
Example	https://en.wikipedia.org/w/index.php?title=User:Matma_Rex/sandbox&veaction=edit	https://en.wikibooks.org/w/index.php?title=User:Matma_Rex/sandbox&veaction=edit	https://www.mediawiki.org/w/index.php?title=User:Matma_Rex/sandbox&veaction=edit
Looks like			(Looks like there aren't any screenshots of this on Commons)
Looks like (expanded)		(depending on whether any citation templates are configured)

Matma Rex (talk) 19:12, 4 July 2022 (UTC)

Thans for all these precisions.

This confirms I dont find it on MediaWiki. But

Question : is it logic to describe here on Mediawiki a function available on en.wikibooks ? ...

On the other side Mediawiki as we see, holds the Help pages of VisualEditor to be as detailed as rich as possible. These pages are then translated to other languages. Once translated in FR, I was surprised to see that the FR pages already exists on https://fr.wikipedia.org/wiki/Aide:%C3%89diteurVisuel which then duplicates the work of Help:VisualEditor/User guide/fr on Mediawiki.

Question : No good to duplicate : what is then the reference page ? (on which host the functionalities/extensions must be documented ? I have seen no official declaration.

Christian 🇫🇷 FR (talk) 19:35, 6 July 2022 (UTC)

MediaWiki's Help: pages are meant to cover (almost) everything for (almost) everyone. It's "help for the whole world", not "help for this single wiki". There are even help pages here for software that isn't available on any WMF-hosted wiki. These pages get copied and adapted to wikis all over the world.

One of my struggles with Help:VisualEditor/User guide is that there are at least three different configuration options. How do you show the information this reader needs, when you don't know which system the reader is trying to figure out? It began to feel like a "choose your own adventure" book (livre-jeu). I never found a good solution. Whatamidoing (WMF) (talk) 21:20, 8 July 2022 (UTC)

VisualEditor : translation conflict definition for 'Reuse' wording

Page https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide/Citation_templates#Re-using_an_existing_footnote speaks about item 'Re-use' using the translation of 'cite-ve-dialog-reference-useexisting-tool' which is perfect on the EN page as 'Re-use' and coherent with what the menu displays.

On https://translatewiki.net/w/i.php?title=MediaWiki:Cite-ve-dialog-reference-useexisting-tool/fr&diff=prev&oldid=10006724 the FR translation was initially 'Réutiliser' and after some fights of translators has become 'déjà présente' which brings a non sens in our VE help page in Help:VisualEditor/User guide/Citation templates/fr#Réutiliser une référence existante which has becomes ' Ensuite dans le menu Sourcer, cliquez sur l'élément déjà présente. ' instead of being 'Ensuite dans le menu Sourcer, cliquez sur l'élément Réutiliser.' There is no element "déjà présente" in this VE menu.

Because the FR menu is coherent at execution, my question is rather directed to a developper (@Matma Rex @Whatamidoing (WMF)?) or to someone who can access the code;

Question: which value is used in the code to see the line Re-use of image https://commons.wikimedia.org/wiki/File:VisualEditor_Cite_menu_re-use.png ?

.... I dont think it was 'cite-ve-dialog-reference-useexisting-tool'. We 'll align the help page on the parameter.

Here are some hits for comparison :

{{int|cite-ve-dialog-reference-useexisting-tool/fr}} → déjà présente

{{int|cite-ve-dialog-reference-useexisting-tool}} → Re-use

{{int|Citoid-citoiddialog-mode-reuse/fr}} → Réutiliser

{{int|Citoid-citoiddialog-mode-reuse}} → Re-use

Thanks.

Christian 🇫🇷 FR (talk) 21:04, 1 July 2022 (UTC)

Question: which value is used in the code to see the line Re-use of image https://commons.wikimedia.org/wiki/File:VisualEditor_Cite_menu_re-use.png ?

The message used for this is: cite-ve-dialog-reference-useexisting-tool

Unfortunately, this message is also used as part of the phrase "Re-use reference" when citations are in the "Insert" dropdown (see my other answer at Project:Village Pump/Flow/2022/07#h-VisualEditor:_menu_item_'Cite_V'_never_appears-2022-07-01T20:08:00.000Z). In this case, the text is composed of cite-ve-othergroup-item + cite-ve-dialog-reference-useexisting-tool.

This is probably what is causing the conflict, as it is impossible to translate correctly to fit both contexts in many languages. This problem is reported as T223349.

I suggest optimizing the translation for the first case, where the message is used by itself, as that is used on more projects; and doing the best you can in the other message to make it somewhat understandable (e.g. something like "Reference: Re-use" might work). Matma Rex (talk) 19:24, 4 July 2022 (UTC)

Thanks for all these explainations; i will adopt a neutral form

Christian 🇫🇷 FR (talk) 20:17, 6 July 2022 (UTC)

Comment savoir si Citoid est réellement Enabled dans MediaWIki ?

Dans le User Guide de VE on nous dit que Citoid doit être 'enabled' pour voir le menu Sourcer. Dans Special:Version j'ai la liste des EXTensions 'autres' installées sur MEdiaWIKi. ELLe y est bien, et si je regarde dans Citoid/Where_citoid_is_enabled elle semble activée par contre je ne vois pas SOURcer dans le VE; qui croire ?

Christian 🇫🇷 FR (talk) 09:56, 3 July 2022 (UTC)

@Wladek92

EN: See Special:Version to verify if the extension is installed.

FR: Consultez Special:Version sur votre wiki. 105.111.113.223 (talk) 13:02, 7 July 2022 (UTC)

installed is one thing, enabled another Christian 🇫🇷 FR 🚨 (talk) 13:45, 7 July 2022 (UTC)

Main Page issue on mobile

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.

---

When I load the main page on mobile, the page is blank and the only way to view it is to click Read as wiki page. 105.106.83.188 (talk) 18:41, 5 July 2022 (UTC)

I can confirm this. A link to test directly from desktop: https://www.mediawiki.org/wiki/MediaWiki?useformat=mobile

Isn't this MobileFrontend being MobileFrontend? :-) Ciencia Al Poder (talk) 21:09, 5 July 2022 (UTC)

Actually, I've never seen this behavior except on talk pages... but the Main page is not a talk page. Ciencia Al Poder (talk) 21:19, 5 July 2022 (UTC)

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

Help:Lists

Dears,

please help me to get the best understanding of the message T:127

It says:

Since each special page, like other pages, has a class based on the pagename, one can separately specify for each type whether the lists should be ordered, see User contributions and What links here.

My question is related to the bold part.

Does it mean a page can separately specify ......?

In this case can we say Since each special page, like other pages, has a class based on the pagename, a page can separately specify for each type whether the lists should be ordered, see User contributions and What links here.??

Furthermore, I propose to make this message nicer as follow:

Since each special page, like other pages, has a class based on the pagename, a page can separately specify for each type whether the lists should be ordered. See also User contributions and What links here.

Regards GpieroMW (talk) 12:28, 6 July 2022 (UTC)

No, the pages themselves don’t specify that their lists should be ordered, but users have the ability to do so (e.g. through Special:MyPage/common.css or m:Special:MyPage/global.css), and they can use the class names to limit the styling to specific page(s). Tacsipacsi (talk) 13:16, 7 July 2022 (UTC)

@Tacsipacsi

ok, clear,

Many thanks for your answer.

Regards GpieroMW (talk) 13:46, 7 July 2022 (UTC)

Enabling the 2017 wikitext editor by default

Currently, you have to use the 2017 wikitext editor as a beta feature but I am asking if MediaWiki.org will switch to the 2017 wikitext editor by default because its stable and nice. It also fits with translatable pages. 197.202.25.31 (talk) 18:30, 6 July 2022 (UTC)

Strange request because I have read that the WYSIWYG Visual Editor will become the rule. Invoked reason: less needs to correct the source directly. Points of view welcomed!

Christian 🇫🇷 FR (talk) 18:43, 6 July 2022 (UTC)

I don't think that will happen until phab:T202921 ("Re-design the Editing preferences to make it easier to pick the editing environment that you want to use"). That should happen before phab:T104479, which is AFAICT the nearest ticket to "Move 2017WTE out of Beta Features". Whatamidoing (WMF) (talk) 21:23, 8 July 2022 (UTC)

Page Help:VisualEditor/VE_as_the_main_editor "the visual editor becomes available by default" ... leads me to say that, because it is the opposite way of "switch to the 2017 wikitext editor by default". Thanks to Preferences settings users can get what he wants. Christian 🇫🇷 FR 🚨 (talk) 12:56, 9 July 2022 (UTC)

The language around "default" is complicated. What's "available by default" is different from "the default". Here is my opinion:

• Something that is available by default means you can use it without taking any extra action to enable it.
• "The default" is what happens when you have no choice (e.g., when reverting an edit), or when you take the first/most obvious thing offered to you.

So I would say that the visual editor is already "available by default" at this wiki (you don't have to take any action to have access to it), and that it is "the default" at this wiki for some actions (e.g., editing) but not for others (e.g., reverting and translating). I would also say that the 2010 WikiEditor is "available by default" at this wiki and also "the default" at this wiki for some actions (e.g., reverting). Whatamidoing (WMF) (talk) 19:49, 26 July 2022 (UTC)

Search bug

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.

---

There is a random chance to see unreadable characters while typing in MobileFrontend's search box on certain mobile devices. 105.111.113.223 (talk) 11:00, 7 July 2022 (UTC)

I fixed it by restarting the mobile device. 105.111.113.223 (talk) 12:59, 7 July 2022 (UTC)

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

Help:Extension:Translate/Off-Line Translation

Dears, a very simple question.

In the section Import, I read

The users with correct user rights can use Special:ImportTranslations to upload and import the translations

But the page Special:ImportTranslations contains the following message:

The action you have requested is limited to users in the group: Translation administrators.

So the question is: why a user can export the whole page for an off line translation and then is forbidden to import in so simple way?

Thank for your attention GpieroMW (talk) 14:18, 9 July 2022 (UTC)

Importing a lot of translations can be abused and cause a lot of disruption that is time-consuming to clean up.

The same happens with Special:Export, which allows anyone to export pages easily, but Special:Import is restricted to administrators by default. Ciencia Al Poder (talk) 16:22, 9 July 2022 (UTC)

@Ciencia Al Poder

Thanks again for your kind answer.

Meanwhile, this time I can't say I found a logical standpoint in the answer I got by WMF.

It seems a nosense in my opinion, but perhaps I am wrong.

This answer suggest me that some data is not properly managed. You are right, one can abused and cleaning up is time-consuming.

I can see that since I regularly check Recent Changes and I see how many people are involved in revert version, blocking user, and so on.

But, on the other hand, you have a data that show how many contribution a user did. And how many times one of you has to change or modify something.

So I wonder how you measure the reliability of a user. For instance since my user right is "autoconfirmed" who and using which method this rating has been assigned and valid up to know?

Something in your process should be tuning yet. But this is only my personal opinion.

Nice weekend to everybody

Regards GpieroMW (talk) 16:56, 9 July 2022 (UTC)

Translate: where are located and defined the ID of Special Pages contents ?

For translation of local pages, on page Special:Tags and because it is a system page, how do we retrieve the ID of messages still left in EN and where can they be found to adapt their translation ?

Example: 'Tagged by filter 76 (hist · journaux)' in my FR Special:Tags page version of line 'Potentially problematic translation' is a mix between EN terms and FR ones and need to be FR aligned. Looking for 'Tagged by filter' on translatewiki.net has provided no satisfying results. Thanks.

Christian 🇫🇷 FR (talk) 08:20, 10 July 2022 (UTC)

Click on the "Edit" link next to the "Tagged by filter 76 (hist · journaux)".

Translate {{Tag description}}. Shirayuki (talk) 09:08, 10 July 2022 (UTC)

ok good => this step allows to translate strings "Tagged by filter..."

Christian 🇫🇷 FR (talk) 09:05, 16 July 2022 (UTC)

... no such Edit link on the page ; @Ciencia Al Poder may be not enough rights for me ? Christian 🇫🇷 FR 🚨 (talk) 11:51, 10 July 2022 (UTC)

I see a link pointing to Edit in Special:Tags. Shirayuki (talk) 12:01, 10 July 2022 (UTC)

not here and if i follow yours it says it is protected;

Vous n’avez pas le droit de6v modifier cette page, pour la raison suivante :

Cette page fournit du texte d’interface pour le logiciel sur ce wiki et est protégée pour éviter les abus. Pour ajouter ou modifier des traductions sur tous les wikis, veuillez utiliser translatewiki.net, le projet de régionalisation de MediaWiki.

where to request ? Christian 🇫🇷 FR 🚨 (talk) 12:07, 10 July 2022 (UTC)

Wladek92 asks to translate the "Potentially problematic translation" text, which is placed at MediaWiki:Tag-Potentially problematic translation. Editing MediaWiki:Tag-Potentially problematic translation/fr to provide a French translation requires some special rights. You can put here the translation text and I can create the page with it. Ciencia Al Poder (talk) 09:07, 11 July 2022 (UTC)

Yes nice, and if I go on this MediaWiki:Tag-Pot.... , they say "To add or change translations for all wikis, please use translatewiki.net, the MediaWiki localisation project." So I have wondered why not to rely on translatewiki.net for that ?

If I take the example of tag 'mobile web edit'

I construct key ID => 'MediaWiki:Tag-mobile web edit'

which exists on https://translatewiki.net/wiki/MediaWiki:Tag-mobile_web_edit/fr => 'Modification par le web mobile ' and that I find back under 'Appearance on change lists'

By adding suffix '-description' for the column beside named 'full description of meaning' I construct key ID 'MediaWiki:Tag-mobile web edit-description/fr'

which gives 'Modification effectuée depuis le site web mobile'

This sounds good with what I get. So for a first shot of my concern, I have created => https://translatewiki.net/wiki/MediaWiki:Tag-Potentially_problematic_translation/fr and https://translatewiki.net/wiki/MediaWiki:Tag-Potentially_problematic_translation-description/fr.

We should be able to find a solution with translatewiki.net for all other messages of Special:Tags and all languages.

Now as we know starting from the tag name XXX in Mediawiki, how to access the text MediaWiki:Tag-XXX/xx and the description MediaWiki:Tag-XXX-description/xx on translatewiki, the problem would be to bring back the translated strings. I have not enough knowledge about that, but this action is to be managed. May be the process already exists (?) and simply because the /fr messages were not existing, EN were used as fallback.

Christian 🇫🇷 FR (talk) 10:25, 16 July 2022 (UTC)

I have created Template:Tag-Potentially problematic translation. Shirayuki (talk) 11:16, 11 July 2022 (UTC)

The per-template base seems not really adapted because there is a lot of other untransaled items on this Special:Tags page (about 32 lines are concerned). If my proposal here (here above) with translatewiki.net is pertinent I 'll solve all of them point per point.

Christian 🇫🇷 FR (talk) 10:39, 16 July 2022 (UTC)

While I understand the fanciness of being able to translate the message without edit-interface rights, invoking a template with the #ifexists parser function on a message that can appear potentially thousands of times on Special:RecentChanges or Special:Watchlist, which already have serious performance problems, can probably cause more harm than good Ciencia Al Poder (talk) 20:44, 11 July 2022 (UTC)

So I have created the FR items herebelow on translatewiki.net for missing FR texts and [this topic] they advice me to 1)create the English base (otherwise it's impossible to translate correctly) 2) make it part of a translation project or subproject for some Mediawiki extension 3.appears in the Translate UI.

Question: what is the next step for us ?

MediaWiki:Tag-Added PHP closing tag-description/fr
MediaWiki:Tag-Added PHP closing tag/fr
MediaWiki:Tag-Anonymous updated project status-description/fr
MediaWiki:Tag-Anonymous updated project status/fr
MediaWiki:Tag-Blocked user editing own talk page/fr
MediaWiki:Tag-Emoji-description/fr
MediaWiki:Tag-New user blanking page-description/fr
MediaWiki:Tag-New user blanking page/fr
MediaWiki:Tag-New user editing project page-description/fr
MediaWiki:Tag-New user editing project page/fr
MediaWiki:Tag-OAuth CID: 1188-description/fr
MediaWiki:Tag-OAuth CID: 1261-description/fr
MediaWiki:Tag-OAuth CID: 1352-description/fr
MediaWiki:Tag-OAuth CID: 1805-description/fr
MediaWiki:Tag-OAuth CID: 1841-description/fr
MediaWiki:Tag-OAuth CID: 2071-description/fr
MediaWiki:Tag-OAuth CID: 21-description/fr
MediaWiki:Tag-OAuth CID: 31-description/fr
MediaWiki:Tag-OAuth CID: 429-description/fr
MediaWiki:Tag-OTRS permission added by non-OTRS member/fr
MediaWiki:Tag-Possible LTA-description/fr
MediaWiki:Tag-Possible LTA/fr
MediaWiki:Tag-Potentially problematic translation-description/fr
MediaWiki:Tag-Potentially problematic translation/fr
MediaWiki:Tag-Rapid reverts/en
MediaWiki:Tag-Rapid reverts/fr
MediaWiki:Tag-Short translation-description/fr
MediaWiki:Tag-Short translation/fr
MediaWiki:Tag-blanking-description/fr
MediaWiki:Tag-blanking/fr
MediaWiki:Tag-deletion template removed-description/fr
MediaWiki:Tag-deletion template removed/fr
MediaWiki:Tag-meta spam id/fr
MediaWiki:Tag-newbie external link or email/fr
MediaWiki:Tag-newbie external link-description/email/fr
MediaWiki:Tag-newbie external link-description/fr
MediaWiki:Tag-newbie external link/email/fr
MediaWiki:Tag-newbie external link/fr
MediaWiki:Tag-newbie translation documentation edit/fr
MediaWiki:Tag-ntsamr (global)/email/fr 
MediaWiki:Tag-possible link spam 2-description/fr
MediaWiki:Tag-possible link spam 2-description/fr
MediaWiki:Tag-possible link spam 2/fr
MediaWiki:Tag-possible link spam/fr
MediaWiki:Tag-possible out of scope-description/fr
MediaWiki:Tag-possible out of scope/fr
MediaWiki:Tag-possible vandalism-description/fr
MediaWiki:Tag-possible vandalism/fr
MediaWiki:Tag-repeated xwiki CoI abuse/fr 
MediaWiki:Tag-repeating characters-description/fr
MediaWiki:Tag-repeating characters/fr

Christian 🇫🇷 FR (talk) 15:18, 17 July 2022 (UTC)

Those translations don't belong to translatewiki.net, because those tags are specific to MediaWiki.org website and not common to all MediaWiki installations. They should be translated on this wiki. Ciencia Al Poder (talk) 18:30, 17 July 2022 (UTC)

Since these tags are defined on-wiki, they don’t, and shouldn’t, belong to any code repository, so they won’t ever be migrated from translatewiki.net to the code repository, and thus won’t be imported to mediawiki.org. They should be deleted over there, and all translation needs to happen locally (through edit requests unless you’re a local admin). Tacsipacsi (talk) 01:08, 18 July 2022 (UTC)

Thanks all for these informations. You can easily understand how difficult it is for a beginnner to guess what to do. Here are the steps I have followed:

1. Message "To add or change translations for all wikis, please use translatewiki.net, the MediaWiki localisation project". present on https://www.mediawiki.org/w/index.php?title=MediaWiki:Tag-Potentially_problematic_translation&action=edit I wondered to all wiki ? ...hum on Meta, Special:Tags is present, so I say yes to all wikis => going to translatewiki.net
2. there I see for example https://translatewiki.net/wiki/MediaWiki:Tag-mobile_web_edit/fr which conforts me that the absent messages are really missing there (but others also exist for different /xx too, which means that other users have reached the honey pot)

Solution proposal:

1. According to your proposal @Ciencia Al Poder would you be kind to retrieve the contents of FR translated strings from above list representing one day of work and the complete page of messages. For example: https://translatewiki.net/wiki/MediaWiki:Tag-OAuth_CID:_1841-description/fr (this is a half way solution)
2. Stregthen/adapt/change/remove the warning message "please use translatewiki.net, the MediaWiki localisation project" discouraging users to go there and make orphaned translations
3. when solution 1. is completed, then according to @Tacsipacsi request translatewiki.net to delete pages associated to such translated tags for coherence .

Any advice ? Thanks.

Christian 🇫🇷 FR (talk) 07:48, 18 July 2022 (UTC)

I exported the list of pages from TWN, and my idea was to import them here, but I'm unable to do so because Special:Import on this wiki doesn't allow uploading an XML file for importing. What kind of black magic is this?

I don't know if there's a way to easily import those pages.

Edit: Looks like this can only be done by a bureaucrat on this wiki. Ciencia Al Poder (talk) 13:27, 18 July 2022 (UTC)

Thanks - I dont know if it is the right way but to advance the subject and earn some time for an Edit Request I have referred the situation in Phabricator.

Tracked in Phabricator
Task T313394

Christian 🇫🇷 FR 🚨 (talk) 10:55, 20 July 2022 (UTC)

yes extra help is required - thanks we'll try to be more clever next time. Christian 🇫🇷 FR 🚨 (talk) 14:30, 18 July 2022 (UTC)

2. Stregthen/adapt/change/remove the warning message "please use translatewiki.net, the MediaWiki localisation project" discouraging users to go there and make orphaned translations

For me, it’s clear, and I think it would be clear as a beginner non-developer as well: this particular message exists only here, so it should be translated here. To stop people like you for whom it’s not clear, I think a better solution is to simply disallow the creation of the translation:

• Don’t allow creating translations on translatewiki.net for messages for which the English version (/en message) doesn’t exist. This likely requires a bit of development, but should be doable.
• (Optional) To make absolutely sure, don’t allow anyone but translation administrators to edit /en pages. This is just a matter of a configuration change, and I’ve just run into a code bit that suggests this actually used to be the case, I don’t know why was it relaxed to a big pink warning.

Edit: Looks like this can only be done by a bureaucrat on this wiki.

Not even bureaucrats, only importers (requires uploadimport right, see Special:ListGroupRights#import)—all four of which happen to be bureaucrats as well. Tacsipacsi (talk) 16:02, 19 July 2022 (UTC)

I imported the messages (based on my quick skim it looks fine) and have created a thread on the TWN side to get those pages deleted: https://translatewiki.net/wiki/Thread:Support/Please_delete_some_messages

Let me know if there's anything else I need to do. Legoktm (talk) 03:51, 23 July 2022 (UTC)

woaw, wonderful and already operational ! Next time we should left an open door for rereading by other users (it is always better), when rereading will be operational again (of course...). May be someone will have better expressions working in the context, but for a first shot I m pretty satisfied. Thanks all.

Dont hesitate to ask me FR directed translations when needed rather than me picking up translations at random. Christian 🇫🇷 FR 🚨 (talk) 09:19, 23 July 2022 (UTC)

@Legoktm @Ciencia Al PoderJust as a complement; we have lost the filter information 'tagged by...’. When no description field existed, take the FR text. When tag template is already present, the description field should hold the FR text + the tag template.

This occurs in: Potentially problematic, Repeating char, Possible vandalism, New user project page, Short translation,... Christian 🇫🇷 FR 🚨 (talk) 10:01, 23 July 2022 (UTC)

@Wladek92: sorry, I haven't really been following this thread, I just jumped in because @Ciencia Al Poder pinged me as I have importupload permissions. If I messed something up happy to fix it but otherwise I'm going to respectfully bow out unless I'm needed again. Legoktm (talk) 15:24, 25 July 2022 (UTC)

ok, so can I have a READ access (path to source/history you have changed) and a code mentor ID to correct the source and propose a version of what is concretly expected ? Thanks.

Christian 🇫🇷 FR (talk) 07:19, 26 July 2022 (UTC)

See Special:Contributions/Legoktm.

As per changes to the messages, you'll have to ask here, on a new thread or on the talk page of those messages (although they may get unnoticed) Ciencia Al Poder (talk) 15:01, 26 July 2022 (UTC)

ok but we dont see really what has been done: before= empty / new=empty ; see here . The last request to Legoktm (he has made a substitution) was to ADD the missing description AND keep what exists because we have lost now the "Tagged by filter 76 (hist · journaux)" of @ Shirayuki herabove . Christian 🇫🇷 FR 🚨 (talk) 17:02, 26 July 2022 (UTC)

Can you be more specific? Legoktm imported the messages as you wrote them on TWN. If more modifications are needed just request them: message to edit and what needs to be edited. Ciencia Al Poder (talk) 20:16, 26 July 2022 (UTC)

yes but I have already listed that hereabove

https://www.mediawiki.org/w/index.php?title=Project%3AVillage%20Pump/Flow/2022/07#c-Wladek92-20220723100100-Legoktm-20220723035100

After rereading I ve put here below the modifications to apply in the current version of Special:Tags FR (that is applied above the first Legoktm FR update attempt) and for the following items. (Caution: translatewiki.net pages are now already deleted) .

We want to see (new displayed) = new translated text + (old text when if exists)

and he has done (new displayed) = new translated

so we have lost the call to the template for corresponding tags and filtering information is now missing. Please read the topic to understand what to request.

Sorry to break for now, but i have a mission with disabled people starting to morrow , Thanks all and hasta la vista till the end of next week.

 EN : Potentially problematic translation	Potentially problematic translation	Tagged by filter 76 (hist · logs)
 FR : 
 Add filter line template to correct the FR description
 Il est possible que le texte proposé pour la traduction soit contraire ou n'ait aucun rapport avec l'original.
 Labellisé par le filtre 76 (hist · journaux)
 ---------------------------------
 EN : repeating characters	Repeating characters	This edit contains a highly repetitive character sequence, like "!!!!!!!" or "hahahahahahaha".
 Tagged by filter 79 (hist · logs)
 FR : 
 Add filter line template to correct the FR description	
 Cette modification contient une séquence de caractères répétés trop souvent comme "!!!!!!!" ou "hahahahahahaha".
 Labellisé par le filtre 79 (hist · journaux)
 ---------------------------------
 EN : possible vandalism	possible vandalism	This edit contains blanks a portion of a page in bad faith
 Tagged by filter 66 (hist · logs)
 FR : 
 Add filter line template to correct the FR description	
 Cette modification contient de nombreuses lignes blanches douteuses, sur une portion de la page
 Labellisé par le filtre 66 (hist · journaux)
 ---------------------------------
 EN : New user editing project page	New user editing project page	Tagged by filter 72 (hist · logs)
 FR : 
 Add lifters line template to correct the FR description
 Un contributeur nouveau vient de modifier la page du projet
 Labellisé par le filtre 72 (hist · journaux)
 ---------------------------------
 EN : Short translation	Short translation	Tagged by filter 76 (hist · logs)
 FR : 
 Add filters line template to correct the FR Description : 
 Peu de termes traduits; la traduction est peut être douteuse ou inachevée
 Labellisé par le filtre 76 (hist · journaux)
 ---------------------------------
 EN : OAuth CID: 1261	SWViewer [1.2]	App to view recent changes on small wikis for SWMT. Diffs, whitelist, quick reverts, etc. See w:ru:User:Iluvatar/SWViewer.
 FR : missing user value
 Add user value to correct the FR Description : 
 OAuth CID: 1261	SWViewer [1.2]	Application qui affiche les modifications récentes sur les petits wikis pour SWMT. Les Diffs, listes blanches, annulations rapides, etc. Voir w:ru:User:Iluvatar/SWViewer.
 ---------------------------------
 EN: OAuth CID: 1188	SWViewer [1.0]	SPA (but auth process in php) for viewing queue of edits on small wikis for SWMT. Diffs, whitelist, reverts. Will be hosted on Labs. Desktop version [[ru:user:Iluvatar/SWViewer]] .
 FR : missing user value
 Add user value to correct the FR Description :
 SPA (processus en PHP) pour afficher la file d'attente des modifications sur les petits wikis pour SWMT. Les Diffs, listes blanches, annulations. Version pour ordinateur de bureau [[ru:user:Iluvatar/SWViewer]]. 
 ---------------------------------

Christian 🇫🇷 FR (talk) 13:41, 27 July 2022 (UTC)

Since nobody else would be able to review the changes until you come back, it would be better to wait until you come back, and maybe delete all those imported messages in the meantime if they're incorrect or misleading.

Since the changes need to be done by a sysop, that may not know French enough, it would be good if you create a subpage on your userpage, with a table with 2 columns:

• A link to the message to translate.
• The text that needs to be placed on that message. Ciencia Al Poder (talk) 11:06, 29 July 2022 (UTC)

Have you please the Ids of the concern sysops for me to speak directly of their requirements for the correction ?

Christian 🇫🇷 FR (talk) 15:57, 14 August 2022 (UTC)

I think anyone from Special:ListUsers/sysop should be able to edit those pages. Ciencia Al Poder (talk) 15:00, 19 August 2022 (UTC)

Now if the development made for MediaWiki.org becomes a supported extension that can/should be reusable for other wiki, it's up to Mediawiki.org developers to open-source that development into a deployable module/extension with its own repository (posibly with some more adaptations to work with other wikis, notably by avoiding to use hardcoded references to other contents specific to Mediawiki.org that cannot be tweaked for use on other wikis, such as includion of service URIs, local templates, local user names...).

At that time, you can request an import right for that project, and start importing an XML file (maybe outside the main "MediaWiki" namespace, just like what was done for Miraheze for example in its own namespace for that/those extension(s), or coordinated with other extensions maintained for Mediawiki itself if you really want to keep the generic "MediaWiki" namespace, but probably with prefixes for each message name).

Of course you should then prepare the translations in English (because for now it's impossible to use any other base language for translations; but may be you should allow correcting that English base by allowing translations e.g. in "en-US": when exporting from TWN, you'll detect those suggeted changes/corrections, will review these en-US transltions to fix the "en" base in your project, then reimport them, once curated, into the "en" base; this is a posible solution to avoid havnig many admin requests posted in TWN support pages, or in your project.

Anyway I really suggest that for local development specific to MediaWiki.org, you rename all your needed messages with a common prefix and not just the "MediaWiki:" namespace, which continues to be filled in by supported core messages or extensions/skins messages. So for now they should probably be renamed from "MediaWiki:Tag-*" to "MediaWiki:Wikimedia-Tag-*" (possibly as well with other prefixes or for unprefixed messages) because they are specific to the Wikimedia local instance of the MediaWiki documentation wiki, cleaning up that namespace to avoid collisions with future developments in supported extensions maintained by other teams (including those for use outside Wikimedia: look at what was done for Miraheze or BlueSpice extensions that also use their own prefixes).

Note that even for supported generic extensions for MediaWiki, they all have (or should have already) their own prefix for each translation group. This is needed to help manage the content of that namespace and fix orphaned translations (notably those that are left from old versions that have been replaced over time), without having to make extensive searches and manage new bug requests after their deployments to other wikis.

And anyway, any translation imported from TWN for new messages (or messages whose base English source was updated, except if these updates are fixing minor typos in English and not altering the functionality, excluding for example changes that affect embedded translation variables like "$1", or rename/reorder them for plural/gender support) should first be imported in a test wiki for local curation, and not directly on the production sites. Then Wikimedia Phabricator tasks can be used to validate those curated messages for later deployment on other Wikimedia wikis or to be included in supported projects deployable to other non-WM wikis. Verdy p (talk) 05:34, 23 July 2022 (UTC)

nice, it is a question of organisation. Christian 🇫🇷 FR 🚨 (talk) 09:06, 23 July 2022 (UTC)

Wikimedia Foundation Board of Trustees election 2022 - Propose statements for the 2022 Election Compass

You can find this message translated into additional languages on Meta-wiki.

More languages • Please help translate to your language

Hi all,

Community members in the 2022 Board of Trustees election are invited to propose statements to use in the Election Compass.

An Election Compass is a tool to help voters select the candidates that best align with their beliefs and views. The community members will propose statements for the candidates to answer using a Lickert scale (agree/neutral/disagree). The candidates’ answers to the statements will be loaded into the Election Compass tool. Voters will use the tool by entering in their answer to the statements (agree/disagree/neutral). The results will show the candidates that best align with the voter’s beliefs and views.

Here is the timeline for the Election Compass:

July 8 - 20: Community members propose statements for the Election Compass

July 21 - 22: Elections Committee reviews statements for clarity and removes off-topic statements

July 23 - August 1: Volunteers vote on the statements

August 2 - 4: Elections Committee selects the top 15 statements

August 5 - 12: candidates align themselves with the statements

August 15: The Election Compass opens for voters to use to help guide their voting decision

The Elections Committee will select the top 15 statements at the beginning of August. The Elections Committee will oversee the process, supported by the Movement Strategy and Governance team. MSG will check that the questions are clear, there are no duplicates, no typos, and so on.

Best,

Movement Strategy and Governance

This message was sent on behalf of the Board Selection Task Force and the Elections Committee

MNadzikiewicz (WMF) (talk) 13:41, 12 July 2022 (UTC)

Please mark pages for translation

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.

---

Hi again,

I have three pages that I would be very grateful to have marked for translation:

• Wikibase (rewrite)
• Wikibase/Using Wikibase (new)
• Wikibase/Reference (new)

Thanks! Dan Shick (WMDE) (talk) 13:17, 13 July 2022 (UTC)

Looks like it has been done now Ciencia Al Poder (talk) 14:48, 13 July 2022 (UTC)

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

Help:Cite

Dears,

please help to clarify message T:110. It says:

Such references are particularly useful when citing sources, if different statements come from the same source.

What I am not able to understand is which condition the if must check.

I could understand the version": Such references are particularly useful if citing sources, different statements come from the same source.
or Such references are particularly useful when citing sources, there are different statements come from the same source.

Or am I wrong?

Which one do you pefere?

Regards GpieroMW (talk) 13:01, 14 July 2022 (UTC)

The English phrasing is a little awkward. I would write something like:

"Such references are particularly useful for citing sources when different statements come from the same source."

or

"Such references are particularly useful if different statements come from the same source"

or

"Such references are particularly useful if you want to cite the same source for different statements." Clump (talk) 17:58, 14 July 2022 (UTC)

@Clump

I vote for....

"Such references are particularly useful if different statements come from the same source"

Here or in the 3rd case the "if" makes sense.

Thanks a lot for your kind feedback.

Regards GpieroMW (talk) 20:44, 14 July 2022 (UTC)

Category:SectionTranslationBeforePublish extensions

Please mark this category for translation. 105.105.150.76 (talk) 10:15, 16 July 2022 (UTC)

Done Shirayuki (talk) 10:40, 16 July 2022 (UTC)

Do NOT create other "hook name extensions" categories. Thanks. Shirayuki (talk) 12:32, 16 July 2022 (UTC)

Help:Cite

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.

---

Dears,

please have a look at the note below.

Does it mean that the point is still open and consequently the note should not be changed or updated or eliminated?

I tried to check WMDE article but it is to much "technical" for me.

Regards

T:147 and T:203

<translate><!--T:147--> Note that this feature doesn't yet work on wikis outside the beta cluster, which is why the above example is a mock.</translate> <translate><!--T:203--> You can follow the project update at [<tvar name="1">m:Special:MyLanguage/WMDE Technical Wishes/Book referencing</tvar> m:WMDE Technical Wishes/Book referencing].</translate> GpieroMW (talk) 06:46, 17 July 2022 (UTC)

I think it is clear engough. The feature is to put the page of a book as a partial reference. Status says: 'July 2021: No further work' so dont expect more; that means it remains as it is.

A doubt ?, test the proposed example of https://www.mediawiki.org/wiki/Help:Cite on your page !

On Mediawiki I get error message 'Cite error: Invalid <ref> tag; invalid names, e.g. too many'. As it is a beta, I check the corresponding box 'Automatically enable most beta features' in my Preferences. Now I see at bottom, the ids of referenced pages without the errors.

The purpose of Mediawiki pages is also to hold the details of each product. so dont be surprised if some features described there are not visible on your wiki (but are present on other wikis - and the documentation is also for them).

Christian 🇫🇷 FR (talk) 10:10, 17 July 2022 (UTC)

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

How often is Mediawiki refreshed with translatewiki.net contents ?

When translations are done on translatewiki.net, how long must we wait for them to be merged into Mediawiki interface contents ? Thanks.

Christian 🇫🇷 FR (talk) 09:43, 17 July 2022 (UTC)

Is this about MediaWiki software used on MediaWiki.org? Shirayuki (talk) 09:47, 17 July 2022 (UTC)

yes - interface (updated above) Christian 🇫🇷 FR 🚨 (talk) 09:52, 17 July 2022 (UTC)

The software appears to be updated every Monday. See "Installed software" section in Special:Version. Shirayuki (talk) 10:01, 17 July 2022 (UTC)

nice i'll wait. Christian 🇫🇷 FR 🚨 (talk) 12:35, 17 July 2022 (UTC)

Translating MediaWiki takes effect after an update. 154.121.53.74 (talk) 12:22, 17 July 2022 (UTC)

Exactly, translations are updated along with the software code. This makes the process a bit complicated, consisting of three steps:

1. Migration of translations from translatewiki.net to the code repository. It looks like this runs approximately daily, around 06:00-08:00 UTC.
2. Branching of MediaWiki—this is the point when the code is frozen (barring exceptional cases like significant breakage noticed later). This runs once a week, early Thursday UTC. (This means that the last translations that get deployed a given week are those that were included in the Monday morning migration from translatewiki.net.)
3. Installation of the weekly update—the code frozen in the previous step is actually deployed. This happens in three phases, mediawiki.org and the test wikis are updated on Thurdays, most Wikipedias on Tuesdays, and the rest on Wednesdays.

This means that updating the translations on mediawiki.org takes up to a bit more than eight days, on Wikipedias up to more than ten days. Tacsipacsi (talk) 00:50, 18 July 2022 (UTC)

Request for protecting MediaWiki 1.40

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 don't know why someone created the MediaWiki 1.40 page too early. I think it should be fully protected until September when it will be deployed on WMF. 154.121.53.74 (talk) 12:56, 17 July 2022 (UTC)

I've deleted it (and the /Roadmap subpage); I don't think protection is necessary though. 「ディノ奴千？！」^{☎ Dinoguy1000} 20:59, 17 July 2022 (UTC)

Why did you do this? The IP reported is mis-informed about timing, and anyway this is not a likely vandalism target. 1.40 is going to be branched in a couple of weeks' time. Jdforrester (WMF) (talk) 14:29, 19 July 2022 (UTC)

I didn't know about the timing, and the content all appeared to be a copy-paste skeleton. Feel free to revert my deletions.

this is not a likely vandalism target

I agree, which is why I did not protect the pages after deletion. =) 「ディノ奴千？！」^{☎ Dinoguy1000} 08:45, 20 July 2022 (UTC)

No worries. Done! Jdforrester (WMF) (talk) 18:41, 20 July 2022 (UTC)

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

rereading not accepted on Special:Translate pages

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.

---

Strange, when I validate the rereading of a message, a rectangular light yellow background appears now behind the arrowed blue check box and rereading is presented again next time for approval (as if it was not accepted) and whatever the message/the page to reread I select.

Christian 🇫🇷 FR (talk) 14:51, 21 July 2022 (UTC)

Reread? Do you mean "validate existing translations"? Ciencia Al Poder (talk) 07:24, 22 July 2022 (UTC)

yes checking others FR translations were ok and accepted, like i’ve always done. Christian 🇫🇷 FR 🚨 (talk) 08:57, 22 July 2022 (UTC)

Ok, there's indeed an error. I've reported it as phab:T313608 Ciencia Al Poder (talk) 17:29, 22 July 2022 (UTC)

... sorry if cleaning each corner. Christian 🇫🇷 FR 🚨 (talk) 09:01, 23 July 2022 (UTC)

Should be fixed on Tuesday. By the way, in English it’s called review, not reread or validate (at least in the Translate extension’s terminology). Tacsipacsi (talk) 14:32, 23 July 2022 (UTC)

Nice, thanks; this could have been already detected : do non regression tests exist for this case ? : I. e. if reviewer valids the translation and the translation is presented back again and again. Christian 🇫🇷 FR 🚨 (talk) 10:36, 24 July 2022 (UTC)

FRench is more precise, it can be a review when there is some debate about the possible solutions between several people. But generally it is not the case. Discussion page is not used, at best one user reads again (when it is functional) what has been translated (thus re-reading) and it receives a 1, at worst it is complely ignored and remains in its original form. But no pb, the idea has been understood. Translators have a transversal activity and different cultures and it is normal they dont have a deeper knowledge of each projets/messages they translate. Christian 🇫🇷 FR 🚨 (talk) 08:23, 24 July 2022 (UTC)

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

how to make numbered list to continue after a <syntaxhighlight> insert

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.

---

Going on => https://www.mediawiki.org/wiki/Gadget_kitchen#Write_your_first_user_script , I would like to see the numbered items 5 and 6 after the var... insertion instead of restarting from 1. How can we force the numbering to continue ? Thanks

1 
2 
3 
4 

var..
var...

1
2

Christian 🇫🇷 FR (talk) 18:34, 21 July 2022 (UTC)

Fixed; it had extra linebreaks before/after the code (and was missing a leading "#' for the indented code block). Clump (talk) 18:59, 21 July 2022 (UTC)

thanks that means the instert must be declared as a list item with hash, but received no numbering: good.

Christian 🇫🇷 FR (talk) 09:42, 22 July 2022 (UTC)

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

Extension:PageTriage

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.

---

In Extension:PageTriage, the link "Open tasks" is broken. Shirayuki (talk) 22:53, 23 July 2022 (UTC)

Fixed. P858snake (talk) 05:17, 24 July 2022 (UTC)

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

Help:Magic_words

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.

---

Dears,

it seems that a couple of messages are not totally included between <translate></translate>

Please check T:13 and T:14

Thanks for your attention GpieroMW (talk) 12:01, 25 July 2022 (UTC)

ok realigned - thanks. Christian 🇫🇷 FR 🚨 (talk) 13:34, 25 July 2022 (UTC)

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

Help:Magic_words

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.

---

Sorry

I realized there is a link for a template that does not work.

But I am not able to understand which solution to adopt. Please help me.

Section Variables

<!--T:471-->In some cases, adding parameters will force the parser to invoke a template; for example, <tvar name="tpl-currentdayname-code">{{CURRENTDAYNAME|x}}</tvar> transcludes <tvar name="tpl-currentdayname-result">Template:CURRENTDAYNAME</tvar>, not the variable.

Regards GpieroMW (talk) 13:53, 25 July 2022 (UTC)

this is an example showing how to access the variable or the template. Here the template is useless. Just to teach the way of expanding symbols; not an error in this context. Christian 🇫🇷 FR 🚨 (talk) 14:03, 25 July 2022 (UTC)

Thanks, it is clear now. GpieroMW (talk) 14:08, 25 July 2022 (UTC)

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

Project:Translation/it: which is the purpose or the usage of this project/page?

Dears,

Just a simple question to understand. How this page helps a beginner translator? Which was the original purpose?

It is available from here.

Could be an outdate page? GpieroMW (talk) 16:54, 25 July 2022 (UTC)

Not a clever representation but use the general scheme of translated pages; what I guess is that the EN page answers to your question 'original purpose of this page'. Then each subpage /it /fr /pl ... is a free text to give rules or other subjects concerning the translations and contains a list of translators for this language.

We cannot set direct translation of page /EN -> /FR or /EN -> /IT because rules applying to /EN may be not valid for /FR. In the same way list of translators EN->IT has probably nothing common with those of EN->FR. So root page /EN links simply to /xx subpages without the translation process.

Christian 🇫🇷 FR (talk) 07:14, 26 July 2022 (UTC)

In my opinion if a page/supbage/section/article exists, should contain clear and helpful info, and above all, being up to date.

If a page was create in 2013 (then in a very remote time like geological eras) and nobody put further information, it means this page make only confusion and it is unuseful. GpieroMW (talk) 07:25, 26 July 2022 (UTC)

Have you contacted the persons ? Do they want to be removed ? Update consequently. At least the list of translators /it should be uptodate. Look at the activity of your /it translators, select most actives, ask them if they continue .... too many ideas for me on how to contribute here. Christian 🇫🇷 FR 🚨 (talk) 07:36, 26 July 2022 (UTC)

Help:Namespaces

@Shirayuki

I would like to suggest an improvement for T:34.

Could divide it into smaller translation unit?

At least two or three.

What do you think?

Thanks GpieroMW (talk) 09:04, 27 July 2022 (UTC)

Done Shirayuki (talk) 10:51, 27 July 2022 (UTC)

Vote for Election Compass Statements

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.

---

You can find this message translated into additional languages on Meta-wiki.

More languages • Please help translate to your language

Hi all,

Volunteers in the 2022 Board of Trustees election are invited to vote for statements to use in the Election Compass. You can vote for the statements you would like to see included in the Election Compass on Meta-wiki.

An Election Compass is a tool to help voters select the candidates that best align with their beliefs and views. The community members will propose statements for the candidates to answer using a Lickert scale (agree/neutral/disagree). The candidates’ answers to the statements will be loaded into the Election Compass tool. Voters will use the tool by entering in their answer to the statements (agree/disagree/neutral). The results will show the candidates that best align with the voter’s beliefs and views.

Here is the timeline for the Election Compass:

• July 8 - 20: Volunteers propose statements for the Election Compass
• July 21 - 22: Elections Committee reviews statements for clarity and removes off-topic statements
• July 25 - August 3: Volunteers vote on the statements
• August 4: Elections Committee selects the top 15 statements
• August 5 - 12: candidates align themselves with the statements
• August 16: The Election Compass opens for voters to use to help guide their voting decision

The Elections Committee will select the top 15 statements at the beginning of August

Best,

Movement Strategy and Governance

This message was sent on behalf of the Board Selection Task Force and the Elections Committee MNadzikiewicz (WMF) (talk) 11:32, 31 July 2022 (UTC)

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

Help:Content_translation/Translating/Translation_quality

nothing to discuss

Dears,

please help me to understand the message T:36.

The picture clearly shows a Wikipedia translating step. Is this message valide for translation on MediaWiki or in translatewiki.net?

I have never seen this kind of message while translating operation on MW. There are come cases where the string suggested by Apertium does not require any adjustment. Everything goes well!!

So, is there some modification to do on the EN page?

Regards GpieroMW (talk) 13:11, 31 July 2022 (UTC)

This page is under Help:Content translation. Extension:ContentTranslation (CX), used on Wikipedias, has nothing to do with Extension:Translate, used on mediawiki.org, Translatewiki, Meta and a few other wikis (but not Wikipedias). So I don’t think the English page needs modification, since the page title already implies that it only applies to CX, not Translate. By the way, there’s a feature request to add warnings in Translate as well, but it’s far from being implemented yet. Tacsipacsi (talk) 22:21, 31 July 2022 (UTC)