-
Notifications
You must be signed in to change notification settings - Fork 6
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
UnicodeEncodeError #50
Comments
Hello, and thanks for your error report! I will probably find time to fix this within the next view hours (it should be relatively trivial, assuming the error is caused by what I think it is caused); I'll inform you once the bug is fixed. |
I can't replicate the problem on my own machine, probably due to using a different operating system, but I found two possible ways to fix it, one which is more elegant (though I'm not sure whether it actually works due to being unable to test it), and one that I am entirely sure will work. Both will make no difference to you as a user. Could you update to version |
With 1.17.3 I offline I now get:
1.17.3 online still gives the error:
with 1.17.4 the offline version gives the error:
the online version first gave a different error:
But when I rerun it now (after running the offline version) I get the error again:
|
You need to specify the positional arguments before the optional ones, like this:
It seems likely to me that this error always occurs when you run the tool for the second time in a row after installing it, no matter whether you use the online or offline version.
See above.
Are you sure you have
Probably the thing I mentioned above. It seems to me that 1.17.3 and 1.17.4 seem to have the same underlying issues, so I based 1.17.5 on 1.17.3. You might encounter some more UnicodeEncodeErrors in different places after this update. If this is the case, I can fix them, but I want to see whether there are any first so I don't add additional clutter to fix a problem that doesn't exist. |
After updating to 1.17.5 I got
wkhtmltopdf was installed, but it did not add itself to the PATH. After I finally got
So, that works! Two problems with the pdf: an image was not included, and the single-pixel-border tables were now all double-bordered. But: it is a multi-page pdf, which I didn't get with some other conversion I tried. But the online version still errors:
PS the md I use it at github.com/wovo/cv |
Glad to hear that, I added a note to the README that you have to add
Looking into this right now.
That's weird; also looking into this right now.
Thanks, that's certainly going to help with debugging! |
The issue with the double border was actually already resolved in a much older version, now that I think about it, so I'm surprised this is happening to you. On my system, I can replicate neither the error with the online version, nor the missing image, nor the error in the online version. Some reasons why this might be occurring for you:
Here is the PDF I get with both commands you used: Would you mind sharing your own result for comparison? You can drag-and-drop it into GitHub's text box to attach it to your reply. |
FYI if the pdf is still open, I get:
using -w . both the offline and the online version gives the correct html (single bordered tables, with image) but the wrong pdf (double bordered tables, no image). |
Thanks, that seems right so far!
I assume that with "still open", you mean that it is opened in the PDF viewer, right? Because that's probably because the PDF viewer locks the file as long as it is opened and blocks write access in the process, leading to a failed write (this seems to be the case with Acrobat Reader, for example). There's nothing It's useful to know nonetheless, though, since I could add a more helpful error message for that. Thanks!
I'm currently looking into this (can't replicate it, though; probably has to do with the different file paths that Windows and Linux use). |
I have the same error:
I'm on windows. wkhtmltopdf path is correctly setted
|
I try to run on windows. I get this error, event with an empty input file:
The text was updated successfully, but these errors were encountered: