Quote:
|
Originally Posted by =X=
Based on the error message above, could it be the switch --output-encoding=OUTPUT_ENCODING might be a what is causing the problem. I just don't know what to pass in since there is no documentation for this.
|
It was an encoding issue but not with the encoding option. It was an issue with the encoding of the title string for the PDB header.
Quote:
Originally Posted by =X=
Did you try running the command line options I used. They are captured in the ZIP file.
|
I copied and used the exact command line options you had in the zip file.
Quote:
Originally Posted by =X=
Also the issues where found in v5 but I also tried with v6 beta and I still get the problem
|
The PDB fix hasn't mad it's way into a beta release yet.
Quote:
Originally Posted by =X=
I've also tried the format=ereader option and the input-profile=default input-profile=default (also replaced default with sony).
I still have the same problem.
|
Sorry for the confusion. I didn't mean that this was a solution. I was just pointing out that in the zip file you didn't use it and thus are not producing eReader pdb files. Meaning there will be no images and very little formating.
Quote:
Originally Posted by =X=
Again the GUI continues to work. There has to be a switch you are using in the GUI that is making the PDB and PDF work.
|
The title for PDB files was probably being pre-encoded correctly before being passed to the conversion pipeline.
As far as PDF goes. It works on the command line for me. However, I'm using Linux and you are using Windows. So I need to look into it a bit further to see what is happening on Windows that prevents the command line from working correctly.