Skip to content

unsupported unicode length #108

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

Open
josh-aliencode opened this issue Oct 14, 2023 · 4 comments
Open

unsupported unicode length #108

josh-aliencode opened this issue Oct 14, 2023 · 4 comments

Comments

@josh-aliencode
Copy link

josh-aliencode commented Oct 14, 2023

When I run the command: detox -rv * on my files.. many of them don't get renamed,
and outputs error: unsupported unicode length
I assume the obvious, that this is because the character length is too much. Is there any way to force this or bypass it?
Or even display the conflicting file?

@dharple
Copy link
Owner

dharple commented Mar 31, 2024

What version of detox are you using? You can get it quickly by running:

detox -V

@dharple
Copy link
Owner

dharple commented Mar 31, 2024

Actually, it's possible that the filenames aren't in UTF-8 at all. You can try detox -n -s iso8859_1 FILE or, if you're using detox 2, detox -n -s iso8859_1-legacy FILE, to see if either yields better results.

@josh-aliencode
Copy link
Author

I figured out the reason was because there was an apostrophe in some names.. will that particular detox command fix that without having to manually rename?

@dharple
Copy link
Owner

dharple commented Mar 31, 2024

It really depends on what the underlying bytes of the apostrophe are. If it's just a normal apostrophe, it shouldn't cause the error you're seeing. If it's a CP-1252 or upper ISO-8859-n apostrophe, then you might get the error you were describing.

The detox -n ... commands above will do a dry run, so you can see what would happen without it actually changing anything.

One other option to help solve this is to use hexdump -C to see what the actual bytes are.

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

No branches or pull requests

2 participants