安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
51 
举报此帖
Greetings.
https://drive.google.com/file/d/1cidNQMqs-3XqG4sVueTqjeUfsCN3XsqC/view?usp=sharing
1) Install the mod.
2) Install a powerful and easy to use notepad that change color of text by code. In that way is easier to notice if you deleted something useful for the syntax of the file that may generate a bug. I recommend you Notepad++, it is free and open source: https://notepad-plus-plus.org .
3) Open your steam folder, (usually Program files (x86)/steam). Navigate to steam/steamapps/workshop/content.
4) You will notice a number of folders with large numbers. Locate the Darkest Dungeon folder, order by modification date, it will helps.
5) You will see another series of folders with large numbers. Depending on the amount of mods can be very tedious to find manually, so like in previous step order folders by date to locate it easier.
6) Inside the mod folder open the folder "localization". You will see a series of files, several ones have a language name and are in ".loc" format, ignore those. You need to translate the .xml files. Copy in this case the files:
"thorn_dialogue.string_table.xml" and "thorn_tooltips.string_table.xml".
7) Open the file copies and look for your language lines, in this language case they will be between <language id=German> and </language>.
Tips:
- If you just send the entire file, it is possible that other undone translations are made or already done ones are polished while you are making the translation. For make easier for the authors of the mod: Delete the rest of the file and leave only the markers <language id="language"> and </language>, and of course your translation in between. In this way the mod authors will have only to copy paste your translation inside the file version they have without affecting the other translations (that may have evolved while you were doing your translation).
- For translating the "tooltips file" open a instance of the game, and have it minimized. While it is easy to translate correctly, for coherency with the rest of the game you will have to translate the tooltips (mostly skill effect descriptions) in a certain way to keep the menu format. The best way to do it, is looking at the description format for the skills of the vanilla characters as reference.
- It is much easier to translate the trinkets by looking at them. Sometimes they are a specific medieval or renaissance object that have a certain name that doesn't match the typical generic translation for the English word. You don't have to earn the trinkets ingame for see their looks. You can see them in inside the mod folder, in the "/panels/icon_equip/trinkets" subfolder.
- Looking for historically accurate words for fencing gear, stances, attacks and movements can be very useful for this certain character.
8) Once you finish the translation you can send the translated .xml files fragments of your language to the authors. They will add to the main ones and generate the .locs. You can send it directly (mail) or use a cloud service (sync, drive, dropbox, etc) for a link depending of authors preferences.
Hopefully it helps, greetings.
I am super busy with other projects I am working in real life, but I will try to get the tooltips part done before Xmas.
Hope people like my translation.
Thanks again :)
The translated chinese one you have upload is my masterpiece. xD
Please re-send me tooltip of v2 whenever you get time or whenever it is close to fatal version
you know, when u have no time playing games, steam become a chat tool. xD