-
Notifications
You must be signed in to change notification settings - Fork 41
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
Export step fails to open file #37
Comments
I thought I had fixed this. Probably the same cause as #34. I am using a low level Win32 copy mechanism for this which has its own ideas about character encoding. I have tried with Cyrillic and that seemed to work. Will test with Japanese again. Regarding the external drive: Was that a local external drive, USB stick or memory card, or a drive on a remote system, NAS, cloud etc? Was it mounted by drive letter? |
An internal drive should be completely harmless. And your Windows system language is English? It shouldn't matter with Unicode but you never know. |
Correct, my system language is English. |
Well, it appears I had indeed already fixed it, but then cleaned up the code and by that, the Unicode enforcement was lost again, unfortunately. Hence my Cyrillic test now failed as well. It will be fixed with the next update. As a temporary workaround, you can manually copy the .m4b file to the export directory and rename it to .aax. Nonetheless, I am still curious about what might have happened when you were using your F: drive. I will add explicit exception handling for this bit. |
Thanks! If you add the exception handling in the next update I can try my old configuration again and open a new issue if I find anything. |
Fix in version 0.8. |
Working perfectly now, thanks so much! |
Hi there, getting the following error message when I try to export a file.
The download and decryption steps work correctly and I can see the files in my download folder:
(The reason I'm using C:\temp is because if I use my actual Music folder, which lives on a different drive, the process silently fails).
Attached are some relevant files. Please let me know if there's any more information I can provide.
BookLibConnect_2022-04-03_005.log
usersettings.json
stacktrace.txt
The text was updated successfully, but these errors were encountered: