User:Nescius/Planned language page changes

Moving all pages ending with language suffix i.e. <page_name>[:/]<lang_suffix> to <lang_suffix>/<page_name> and also change all links on the given pages (other than en) to be [[<lang_suffx>/<page_name>]]. That way Template:Uselang which is currently extremely slow can be rewritten to simply {{ROOTPAGENAME}} because the root page would become the <lang_suffix> for all non english pages and templates like KV,IO etc. can keep working properly and remain universal. The benefits of this is fixing this clutter File:Language_suffix_clutter.png and make loading faster by optimizing uselang which I think needs to be done one way or another. Undoing multipage after that is also planned because it's clearly not liked by many users and it's actually required to be removed to make the mentioned optimization to uselang.

How I imagine it being done automatically with no issues during the process

1. Creating new redirect pages <lang_suffix>/<page_name> that redirect to <page_name>[:/]<lang_suffix>
2. Editing MultiPage template to use the new redirects and make sure everything works properly
3. Overwrite all the created <lang_suffix>/<page_name> redirects in step 1 with their respective <page_name>[:/]<lang_suffix> while still leaving redirect behind
4. Edit all the needed links on those pages
5. Delete all remaining <page_name>[:/]<lang_suffix> redirects

later

• x .. abandoning multipage

1. overwriting the base pages where with the /en suffix version (I think the base page page history is irrelevant it's mostly the notice about moving stuff and the actual page history is on the /en suffix version)
2. moving all the needed content like 'this is a' template and other notices that were on the base page back to the translated pages
3. ....
4. uselang rewritten to {{ROOTPAGENAME}}
5. ....

• xi .. language categories can be subcategories of the default categories (I assume it was something like that before)

Category:Entity on english page and on translated page it would be Category:langshortcut/Entity which would be subcategory of Category:Entity and all categories entity/command related can be automatically applied by Template:this is a which is already on 99% entity/command pages.

• xii .. red links - There will be red links on translated pages at the end of this because lot of pages are simply not translated

idea for solution if that needs one is making new pages automatically with bot for each such red link and putting some sort of template there like {{untranslatedpage}} which would have a notice about page not being translated for current language and have a link to the english article. This can all be detected in the potential untranslatedpage template. Making such template would also need to be accounted for in whatever template takes care of country flags listings on top of the page as currently which flags to list is done using #ifexits and we don't want untranslated pages to be listed too.

Todo: address issues limitations or whatever I missed

suffixes stats

• en has 1375 pages
• ru has 1000 pages
• zh has 709 pages (also contains zh-cn)
• de has 268 pages
• es has 207 pages
• fr has 145 pages
• ko has 133 pages
• ja has 91 pages
• pl has 76 pages
• pt-br has 54 pages
• vi has 37 pages
• uk has 37 pages
• zh-tw has 31 pages
• hr has 26 pages
• eo has 20 pages
• it has 16 pages
• hu has 16 pages
• tr has 16 pages
• pt has 13 pages
• fi has 11 pages
• ka has 5 pages
• sv has 5 pages
• nl has 5 pages
• he has 4 pages
• cs has 3 pages
• el has 2 pages
• no has 2 pages
• hi has 1 pages
• et has 1 pages

See Also

• Template talk:Page
• Template talk:Uselang
• Template talk:MultiPage