-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Handle utf-8 output by kpathsea on Windows. #12253
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
Conversation
32fa7af
to
a348ba4
Compare
a348ba4
to
acd84c8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks reasonable to me. To be on the safe side, should we ask on the kpathsea mailing list?
You get to do it :) |
Asked on the kpathsea mailing list: https://tug.org/pipermail/tex-k/2018-September/002907.html |
Something went wrong ... Please have a look at my logs. |
From the answer in the mailinglist It seems not to be correct to assume utf-8 output on windows. |
PR Summary
cf #11848, especially #11848 (comment). Unfortunately, I haven't been able to find documentation on kpathsea's behavior wrt. encoding, beyond trying to look at the sources.
Thanks to @MortenSHUTE for the original report.
PR Checklist