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
Describe the Bug
The Mods Manager errors out if characters 0x91 (い) or 0x93 (え) are found within text, and will refuse to build because the encoding does not support the characters. The problem with that is the encoding does support said characters.
To Reproduce
Steps to reproduce the behavior:
Have a mod that uses either of those characters in a text file.
Try to build the mod.
???
Profit!
Expected behavior
The mod should build without issue.
The text was updated successfully, but these errors were encountered:
So it crashes when you those 2 Japanese characters but not when you use {:unk 91}. Would it be a lot of work to make empty mods where one has the Japanese character that would crash it and the other where it doesn't and attach them to this issue?
So it crashes when you those 2 Japanese characters but not when you use {:unk 91}. Would it be a lot of work to make empty mods where one has the Japanese character that would crash it and the other where it doesn't and attach them to this issue?
It doesn't crash, it just cannot build because the character is unrecognized. Of course the unk tag does not fail building since it's entire purpose is to use unrecognized characters.
Also, I can quickly make something of that nature but it will be a minute before I can do so.
OpenKH Build
Latest as of 12/15/2024
OpenKH Program
Mods Manager
Describe the Bug
The Mods Manager errors out if characters 0x91 (い) or 0x93 (え) are found within text, and will refuse to build because the encoding does not support the characters. The problem with that is the encoding does support said characters.
To Reproduce
Steps to reproduce the behavior:
Have a mod that uses either of those characters in a text file.
Try to build the mod.
???
Profit!
Expected behavior
The mod should build without issue.
The text was updated successfully, but these errors were encountered: