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

(xlib → win32 file transfers) File names contain mojibake when saved #1012

Open
tsudoko opened this issue May 3, 2015 · 4 comments
Open

Comments

@tsudoko
Copy link
Contributor

tsudoko commented May 3, 2015

@irungentoo
Copy link
Collaborator

Does windows use UTF8 for filenames or some other encoding?

@GrayHatter
Copy link
Collaborator

@irungentoo I was working on fixing this when the new api got released, so it got put onto the back burner. https://github.com/notsecure/uTox/milestones/unicode%20file%20transfers%20on%20windows is the milestone group for this.

I tried to translate the filename string with utf8_to_native(), which allows you to select the save file name you want to use. But then fopen() chokes on that data, not using the selected filename. I was in the process of writing a native_to_utf8() to translate the string back to something fopen() can use, and that's where I stalled. I'm looking for the branch/code now but it seems to have gone missing.

@GrayHatter
Copy link
Collaborator

@irungentoo windows does use utf-16, but after reading #1013 I wonder if utox assumes it's getting utf8 from windows file transfers, or if just accepts u16 and runs with it...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants