User talk:Nescius/Planned language page changes

Moving language pages

It might make more sense to keep page translations as subpages. Something like Team Fortress 2/Scripting/Script Functions/es helps convey that it's still a subpage of the main Team Fortress 2 article. It also helps people search for these translations, since it's a bit unintuitive to search for es/pagename. Lastly, it's still easy to just press enter and see more search results. ―Pee (talk) 16:55, 8 July 2024 (PDT)

There are 10 quick search suggestion but more than 10 languages which means in some cases person seeking their language won't even see it anyway. And also when they seek their language they will still see 9 useless suggestions. The translated pages will still be easily accessible from the country flags on each page so it doesn't also need to clutter the quick suggestion results. Users will understand quickly how to explicitly search for their language the moment they see the link. A lot less intuitive thing is letter casing of the search where they need to match it completely except the first letter.

Another think is backlinks. In your example Team Fortress 2 and Scripting will be a backlink to the English page. In the current use of multipgae that would be the base page but multipage is also planned to be reverted so the backlinks would be wrong if suffix was used.

Also SUBPAGENAME would not be consistent with suffixes. On english pages it gives us the thing we are reading about and on translated pages it would always give us just laguage shortcut and ROOTPAGENAME wouldn't necessariliy gives us what we want. With language prefix ROOTPAGENAME always gives us language shortcut (except in english because that's default and that's still easily distinguishable this way) and SUBPAGENAME always gives us the current page title and so it's easy to work with in templates which can remain universal. Nescius (talk) 00:46, 9 July 2024 (PDT)