Project:Village Pump

About this board

This page is only for discussing issues related to site.
To get help with MediaWiki software, ask on Project:Support desk.
GpieroMW (talkcontribs)


reading T:12 my understanding about Most content pages, not talk pages


The purpose of the writer was focalized that the tool should be used mainly to produce content page, since this is the aim of the improvement.

Using VE for talk page is only a consequence of the high number of content page produced.

This standpoint, if confirmed, have an influence on the accurate translation of the message.

Furthermore I will suggest the following change:

VisualEditor is not currently available for Wikipedia: neither for pages nor for talk pages.


Reply to "VisualEditor/Portal"

Remove/rename some items in sidebar

AKlapper (WMF) (talkcontribs)

I propose to change some items from the crowded MediaWiki:Sidebar on Because it's crowded.

  • Remove "Main page" - already reachable by clicking the logo above.
  • Rename "Get MediaWiki" to "Install MediaWiki" and link to Manual:Installing MediaWiki instead which covers all steps (including downloading and additional extensions).
  • Remove "Get extensions" - is an overwhelming unhelpful page and installing extensions is another optional part of Manual:Installing MediaWiki already.
  • Remove "Tech blog" - already linked from Communication.
  • Add "Recent news" - linking to News.
  • Rename "Communication" to "Get help and support".
  • Remove "Support desk" - linked as the first item from Communication already.
  • Remove "Code statistics" - not a common enough use case to justify having this clutter the sidebar.
  • Remove "Create a book" - it is uncommon and disabled functionality.
  • Remove "Printable version" - already available via any browser by selecting "File 🡒 Print" or pressing Ctrl+P in the browser.


Ciencia Al Poder (talkcontribs)

That looks good for me.

The items "Create a book" and "Printable version" are not editable from MediaWiki:Sidebar. The first one is provided by an extension that would need to be disabled or uninstalled for this wiki. The second one is a core MediaWiki feature that has no option to disable AFAIK.

Clump (talkcontribs)

Seems good. If you rename "Communication" to "Get help and support" I would also suggest renaming "User help" to something else to reduce confusion. btw "User help" also has what I guess is a truncated mouseover ("The place to find out") which should either be fixed or removed.

Mainframe98 (talkcontribs)

I think this is a good idea. I agree with Clump that renaming "User help" would be useful too. In Dutch that is simply called "Help", so, looking at the title on Help:Contents, " help pages" perhaps?

AKlapper (WMF) (talkcontribs)

Thanks, that makes sense, yes. Probably "User help" should become "User manual" to be aligned with "Technical manual" (though naming these things is very inconsistent across wiki pages).

Regarding the tooltip, that's literally what's in MediaWiki Core's languages/i18n/en.json file for tooltip-n-help: "The place to find out".

PerfektesChaos (talkcontribs)

I am always happy with focussing to important things. Many wikis do offer a confusing bunch of very very interesting links, in the end nothing will be found by newbies any more. Go ahead.

Jdforrester (WMF) (talkcontribs)

For those confused like I was, "User help" is MediaWiki:Help which is over-ridden in English, Farsi, Russian, and Polish, but not other languages where it's just "Help" like on other wikis.

Changed in 2007, presumably to differentiate it from help with installing MW.

P858snake (talkcontribs)

The only one I would disagree with is "Main Page" I unfortunately deal with too many sites & systems where the logo either doesn't go back to the main page or goes somewhere unexpected, so I always try to hunt out a main page type link on systems i'm not familiar with.

PerfektesChaos (talkcontribs)

Meanwhile I examined all links in detail.

  • Positively, the question is which links are important for a less experienced user when visiting any page anywhere.
  • Judging this in context of a software development wiki, which is only consumed by outside readers. They are not supposed to contribute content about their city or favoured music right now, but learning from manuals and documentation pages.
  • Other than with other wikis, this entire wiki is a manual and pile of help pages. On a wikipedia a help page is describing means to achieve something in content but here it is the main purpose itself.
Logo / Main page
Explicit textual link towards mw: is okay.
Many websites do offer a link to their start page this way, but not every user did learn already to try that.
From the view of accessibility this link is appearing with link description but no link title. That does mean: Blind users are in advantage against those who can see the icon but would not guess the effect.
Get MediaWiki
Get extensions
Not necessary to get this access on every page.
From start page there is a prominent box for this branch.
Not helpful on reading a manual page.
Tech blog
Interesting detail for experts. Nice to have.
Leaving the current project. Unexpected behaviour. Confusing.
That’s what a community portal is for.
There is more space to explain to what kind of things I will be transferred to.
Advertise volunteer staff recruiting.
Very important to remind everywhere. Hope for the best.
User help
Technical manual
Crucial navigation.
Support desk
Invites me to ask for support.
It is not obvious to me that there is a responding help desk anywhere.
Crucial navigation to support.
May be renamed to a more intuitive title.
Developer portal
Shifting me to another website. Confusing.
Avoid that.
Linked by a particular box on general start page.
No need to visit that to readers of a manual.
Code statistics
One of many many interesting things.
Nice to have for some insiders.
Does not tell anything to readers of a manual.
May be accessible from any insider navigation.
Community portal
Important navigation access for insiders.
Should bundle all insider links, while particular expert stuff can be removed from side bar. Shifting to expert mode.
Recent changes
Interesting feature for content wikis like a wikipedia.
Pointless for readers of a manual.
Supervising will be done by a few insiders. Such RC people will find their way on every wiki.
Translate content
Needs special experience, permissions, training.
Might be made visible for registered users.
Should be hidden for anonymous.
CSS rule for hiding (MediaWiki:Group-user.css) see en:MediaWiki:Group-user.css
Is there a group assignment for translating accounts? Not my business.
Random page
Interesting feature for content wikis like a wikipedia.
Pointless for this wiki.
It might be nice to experience how some random encyclopedic articles look like, but not meaningful how a random page about software issues will appear.
Here users are looking for something specific, not to get any fun fact on some technical feature. A random encyclopedic article might bewitch me.
Village pump
Important for all visitors, direct access meaningful. Everybody who knows this term might join that.
Could be more close to item “Community portal” and is actually a shortcut for a community issue.
Important for a wiki with one major purpose to explain wikisyntax.
Should enable everybody to test any wikisyntax manual page examples and their variants.
What links here
Navigation to find related pages if the current page did not satisfy.
Related changes
Interesting feature for content wikis like a wikipedia.
Similar issue to Recent Changes.
Pointless for readers of a manual.
Supervising will be done by a few insiders. Such RC/RC people will find their way on every wiki.
Upload file
Interesting feature for content wikis like a wikipedia, where I could upload a photograph of my town hall.
Visitors are not supposed to contribute a lot of content here, nor uploading many images.
Available via Special Pages.
Regulars will manage that anyway.
Special pages
Important navigation access to >100 functionalities.
Generally important.
Page information
Generally meaningful.
Cite this page
Well, yes, okay, maybe.
Quite a lot of redlinks which should be diverted to enWP.
On BibTeX entry please obey this change respectively, which avoids that every citation of anything from any wiki will get the identical identifier. This needs to be unique and must not be wiki:xxx everywhere. I asked for that modification. MediaWiki:{{REVISIONID}}, is fine.
Wikidata item
Generally meaningful navigation. See what happens. Perhaps connected to a wikipedia in certain language.
Create a book
Download as PDF
Printable version
Does not work, or is not meaningful.
We are providing dynamic manuals which might change every hour, not static books to be archived in book shelves.
Every browser has a function to download every web page if needed, including CSS and JS.
In other projects
Helpful to find the similar page in a wikipedia, in certain language, on Commons or whatever.

Even if not configurable by system message or Local.php, undesired items may be hidden via site CSS for all users, or for anonymous.

  • Some of the insider links could be limited to login.
Reply to "Remove/rename some items in sidebar"
GpieroMW (talkcontribs)


a clarification need in the message T:4

Reading the criteria I understood:

'''$AutoConfirmAge''' (Interval of (elapsed) time (in number of seconds) between the creation of the account to the time which qualification was achieved)

Is this the real meaning of that variable?

Could you help me to make the statement more simple?


Ciencia Al Poder (talkcontribs)

Your understanding seems mostly correct. This may be a bit more correct:

Interval of elapsed time (in number of seconds) since the creation of the account to qualify.

GpieroMW (talkcontribs)

thanks a lot

clear, I will make my proposal to update it


Movement Strategy and Governance News – Issue 7

MNadzikiewicz (WMF) (talkcontribs)

Movement Strategy and Governance News

Issue 7, July-September 2022Read the full newsletter

Welcome to the 7th issue of Movement Strategy and Governance News! The newsletter distributes relevant news and events about the implementation of Wikimedia's Movement Strategy recommendations, other relevant topics regarding Movement governance, as well as different projects and activities supported by the Movement Strategy and Governance (MSG) team of the Wikimedia Foundation.

The MSG Newsletter is delivered quarterly, while the more frequent Movement Strategy Weekly will be delivered weekly. Please remember to subscribe here if you would like to receive future issues of this newsletter.

  • Movement sustainability: Wikimedia Foundation's annual sustainability report has been published. (continue reading)
  • Improving user experience: recent improvements on the desktop interface for Wikimedia projects. (continue reading)
  • Safety and inclusion: updates on the revision process of the Universal Code of Conduct Enforcement Guidelines. (continue reading)
  • Equity in decisionmaking: reports from Hubs pilots conversations, recent progress from the Movement Charter Drafting Committee, and a new white paper for futures of participation in the Wikimedia movement. (continue reading)
  • Stakeholders coordination: launch of a helpdesk for Affiliates and volunteer communities working on content partnership. (continue reading)
  • Leadership development: updates on leadership projects by Wikimedia movement organizers in Brazil and Cape Verde. (continue reading)
  • Internal knowledge management: launch of a new portal for technical documentation and community resources. (continue reading)
  • Innovate in free knowledge: high-quality audiovisual resources for scientific experiments and a new toolkit to record oral transcripts. (continue reading)
  • Evaluate, iterate, and adapt: results from the Equity Landscape project pilot (continue reading)
  • Other news and updates: a new forum to discuss Movement Strategy implementation, upcoming Wikimedia Foundation Board of Trustees election, a new podcast to discuss Movement Strategy, and change of personnel for the Foundation's Movement Strategy and Governance team. (continue reading)
Reply to "Movement Strategy and Governance News – Issue 7"

Vote for Election Compass Statements

MNadzikiewicz (WMF) (talkcontribs)

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

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


Movement Strategy and Governance

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

Reply to "Vote for Election Compass Statements"
GpieroMW (talkcontribs)


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

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?


Tacsipacsi (talkcontribs)

This page is under Help:Content translation. Extension:ContentTranslation (CX), used on Wikipedias, has nothing to do with Extension:Translate, used on, 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.

Reply to "Help:Content_translation/Translating/Translation_quality"

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

Wladek92 (talkcontribs)

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 has provided no satisfying results. Thanks.

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

Shirayuki (talkcontribs)

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

Translate {{Tag description}}.

Wladek92 (talkcontribs)
   ok good => this step allows to translate strings "Tagged by filter..."
   Christian 🇫🇷 FR (talk) 09:05, 16 July 2022 (UTC)
Wladek92 (talkcontribs)

... no such Edit link on the page ; @Ciencia Al Poder may be not enough rights for me ?

Shirayuki (talkcontribs)
Wladek92 (talkcontribs)

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, le projet de régionalisation de MediaWiki.

where to request ?

Ciencia Al Poder (talkcontribs)
Wladek92 (talkcontribs)

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

If I take the example of tag 'mobile web edit' I construct key ID => 'MediaWiki:Tag-mobile web edit' which exists on => '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 => and

We should be able to find a solution with 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)

Shirayuki (talkcontribs)
Wladek92 (talkcontribs)

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 is pertinent I 'll solve all of them point per point.

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

Ciencia Al Poder (talkcontribs)

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

Wladek92 (talkcontribs)

So I have created the FR items herebelow on 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-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-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)

Ciencia Al Poder (talkcontribs)

Those translations don't belong to, because those tags are specific to website and not common to all MediaWiki installations. They should be translated on this wiki.

Tacsipacsi (talkcontribs)

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 to the code repository, and thus won’t be imported to They should be deleted over there, and all translation needs to happen locally (through edit requests unless you’re a local admin).

Wladek92 (talkcontribs)

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, the MediaWiki localisation project". present on I wondered to all wiki ? ...hum on Meta, Special:Tags is present, so I say yes to all wikis => going to
  2. there I see for example 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: (this is a half way solution)
  2. Stregthen/adapt/change/remove the warning message "please use, the MediaWiki localisation project" discouraging users to go there and make orphaned translations
  3. when solution 1. is completed, then according to @Tacsipacsi request to delete pages associated to such translated tags for coherence .

Any advice ? Thanks.

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

Ciencia Al Poder (talkcontribs)

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.

Wladek92 (talkcontribs)

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.

Wladek92 (talkcontribs)

yes extra help is required - thanks we'll try to be more clever next time.

Tacsipacsi (talkcontribs)
  1. Stregthen/adapt/change/remove the warning message "please use, 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 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.

Legoktm (talkcontribs)
Wladek92 (talkcontribs)

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.

Wladek92 (talkcontribs)

@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,...

Legoktm (talkcontribs)

@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.

Wladek92 (talkcontribs)

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)

Ciencia Al Poder (talkcontribs)

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)

Wladek92 (talkcontribs)

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 .

Ciencia Al Poder (talkcontribs)

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.

Wladek92 (talkcontribs)

yes but I have already listed that hereabove

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: 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)

Ciencia Al Poder (talkcontribs)

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.
Verdy p (talkcontribs)

Now if the development made for becomes a supported extension that can/should be reusable for other wiki, it's up to 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 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, 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.

Wladek92 (talkcontribs)

nice, it is a question of organisation.

Reply to "Translate: where are located and defined the ID of Special Pages contents ?"
GpieroMW (talkcontribs)


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?


Shirayuki (talkcontribs)

Yes Done

Reply to "Help:Namespaces" (talkcontribs)

Currently, you have to use the 2017 wikitext editor as a beta feature but I am asking if will switch to the 2017 wikitext editor by default because its stable and nice. It also fits with translatable pages.

Wladek92 (talkcontribs)

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)

Whatamidoing (WMF) (talkcontribs)

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".

Wladek92 (talkcontribs)

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.

Whatamidoing (WMF) (talkcontribs)

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).

Reply to "Enabling the 2017 wikitext editor by default"

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

GpieroMW (talkcontribs)


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?

Wladek92 (talkcontribs)

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)

GpieroMW (talkcontribs)

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.

Wladek92 (talkcontribs)

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.

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