ARCHIVED team board for the previously existing Parsing Team; see Content-Transform-Team since August 2021
Details
Thu, May 22
Sun, May 18
May 9 2025
May 2 2025
Feb 19 2025
Explicit numbering is looking good, closing this investigation.
Dec 5 2024
This is stalled on T179769. Minor wikis are not going to change magic links while any VisualEditor change can change them back to magic links. It should be an obvious non-starter.
Tbh I don’t think it is that much of a tragedy if some smaller wikis do not have those links for some time. Bot support is definitely needed, but these sorts of replacements are easy to do just with tools like AWB/JWB. So someone just needs to come up with a documentation page on how to do a switch using those sorts of tools. They do not require some very complicated bots, so if magic links do not work until someone runs a bot, that’s fine. It’s not like ISBN data will combust when magic links are not there.
For smaller of almost 1000 WMF wikis it is hard enough to migrate current pages towards {{#isbn:}} in all pages. While larger wikis do have bots, many small projects have just three or four regular article authors. A global support by bots in foreign wikis will be needed.
- When migrating, all 1000 wikis would need to maintain a template implementation of {{ISBN}} which might collide with existing implementations.
- A {{#isbn:}} is not local, but maintained globally and present everywhere.
Dec 4 2024
I will advocate for ‘why’s for a parser function here:
- does not increase template size limit as much as a template would (which is important in citation templates since many are still wikicode-based, not Lua based, so having a template that does [[Special:BookSources/{{{1}}}|ISBN {{{1}}}]] will be much more expensive the more citations you use);
- does not add additional hundreds of thousands of rows to template links table on all big wikis;
- seems correct at least for ISBN since it links to a special page anyway.
Nov 9 2024
Nov 7 2024
Oct 28 2024
Change #1083394 merged by jenkins-bot:
[mediawiki/core@master] docs: Mention wgParserEnableUserLanguage in release notes
Change #1083395 merged by jenkins-bot:
[mediawiki/core@REL1_43] docs: Mention wgParserEnableUserLanguage in release notes
Oct 27 2024
Change #1083395 had a related patch set uploaded (by XtexChooser; author: XtexChooser):
[mediawiki/core@REL1_43] Mention wgParserEnableUserLanguage in changelog
Change #1083394 had a related patch set uploaded (by XtexChooser; author: XtexChooser):
[mediawiki/core@master] Mention wgParserEnableUserLanguage in changelog
Oct 24 2024
Oct 17 2024
@tstarling Thanks! Is there a documentation page#section that it can link to?
Mentioned in SAL (#wikimedia-operations) [2024-10-17T02:18:42Z] <tstarling@deploy2002> Synchronized wmf-config/InitialiseSettings.php: T4085 Enable {{USERLANGUAGE}} on Commons and Meta (duration: 06m 34s)
Change #1079680 merged by jenkins-bot:
[operations/mediawiki-config@master] Enable {{USERLANGUAGE}} on Commons and Meta
Oct 16 2024
Please could someone suggest wording for this proposed Tech News entry, including what documentation it should link to. Thanks.
Oct 14 2024
Change #1079680 had a related patch set uploaded (by Tim Starling; author: Tim Starling):
[operations/mediawiki-config@master] Enable {{USERLANGUAGE}} on Commons and Meta
Sep 23 2024
Untagging design projects since this seems like a bug where some internal links are being marked as external.
Sep 9 2024
Sep 8 2024
Change #508295 merged by jenkins-bot:
[mediawiki/core@master] parser: Add a new {{USERLANGUAGE}} magic word for use in wikitext
Sep 6 2024
Sep 3 2024
Change #508295 restored by Tim Starling:
[mediawiki/core@master] Add a new {{USERLANGUAGE}} variable for use in wikitext
Aug 23 2024
The major issue on this kind of magic is that they are a nightmare on parsing.
- And hard to understand and teach and describe to authors as well.
- It is blowing up syntax description and make things even more complicated.
Aug 22 2024
Aug 21 2024
@Legoktm: German Wikipedia discontinued to use RFC magic in article space for almost a year now.
Aug 13 2024
No response, assuming so.
Aug 7 2024
Aug 1 2024
Can this be considered resolved by T340201: Use custom language code to find i18n XSS issues