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
most of texts are saved in UTF8 now. For example tags, system messages, scripts, tooltips etc.
Problem is that names (items, players, characters) are saved in CP1252. Would it be possible to change this to UTF 8 as well? Or make some sort of function that would convert encoding between CP1252 and UTF8 and vice versa?
For example:
.set name Příliš žluťoučký kůň
Name is not displayed correctly in paperdoll, status, journal. However tooltip is fine.
When you want to insert this to UTF8 database, it's clearly in CP1252 encoding.
I know most of you don't use these special characters, but we have made several issues about this (unicode support for console, promptconsoleu...).
The text was updated successfully, but these errors were encountered:
We are aware of the issues and it's definitely something to work on. It won't be simple though, because a lot of changes are needed to handle correctly UTF-8 everywhere (also, it's already supposed be handled correctly in multiple places in sphere code, but it seems it's not perfect everywhere).
This issue will be addressed, but be aware it will require time and there are more urgent things to work on
Hi,
most of texts are saved in UTF8 now. For example tags, system messages, scripts, tooltips etc.
Problem is that names (items, players, characters) are saved in CP1252. Would it be possible to change this to UTF 8 as well? Or make some sort of function that would convert encoding between CP1252 and UTF8 and vice versa?
For example:
.set name Příliš žluťoučký kůň
Name is not displayed correctly in paperdoll, status, journal. However tooltip is fine.
When you want to insert this to UTF8 database, it's clearly in CP1252 encoding.
I know most of you don't use these special characters, but we have made several issues about this (unicode support for console, promptconsoleu...).
The text was updated successfully, but these errors were encountered: