‫בתאריך יום ד׳, 2 בספט׳ 2026 ב-5:18 מאת ‪Geert Van Pamel via Wikimedia-l‬‏
<‪[email protected]‬‏>:‬

> About the clutter of local templates on Wikipedia. Since 2019 there was a
> project for "Global templates".


It never was a project.


> What is the status? I don't
> see much strategy to implement this soon. As a volunteer, active on
> multiple languages, this is a handicap; every Wikipedia is using
> its own templates.
>

This is not just your intuition. It was also confirmed by several research
project, e.g.
https://www.mediawiki.org/wiki/File:Connecting_Wikifunctions_to_Wikipedia_Opportunities_and_Challenges.pdf
(page 13)
https://meta.wikimedia.org/wiki/Research:Languages_Onboarding_Experiment_2024_-_Executive_Summary
(not immediately obvious, but if you read the fineprint, a lot will be
about templates)


>
> I read on https://www.mediawiki.org/wiki/Global_templates:
> "This is not a project that is being executed or planned to be executed by
> anyone at any defined point in time, at least not yet. This
> is just an idea, albeit a very detailed one."
>

Exactly, that's what it always has been.


> Personally, I believe templates should not be translated, nor localised
> (except in rare cases).
>
> Advantages of Global templates:
> * all languages use the same template, with identical parameters
> * copy/past is easy amongst languages on Wikipedia
> * easier documentation maintenance: less obsolete documentation


If by "translated" you mean that they shouldn't be forked in every wiki,
then I agree.

The strings that are shown to users must be translatable.

Most of the other code should be shareable and not forked.

Or do you mean something else?
_______________________________________________
Wikimedia-l mailing list -- [email protected], guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/[email protected]/message/SU7ZHRBHKMNRXDI35FWJDDWVG7HK4D3F/
To unsubscribe send an email to [email protected]

Reply via email to