Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Boop application misinterprets UTF-8 text as the native codepage of the operating system #40

Open
DragRedSim opened this issue Dec 18, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@DragRedSim
Copy link

As per the title.

Example: attempting to boop from the game https://www.steamgriddb.com/game/5262323 gives the following:
image
Note the character in the title which maps to hex C2, which in Windows-1252 produces a Latin Capital letter A with circumflex , but which in UTF-8 is a pointer to Latin-1 Supplement, with the following character, hex AE, being shown in its Windows-1252 representation as the correct character, the registered trademark symbol. The string displays correctly on the SteamGridDB site, since pages there declare the UTF-8 encoding

Function reference:

struct nonSteamApp* selectNonSteamApp(char* sgdbName, struct nonSteamApp* apps) {

Since the string is passed in as a char* pointer, it will be treated as a set of bytes without care given to the encoding within.

As a workaround, if the user enables UTF-8 support in Windows 11, it should parse the characters correctly.

I suspect this will also extend to the qsort() call within the function, causing certain cases not to match where they may otherwise appear to do so.

@doZennn doZennn added the bug Something isn't working label Dec 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants