A recent change to MediaWiki software seems to have broken templates
everywhere. The syntax
[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]
used to work on a template to generate a link to a page in the same
namespace, typically used on templates related to move (rename) discussions.
However this has stopped working as of last month, causing lots of
[[::ABC|ABC]] to be displayed in plain-text everywhere when this syntax is
used in the main namespace.
We figured for now at yue.wp that
[[{{NAMESPACE}}:{{{1}}}|{{{1}}}]]
(notice the deletion of the colon at the beginning) works and would like to
know if this is the recommended solution. This doesn't seem to have been
picked up by Linter.
Related discussion on yue.wp:
https://zh-yue.wikipedia.org/w/index.php?title=Wikipedia%3A%E5%9F%8E%E5%B8%…
Deryck
[[User:Deryck Chan]]
Sysop & ambassador, yue.wp
Hello,
As mentioned a few months ago there has been a significant update to
the design and layout of printed articles.[0] [1] This impacts both
PDF's created from the "Download as PDF" feature and from printing
directly from the web browser.
The feedback and discussion have been incredibly helpful. The team is
now ready to enable these styles as default across all projects. The
deployment is scheduled for Monday, October 9th. If you have used the
feature recently, not much has changed. If you haven't used it
recently we encourage you to check out the new styles. A few features:
* New layout to reduce paper usage
* Clear printing of tables and infoboxes
* Better headings
* Project-specific branding
For more information, please visit the project page on MediaWiki.org.
Comments and feedback can be left on the talk page there.
[0] https://lists.wikimedia.org/pipermail/wikitech-l/2017-August/088565.html
[1] https://www.mediawiki.org/wiki/Reading/Web/Projects/Print_Styles#Desktop_Pr…
Yours,
Chris Koerner
Community Liaison
Wikimedia Foundation
SUMMARY: The Search Platform team (formerly part of Discovery) is planning
to fix a long-standing search bug on many wiki projects by disabling the
code in CirrusSearch that re-uses the “fallback” languages (which are
specified for user interface or system messages) for the language analysis
modules (which are used to index words in search). Deployment is planned to
start the week of October 9, 2017.
Messaging fallbacks specify what language to show a message in when there
is no message available in the language of a given wiki. A language
analysis module is language-specific software that processes text to
improve searching—so that, for example, searching for a given word will
find related forms of that word, like "hope, hopes, hoping, hoped" or
"resume, resumé, résumé" on English-language wikis.
Fallback languages for system messages make sense for historical and
cultural reasons—a reader of the Chechen Wikipedia is more likely to
understand a user interface or system message in Russian than in French,
Greek, Hindi, Italian, or Japanese—but the fallbacks don't necessarily make
any linguistic sense. Chechen and Russian, for example, are from unrelated
language families; while the languages have undoubtedly influenced one
another, their grammars are completed different.
We will deploy the software change that disables using messaging fallbacks
for language analysis fallbacks in about two weeks (targeting the week of
October 9, 2017), with any cross-language analysis exceptions explicitly
configured in a new manner. Changes will not immediately happen to all
affected wikis because each wiki in each language will need to be
re-indexed, which is a separate process that takes time. There may also be
other delays caused by Elasticsearch upgrades or other changes that need
immediate attention.
You can also track progress of the tasks on Phabricator[1] or read more,
see examples, and get the full list of languages affected on MediaWiki.[2]
[1] https://phabricator.wikimedia.org/T147959
[2]
https://www.mediawiki.org/wiki/Wikimedia_Discovery/Disabling_Messaging_Fall…
Trey Jones
Sr. Software Engineer, Search Platform
Wikimedia Foundation
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow 3-4 pm UTC** on
#wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting: https://www.mediawiki.org/
wiki/Technical_Advice_IRC_Meeting
This meeting is an offer by WMDE’s tech team. Hosts of tomorrows meeting
are: @addshore & @CFisch_WMDE.
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow 3-4 pm UTC** on
#wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
This meeting is an offer by WMDE’s tech team. Hosts of todays meeting are:
@addshore & @CFisch_WMDE.
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
(sorry for cross-posting)
Dear all,
*TL;DR: *If you don't want to wait until you run into a real edit conflict
to tryout *Two Column Edit Conflict View* [1], you can now test the new
interface on a temporary testpage where you will get simulated edit
conflicts.
*About Two Column Edit Conflict View*
Improving the current UI of the edit conflict resolution page was wish #1
in the 2015 Technical wishes survey of the German-speaking community [2].
The TwoColConflict extension ("Two Column Edit Conflict View") [3]
highlights differences between the editor's and the conflicting change
directly in the textfield for an easy possibility to copy and paste desired
pieces of the text and resolving the conflict. It has been a beta feature
on all wikis for 5 months now and users have been invited to test it and
give feedback. [4]
Here is a rough visualisation of how the Two Column Edit Conflict view
works:
https://commons.wikimedia.org/wiki/File:Two_Column_Edit_Conflict_View_-_rou…
:-)
*The challenge*
We got some feedback on the beta feature, but not enough to get a good
feeling if the product is already great as it is now, or if some changes
are still needed. We assume that's because in order to give feedback,
people have to have the beta feature activated AND have an edit conflict
AND share their feedback - that's a pretty rare combination.
*More testing!*
We've implemented a temporary Special page that serves as a *test page* [5]
where you will get simulated edit conflicts: The new interface can be
tested now without actually having an edit conflict, and without the risk
of messing up real wiki pages.
We'd like to invite everyone to test the new interface with the test page
until November 9, 2017!
Please go to *https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Edit_Conflicts/Feedback_Round_Test_Page
<https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Edit_Conflicts/Feedba…>
*for more informations.
If you know people who might be interested in testing, please spread the
word!
Thank you so much,
Birgit (for the Technical Wishes team)
Links:
[1] Multilingual help page
<https://www.mediawiki.org/wiki/Help:Two_Column_Edit_Conflict_View>
[2] Main project page
<https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Edit_Conflicts>
[3] Extension manual
<https://www.mediawiki.org/wiki/Extension:TwoColConflict>
[4] Central feedback page
<https://www.mediawiki.org/wiki/Help_talk:Two_Column_Edit_Conflict_View>
[5] Ticket on Phab for the Special page
<https://phabricator.wikimedia.org/T170375>
--
Birgit Müller
Community Communications Manager
Software Development and Engineering
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Dear Tech Ambassadors,
TLDR: Please give this a try, subscribe, and promote it in your
communities: https://www.mediawiki.org/wiki/Newsletter:Tech_Showcase.
I am of course biased, but I do believe that this newsletter is interesting
basically for any active contributors. The simplest and easiest way to know
about interesting software being developed by staff or volunteers for our
readers and our contributors.
No tech knowledge needed and no time commitment required either. You will
just receive one sentence notifications linking to the fresh software
showcased.
PS: This is a new concept of newsletter for experienced Wikimedians as
well. The Technical Collaboration team hopes that these types of
newsletters will reach new audiences and new voices beyond the power users
following Village Pumps, mailing lists or Phabricator.
---------- Forwarded message ----------
From: Quim Gil <qgil(a)wikimedia.org>
Date: Fri, Oct 13, 2017 at 12:18 PM
Subject: New newsletter: Tech Showcase
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
Tech curious? This is for you:
Tech Showcase <https://www.mediawiki.org/wiki/Newsletter:Tech_Showcase>
A newsletter (*) about fresh software for Wikimedia caught on the spot.
Plans, prototypes, releases... Do you have a scoop? Tell us in the Talk
page!
Just click "Subscribe" and you will be notified in your preferred Wikimedia
wiki.
https://www.mediawiki.org/wiki/Newsletter:Tech_Showcase
(*) This is a newsletter powered by the Newsletter extension
<https://www.mediawiki.org/wiki/Help:Extension:Newsletter>. Expect one
sentence notifications linking to the tech showcased, not lengthy articles
and prose.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
