Valve Developer Community talk:Alternative Languages: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
(Moved Amicdict message from Template talk:MultiPage.)
Line 20: Line 20:


* Any updates to this idea? - [[User:Amicdict|Amicdict]] ([[User talk:Amicdict|talk]]) 11:25, 5 April 2023 (PDT)
* Any updates to this idea? - [[User:Amicdict|Amicdict]] ([[User talk:Amicdict|talk]]) 11:25, 5 April 2023 (PDT)
{{Message
| user = Amicdict
| time = 5:50, 5 Apr 2023
| As for translating templates, why not just use redirect names as the templates in foreign languages to the English template? For example, using a Russian name for the {{Code|style=2|<nowiki>{{Warning}}</nowiki>}} template {{Code|Предупреждение}} redirect; an Esperanto redirect {{Code|Noto}} to the English template {{Code|style=2|<nowiki>{{Note}}</nowiki>}}.
}}
{{Message
| user = Max34
| time = 19:27, 5 Apr 2023
| text = {{Quote|As for translating templates, why not just use redirect names as the templates in foreign languages to the English template?|sign = [[User:Amicdict|Amicdict]] }}
Well, this makes some sense. However, this also has its downsides.
<span style="color:green">+</span> This option will make it easier for editors who do not know English very well.<br>
<span style="color:red">−</span> Editing the language subpages of a language you don't know will become very difficult. For example, you just wanted to fix something in all the Note templates on the Turkish subpage, but how will you understand where this template is if everything is in Turkish?<br>
<span style="color:red">−</span> Moderation of such things will become much more difficult. In fact, anyone can come and create a redirect to a template with a bad (or obscene) name in an unknown language.<br>
<span style="color:red">−</span> Translation problem: not everything is so good and can be easily translated. For example, {{Code|style=2|Todo}} can be translated into Russian as {{Code|style=2|Необходимо сделать}}, and this is quite long. And some things are very difficult to translate, because in English, for example, there is a word {{Code|style=2|art}}. In Russian this word has many spellings, but none of them reflects the same essence as the original word {{Code|style=2|art}}.
I can also say that redirects make pages load a little longer due to the extra inclusion, but this is very slightly longer, so I do not consider this a minus. Also, such redirects will clog the list of used templates (you can see it when previewing while editing the page), but this is not so scary, so this is also not a minus.
I'm not saying that it's not worth experimenting in this area, it's just that this wiki is not very flexible and we don't have enough tools to work with such things fully.
}}


== Language Subpages ==
== Language Subpages ==

Revision as of 12:27, 5 April 2023

As languages increase in number, the amount of new templates for every language to cater every other language will increase. This seems like an unnecessity. I vote Valve adds official support for languages. --Kodak 17:00, 10 Oct 2005 (PDT)

  • I created this page and most of the current template schema, knowing that we'd have an excessive amount of languages. I also agree with you, but that's up to Valve.. The wiki version is still 1.4.5, while 1.5.0 is out. Good luck with that. --AndrewNeo 03:57, 11 Oct 2005 (PDT)

Languages Category

Added a category to more easily find available languages: Category:Languages --Kodak 14:56, 14 Oct 2005 (PDT)

how to add the tempate to a category?

{{otherlang:en}} {{otherlang:en:de|category:categoryname:de}}

how to link a category to the category for translated pages? SIzzLeopard 08:33, 25 Sep 2007 (PDT)

Should I add redirects with translated names to translated templates?

So like for instance if a chinese person wanted to use Template:Confirm:zh-cn, it would likely be annoying to use it, as they would need to either copy paste english text or use an english keyboard to type in {{confirm:zh-cn}}, which not all chinese people want to do. If there was a template redirect page named simply Template:确认 that redirected to Template:Confirm:zh-cn, then chinese people would only have to type in {{确认}} to use the chinese confirm template.

In my opinion this would make it easier for chinese people to insert chinese templates. Right? - Amicdict (talk) 16:23, 15 September 2021 (PDT)

  • Any updates to this idea? - Amicdict (talk) 11:25, 5 April 2023 (PDT)


(using Template:Message)  As for translating templates, why not just use redirect names as the templates in foreign languages to the English template? For example, using a Russian name for the {{Warning}} template Предупреждение redirect; an Esperanto redirect Noto to the English template {{Note}}.  --Amicdict (talk) 5:50, 5 Apr 2023 (UTC)


(using Template:Message) Template:Text --Max34 (talk) 19:27, 5 Apr 2023 (UTC)

Language Subpages

how do we treat translations of subpages? this page says that if a translated page's URL doesn't match the English version, it should be moved, but like

that feels wrong for subpages. technically, the Russian translation of SteamVR/Environments should be SteamVR/Environments:ru, but that feels off. it isn't a subpage of SteamVR, it's a subpage of SteamVr:ru. this gets even worse for the sub-subpages, like SteamVR/Environments/Getting Started. what should be done in these cases? Kestrelguy (talk) 18:33, 30 April 2022 (PDT)