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.

Sign up for GitHub

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

Jump to bottom

Conversion of ISO9660 filenames results in '?' on en_US systems #82

Closed
pbatard opened this issue Apr 30, 2012 · 1 comment
Closed

Conversion of ISO9660 filenames results in '?' on en_US systems #82

pbatard opened this issue Apr 30, 2012 · 1 comment
Assignees
@pbatard

Comments

@pbatard
Copy link
Owner

pbatard commented Apr 30, 2012

This issue occurs with nonstandard ISO that abuse the ISO-9660 FS and have extended characters for filenames.
One such instance are LiveXP ISOs that contain an 0xE9 character (Latin 2 'é') that gets converted to '?' by MinGW32's tolower() call during the extraction pass (but not during the scan pass), which results in the extraction being interrupted as the target filename is invalid.
@ghost ghost assigned pbatard Apr 30, 2012
@pbatard
Copy link
Owner Author

pbatard commented May 16, 2012

This seems to be linked to LoadLibrary("fmifs.dll") changing the locale.
See http://comments.gmane.org/gmane.comp.gnu.mingw.user/39300

Repository owner locked and limited conversation to collaborators Apr 5, 2019
pbatard pushed a commit that referenced this issue May 20, 2024
@debrouxl @x86fr
Add support for configuring the CPU sequencing mode through the comma…
f24e897 
…nd line. Reorder tests in app/config.c::parse_option alphabetically. Fixes #82.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pbatard pbatard

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pbatard