Akira Kurosawa Posted July 20, 2022 Share Posted July 20, 2022 Non-latin symbols errors in release candidate version in main menu, repeats or after skirmish exit. Link to comment Share on other sites More sharing options...
Stan` Posted July 20, 2022 Share Posted July 20, 2022 3 hours ago, DeWynter said: Non-latin symbols errors in release candidate version in main menu, repeats or after skirmish exit. This is a permission issue ? Link to comment Share on other sites More sharing options...
Akira Kurosawa Posted July 20, 2022 Author Share Posted July 20, 2022 (edited) 30 minutes ago, Stan` said: This is a permission issue ? No. Same errors even with admin rights. It's probably unsupported non-latin characters in username. Post limitation, so I would write here. Yes, Yauna also show error at menu, but there is no error about cache. Edited July 20, 2022 by DeWynter Link to comment Share on other sites More sharing options...
Stan` Posted July 20, 2022 Share Posted July 20, 2022 12 minutes ago, DeWynter said: No. Same errors even with admin rights. It's probably unsupported non-latin characters in username. Oh. Right title implied that the game showed non latin chars. A25 does the same I assume ? Link to comment Share on other sites More sharing options...
Stan` Posted July 20, 2022 Share Posted July 20, 2022 I might have a fix for it. std::wofstream instead of ofstream. Link to comment Share on other sites More sharing options...
hyperion Posted July 20, 2022 Share Posted July 20, 2022 1 hour ago, Stan` said: std::wofstream instead of ofstream. ofstream isn't the issue, json is mandated to be utf-8, the path is. c++17 offers an overload for using filesystem::path::value_type* instead of a char* though, don't recall a portable alternative otherwise. Link to comment Share on other sites More sharing options...
Stan` Posted July 20, 2022 Share Posted July 20, 2022 Just now, hyperion said: ofstream isn't the issue, json is mandated to be utf-8, the path is. Maybe not but it fixes the issues of the mod.json not being created... Just now, hyperion said:  c++17 offers an overload for using filesystem::path::value_type* instead of a char* though, don't recall a portable alternative otherwise. Vladislav suggested that too, but there is a high chance it does not compile on 10.12 macOS.  Well the game manages to get the path right with offstream. One cannot load any non latin mods because of the discrepancy between folder name and the rest. Link to comment Share on other sites More sharing options...
Gurken Khan Posted July 20, 2022 Share Posted July 20, 2022 Reminds me of the credits where some names are still not displayed properly. Link to comment Share on other sites More sharing options...
Stan` Posted July 20, 2022 Share Posted July 20, 2022 2 hours ago, Gurken Khan said: Reminds me of the credits where some names are still not displayed properly. Can't do much until Freetype is used Link to comment Share on other sites More sharing options...
Akira Kurosawa Posted July 24, 2022 Author Share Posted July 24, 2022 On 20/07/2022 at 10:40 PM, Stan` said: Can't do much until Freetype is used So, that's mean errors impossible to fix? Link to comment Share on other sites More sharing options...
Stan` Posted July 24, 2022 Share Posted July 24, 2022 24 minutes ago, DeWynter said: So, that's mean errors impossible to fix? Two things here Arabic, Hebrew, CJK, Bengali etc require a special font. Currently those are provided as mods. Nothing to do there. The mod.json error is due to something else and can be fixed. Just have to find how. Link to comment Share on other sites More sharing options...
Akira Kurosawa Posted July 24, 2022 Author Share Posted July 24, 2022 3 minutes ago, Stan` said: The mod.json error is due to something else and can be fixed. Just have to find how. Strange thing, because at pre-Kishite alphas there was no any errors. Link to comment Share on other sites More sharing options...
Stan` Posted July 24, 2022 Share Posted July 24, 2022 4 minutes ago, DeWynter said: Strange thing, because at pre-Kishite alphas there was no any errors. The error was still there, just not visible. Link to comment Share on other sites More sharing options...
Silier Posted July 25, 2022 Share Posted July 25, 2022 On 24/07/2022 at 2:49 PM, Stan` said: The error was still there, just not visible. It wasn't. It was introduced by rewriting the mod loading. Link to comment Share on other sites More sharing options...
Stan` Posted July 25, 2022 Share Posted July 25, 2022 15 minutes ago, Silier said: It wasn't. It was introduced by rewriting the mod loading. It was in the sense that we never supported writing there nor reading the names ? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now