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

WIP: FIX(client): Fix Windows unicode paths on writing files with ofstream #6635

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Hartmnt
Copy link
Member

@Hartmnt Hartmnt commented Nov 25, 2024

No description provided.

@Hartmnt Hartmnt force-pushed the fix_unicode_path branch 3 times, most recently from ae295fd to a63ba6c Compare November 25, 2024 20:57
Copy link
Member

@Krzmbrzl Krzmbrzl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Has this already been tested on an actual Windows machine that could reproduce the original issue?

Changes LGTM. However, I think the commit message should contain a short explanation as to why this change was necessary in the first place. That'll make future change reasoning easier :)

@Hartmnt
Copy link
Member Author

Hartmnt commented Nov 26, 2024

However, I think the commit message should contain a short explanation as to why this change was necessary in the first place. That'll make future change reasoning easier :)

Yes, this is very much not complete, yet. It does not compile on Windows. However, the Windows CI pipeline is currently broken (see translation PR for example)

When this is fixed, i'd like to give the CI build to the bug reporters to test

@Hartmnt Hartmnt force-pushed the fix_unicode_path branch 10 times, most recently from 5dc0e5b to aaaa5c2 Compare November 30, 2024 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants