You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if the files are moved during compiling, but pack.mcmeta should be in
TFCraft / src / Resources /
and not in
TFCraft / src / Resources / assets / terrafirmacraft /
In case you add a new language not based on english, for example Hong Kong Chinese, it would also require the creation of a new .lang file for vanilla items.
To do so, you only have to go in .minecraft\assets\virtual\legacy\lang and copy paste the language you want to base your new translation on. In our example, copy zh_TW, then rename it the same way the file is named in tfc, like zh_HK. That would require some explanation on the website/wiki or in an official tread about translation in the forum.
I plan to add zh_HK as we have the translation ready, and also ja_US that will be an alternative japanese translation. It will use transliteration of words instead of translation. For example, Basalt will be バサルト "Basaruto" instead of the technical word 玄武岩 "Genbugan".
The addition of new language can also allow the creation of more english variation, like en_JP that can change "savory" for "umami" in the taste skill and "lemon" for "yuzu".
The text was updated successfully, but these errors were encountered:
I tested the addition of new language in 1.7.2 (using bibliocraft), we only need to add some lines in the pack.mcmeta file (see instruction here http://minecraft.gamepedia.com/Resource_pack#Adding_Languages)
I don't know if the files are moved during compiling, but pack.mcmeta should be in
TFCraft / src / Resources /
and not in
TFCraft / src / Resources / assets / terrafirmacraft /
In case you add a new language not based on english, for example Hong Kong Chinese, it would also require the creation of a new .lang file for vanilla items.
To do so, you only have to go in .minecraft\assets\virtual\legacy\lang and copy paste the language you want to base your new translation on. In our example, copy zh_TW, then rename it the same way the file is named in tfc, like zh_HK. That would require some explanation on the website/wiki or in an official tread about translation in the forum.
I plan to add zh_HK as we have the translation ready, and also ja_US that will be an alternative japanese translation. It will use transliteration of words instead of translation. For example, Basalt will be バサルト "Basaruto" instead of the technical word 玄武岩 "Genbugan".
The addition of new language can also allow the creation of more english variation, like en_JP that can change "savory" for "umami" in the taste skill and "lemon" for "yuzu".
The text was updated successfully, but these errors were encountered: