Template talk:LanguageBar

Interesting behaviour on Czech pages

I noticed that on the Czech pages, there is a link back to the Cs page, which is a redirect to Counter-Strike (see Cs/SDK Docs). I'm not sure if this can be fixed other than just deleting the CS redirect. -Equalizer, aka the better pickaxe (talk) 09:28, 12 July 2024 (PDT)

That backlink is shown only when the page exist in this case cs. Thinking creating all those pages like Ru/ Zh/ etc. and those pages could have information about how to make translations, info about templates etc. Nescius (talk)

damn title

I guess it isn't possible to default to SUBPAGENAME displaytitle while also letting other templates called lower like 'this is a' override the title Nescius (talk) 23:32, 12 July 2024 (PDT)

Actually it should be possible by just removing noreplace and changing it to noerror in 'this is a' DISPLAYTITLE use right ?Nescius (talk) 23:37, 12 July 2024 (PDT)

Page layout quirk

Any idea why Half-Life 2 has the language bar on the horizontal line, while Dota 2 has it on top of that line and touching the icons above it, and then Half-Life has the icons overlapping?

Tried switching them around in the page code, adding a line break, and a couple other things, but I don't get why it's happening. Cvoxalury (talk) 06:13, 16 July 2024 (PDT)

using PAGESINCATEGORY to link to categories

Now that {{ACategory}} exists, some categories will have alternate languages that don't exist but contain pages (such as Category:es/Source base brush entities, which currently contains 1 page but doesn't exist). The language bar template could be made to use the PAGESINCATEGORY parser function alongside ifexist on category pages to link to nonexistent translations of the category that have pages in them (for example, {{PAGESINCATEGORY:es/Source base brush entities}} yields 1). This would be helpful for people looking for categories that have translated pages but don't exist (such as the given example of es/Source base brush entities). However, it would double the number of expensive parser functions on category pages. Should this be implemented? ―Pee (talk) 21:30, 20 July 2024 (PDT)

I think it’s unneeded. People that really need those pages will seek them and when they see they are red they can simply create them.

If the suggestion I made in MediaWiki talk:Common.css is implemented we should be able to avoid the #ifexist checks completely Nescius (talk) 00:48, 21 July 2024 (PDT)

Hebrew

Why add Hebrew back ? there are 4 pages from which main page and sdk docs are left untouched with unfinished translation for over 5+ and 12+ years and the other 2 are small. --Nescius (talk) 09:27, 2 September 2024 (PDT)

I didn't see a reason to remove it since there are already a few translated pages and it doesn't do any harm keeping it (#ifexist actually takes an extremely short amount of time to calculate, less than transclusion), and it also seeems like a language that might be translated more in the future. ―Pee (talk) 11:02, 2 September 2024 (PDT)

I don't see a point of keeping language nobody maintains for several years. If there is interest and hebrew translator shows up I see no issue with putting it back. As of now there is no reason to have it. Included languages should at least meet these criteria Valve_Developer_Community:Alternative_Languages#Language_Checklist. (not all included currently do but not to this extent)

The few pages consists of:

Category:He/Portal - single sentence

He/Creating Portal turrets - few sentences

He/Main_Page - unfinished translation last touched by Hebrew editor 5+ years ago

He/SDK_Docs - unfinished translation last touched by Hebrew editor 12+ years ago --Nescius (talk) 11:10, 2 September 2024 (PDT)

Acts weirdly on user pages

See User:Ru/SirYodaJedi/Image formats, which was a langsp page that someone else made for one of my user subpages. Idk why the language was changed to a prefix, which it's traditionally always been a suffix (:es, /es).

— SirYodaJedi (talk) 14:54, 22 September 2024 (PDT)

LanguageBar isn't meant to be used on User namespace. {{Language subpage}} is just remnant from multipage that is currently placing LanguageBar and just waiting to be rewritten

As for the change to suffixes this was one of the reasons File:Language_suffix_clutter.png and another one was ease of detecting language via {{ROOTPAGENAME}}, super page links working properly i.e Ru/page1/page2/page3 the links generated at the top will all properly lead back to Russian page. While with page1/page2/page3/ru page1 and page2 would go to english page. Another thing is having {{SUBPAGENAME}} giving us consistently name of the page i.e on info_target and ru/info_target we get info_target on both.

--Nescius (talk) 14:57, 22 September 2024 (PDT)

LanguageBar isn't meant to be used on User namespace.

So what would be the preferred way of handling the aforementioned page? I don't want to delete it, because it's a genuine translation, but I don't want to move it out of userspace, because it's filled with subjective opinions.
— SirYodaJedi (talk) 15:06, 22 September 2024 (PDT)

I assume separate template for that stuff since it's rare situation. For now if there is no user named Ru it's not really an issue to leave as is. Or can just put see also at the top that links russian page for now --Nescius (talk) 15:11, 22 September 2024 (PDT)

I opted for the latter, moving it back to the original langsp location.
— SirYodaJedi (talk) 15:19, 22 September 2024 (PDT)