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
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
> 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.
The change is in, https://gerrit.wikimedia.org/r/#/c/361597/
The commit message there asserts that there were only a handful
of pages this was seen to affect in [[mw:Parsoid/Round-trip_testing]].
Nevertheless, I should have communicated it more widely, since that
isn't necessarily representative of your wiki.
> 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.
Can you quantify "lots"?
https://zh-yue.wikipedia.org/w/index.php?title=Special:%E9%82%8A%E5%BA%A6%E…
shows less than a hundred main namespace pages.
The justification for the change is that the first colon has meaning,
it escapes the link, giving it the default namespace, but the second
colon is part of the title.
https://en.wikipedia.org/wiki/:Link
vs
https://en.wikipedia.org/wiki/::Link
> 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.
That isn't exactly the same thing.
For some namespaces (File, Category, etc.) the colon
escape renders that syntax as a link rather than
construct itself (file, or whathaveyou).
Using that template on pages in those namespaces
will have different results.
The pseudocode you want is more like,
if (namespace) { ":" + namespace }
> 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
Sorry for the inconvenience. If the above workaround
is unacceptable, let me know, and we'll reassess.
Arlo
Hello,
for quite a few months a server is set up to handle exports the output
formats LaTeX, EPub and Odt.
http://mediawiki2latex.wmflabs.org/
What about making the export to those formats available to wider public.
Can we eventually bring these abandoned features back to the book
creator. Could I help in such an effort.
Yours Dirk
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.
We recently got a suggestion via Phabricator[1] to automatically map
between hiragana and katakana when searching on English Wikipedia and other
wiki projects. As an always-on feature, this isn't difficult to implement,
but major commercial search engines (Google.jp, Bing, Yahoo Japan,
DuckDuckGo, Goo) don't do that. They give different results when searching
for hiragana/katakana forms (for example, オオカミ/おおかみ "wolf"). They also give
different *numbers* of results, seeming to indicate that it's not just
re-ordering the same results (say, so that results in the same script are
ranked higher).[2] I want to know what they know that I don't!
Does anyone have any thoughts on whether this would be useful (seems that
it would) and whether it would cause any problems (it must, or otherwise
all the other search engines would do it, right?).
Any idea why it might be different between a Japanese-language wiki and a
non-Japanese-language wiki? We often are more aggressive in matching
between characters that are not native to a given language--for example,
accents on Latin characters are generally ignored on English-language
wikis. So it might make sense to merge hiragana and katakana on
English-language wikis but not Japanese-language wikis.
Thanks very much for any suggestions or information!
—Trey
[1] https://phabricator.wikimedia.org/T176197
[2] Details of my tests at https://phabricator.wikimedia.org/T173650#3580309
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 todays meeting are:
@addshore & @Tobi_WMDE_SW.
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.