Proposed bulk change: <<FullSearch>>
I'm making a series of changes to the wiki, designed to ease the migration
to MediaWiki. Many of these are uncontroversial (like fixing broken markup
rather than writing a parser to parse it), but some generate pushback.
Given the volume of changes, the only practical solution is to make changes
and wait for people to object. If you came here because you object to a change,
please reply to the list with an explanation.
The rough plan is shown below, but the details might change due to edge cases.
Standardise content within /<<FullSearch(?:Cached)?+(.*?)>>/:
1. s/(Category\w+)/category:$1/g
* "CategoryFoo" searches for pages that contain the string "CategoryFoo",
"category:CategoryFoo" searches for pages *in* that category
* I'll try to check for pages that actually want the former
* depending on how the search function works, this might involve fixing
some other pages I missed while fixing footers the other week
2. s/(language:\w+) (category:\w+)/$2 $1/g
* shouldn't change page output, but simplifies processing
3. s/category:(?!Category)(\w+)/category:Category$1/g
* seems to be a typo that exists on a few pages
4. s/<<FullSearch(\(\))?>>//g;
* only seems to occur on category pages that redirect to portal pages,
e.g. https://wiki.debian.org/CategoryXWindowSystem?action=raw
Fix complexity around DebianWiki/ObsoleteText:
1. s/manpages.debian.net/manpages.debian.org/ on pages linked from there
* only 36 instances
* the former redirects to the latter, so this seems low-risk
2. ignore "http:" links
* 16,341 instances
* would need to check each link individually
3. delete DebianWiki/ObsoleteText
* actually delete the page, not just add CategoryProposedDeletion
Miscellaneous:
1. change some <<FullSearch>> instances to <<Navigation(children)>>
* more clearly conveys the intent to list children of the current page
2. clear up negative searches as best I can (see e.g. CategoryProposedDeletion)
* looks like some can just become category searches
* "CategoryNetwork -category:CategoryNetworkApplication" might be redundant?
* or maybe we just need to recategorise the relevant pages?
3. add comments next to anything that's unlikely to be translatable
* sorry Beatrice, but you'll probably need to manually find the MediaWiki
equivalent of "language:it -category:CategoryHomepage"
4. possibly some other changes to unique uses of the search function
* e.g. CipUX's right-hand navigation bar
Possible further work:
Translations of portal pages often search for "Category:foo language:bar".
A quick look didn't show a MediaWiki equivalent, and translated URLs
will probably need to be renamed anyway. My current guess is that if page
"ab_CD/SomePage" is in "CategoryFoo", we'll need to change it to
"SomePage/ab-cd" in "CategoryFoo/ab-cd". Templates could automate that a bit.
I haven't looked into this properly yet, so the above might be wrong.
If you have a good idea, or think this is better/worse, please reply!
Reply to: