Hello,
I encountered an issue when developing a Hearts of Iron IV mod with CWTools in VSCode.
When localisation keys are defined in non-English localisation files (e.g. l_simp_chinese, l_japanese), CWTools reports them as missing with the warning: Localisation key is not defined for English. CW100
This happens even though the keys are correctly defined in the respective .yml files.
I have already set Localisation Language = Chinese in the CWTools configuration, but the error persists.
To reproduce this Issue,
-
Create a localisation file with a non-English label, e.g.:
l_simp_chinese:
test_key: "測試"
-
Reference this key in a script, e.g. text = test_key.
-
CWTools shows a CW100 warning saying the key is not defined for English.
Would you consider adding proper support for non-English localisation labels so CWTools does not always expect l_english?
Thank you!
Hello,
I encountered an issue when developing a Hearts of Iron IV mod with CWTools in VSCode.
When localisation keys are defined in non-English localisation files (e.g. l_simp_chinese, l_japanese), CWTools reports them as missing with the warning: Localisation key is not defined for English. CW100
This happens even though the keys are correctly defined in the respective .yml files.
I have already set Localisation Language = Chinese in the CWTools configuration, but the error persists.
To reproduce this Issue,
Create a localisation file with a non-English label, e.g.:
l_simp_chinese:
test_key: "測試"
Reference this key in a script, e.g. text = test_key.
CWTools shows a CW100 warning saying the key is not defined for English.
Would you consider adding proper support for non-English localisation labels so CWTools does not always expect l_english?
Thank you!