 |
This bug has the effect that darkmod.txt and README.txt cannot be translated in an FM yet. |
 |
@nbohr1more, as we have multi-language support I assume this can be closed..? |
 |
bump on my last comment. |
 |
A related problem to this is that it's not documented what character encoding readme.txt and darkmod.txt even use. I assume that ISO8859-1 derivative from https://wiki.thedarkmod.com/index.php?title=I18N_-_Charset#European_Languages ? So using the ISO8859-1 subset that is *not* "Changed from ISO 88590-1" in that table should be safe - except when the user is using Russian language, because that uses a totally different font? Idea: It might be feasible to support UTF-8, by detecting if those files are UTF-8 encoded (=> decoding as UTF-8 has no errors), and if they are, convert them from UTF-8 to the TDM custom charset. For localization, maybe something like readme-<language>.txt and darkmod-<language>.txt, like readme-german.txt and darkmod-german.txt, readme-czech.txt and darkmod-czech.txt, etc? Then load the one with the correct prefix (fall back to no prefix, which should be english, if it doesn't exist). Could still all be in UTF-8 to make creating/editing them easier. Related: dhewm3 has code to convert between UTF-8 and regular ISO8859-1 (for ImGui), it could be used as a base for conversions: https://github.com/dhewm/dhewm3/blob/a93e50f95796c93dab7b8d8a8daf495ef767afa3/neo/idlib/Str.cpp#L1885 and following |
 |
@covert_caedes I think it's better to make a new issue and then connect it to this so it shows in "Relationships". Well maybe next time at least. |
- Anonymous
