MobileRead Forums - View Single Post

PressEnter · 10-29-2009, 11:18 AM

I'm trying to figure this out too. I know a particular ereader file I want to convert to LRF is cp1252 charset, but where exactly does --input-encoding="cp1252" go, when using the command-line interface?

Given the command is written

ereader2html infile.pdb outdir "your name" credit_card_number

(which works fine, bar the dodgy A's with hats and random line-breaks, etc), where should one insert

--input-encoding="cp1252"

Or have I typically got it all horribly wrong?

And is it likely to make a difference, given that the html file produced by MobiDeDrm is already encoded in cp1252, according to Firefox?

I should also mention the following: I went to calibre, set the specified file--type plug-in to 'cp1252'. I then imported an html file which had been successfully exploded from ereader with MobiDeDrm. I had already checked that html file and saw that all characters etc, under firefox showed up just fine.

After importing the html file - which apparently causes calibre to automatically zip the html, together with any associated image files, into a single zip - I navigated to the folder (on a mac) where the new zip file was located: exploded the zip: and found that the html file within had become scrambled - ie missing apostrophes and quote marks, random page breaks, that kind of thing. So clearly the problem happens when the html is first exported into Calibre.

Any thoughts? Or should I try and 'open' a ticket as suggested (I figured I'd try here first, being as clueless about a lot of this stuff as some others on this thread)?

10-29-2009, 11:18 AM	#46
PressEnter Member Posts: 15 Karma: 50 Join Date: Jul 2008 Device: Sony Reader	I'm trying to figure this out too. I know a particular ereader file I want to convert to LRF is cp1252 charset, but where exactly does --input-encoding="cp1252" go, when using the command-line interface? Given the command is written ereader2html infile.pdb outdir "your name" credit_card_number (which works fine, bar the dodgy A's with hats and random line-breaks, etc), where should one insert --input-encoding="cp1252" Or have I typically got it all horribly wrong? And is it likely to make a difference, given that the html file produced by MobiDeDrm is already encoded in cp1252, according to Firefox? I should also mention the following: I went to calibre, set the specified file--type plug-in to 'cp1252'. I then imported an html file which had been successfully exploded from ereader with MobiDeDrm. I had already checked that html file and saw that all characters etc, under firefox showed up just fine. After importing the html file - which apparently causes calibre to automatically zip the html, together with any associated image files, into a single zip - I navigated to the folder (on a mac) where the new zip file was located: exploded the zip: and found that the html file within had become scrambled - ie missing apostrophes and quote marks, random page breaks, that kind of thing. So clearly the problem happens when the html is first exported into Calibre. Any thoughts? Or should I try and 'open' a ticket as suggested (I figured I'd try here first, being as clueless about a lot of this stuff as some others on this thread)?