though one can't directly input utf8 chars in hardcoded strings, (must use \uXXXX which XXXX is utf16 codepoint)
loading unicode cfg with #108 changes will display correctly.
so abstract all hardcoded strings to separate cfg may be good idea to i10n this.
when such config or such entry unexists, fallback to original string.
format example:
UiString[Base Defense]: B. DEF.
i have very very limited coding skills so i will leave this request open until repo owner decides to do us a favor,
or when i have enough time to waste.
though one can't directly input utf8 chars in hardcoded strings, (must use
\uXXXXwhich XXXX is utf16 codepoint) loading unicode cfg with #108 changes will display correctly.so abstract all hardcoded strings to separate cfg may be good idea to i10n this. when such config or such entry unexists, fallback to original string.
format example:
UiString[Base Defense]: B. DEF.i have very very limited coding skills so i will leave this request open until repo owner decides to do us a favor, or when i have enough time to waste.