安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
Because it's not a centralized system, even if there are numerous translation providers, the operation itself won't be problematic. (However, players can choose the better translation. Even for the same language, some translations might be better than others.) These advantages are why I wasn't attracted to a centralized system.
I've considered offering translations via Pot files, but since Oni might process them directly, it's still a tentative option for now.
Firstly, the mod you mentioned operates in a completely different manner from this mod.
This mod loads mods that provide translated text without requiring a DLL. The reason for this approach is because in the past, to offer translations for my mods, programming skills were necessary and it was provided in the form of a separate mod. Additionally, I wanted it to operate in a similar feel to that method.
While there are advantages to consolidating all translations into one place for centralized management, as done by the mod you mentioned, I didn't choose that route because I don't have the time to manage it that way. Moreover, the principle of providing translations as needed is also crucial. I believe there's no need to add translation texts for mods one hasn't subscribed to. Given that everyone has a unique list of mods they've subscribed to, I thought it best to provide translations only as necessary.