Quote:
Originally Posted by dwanthny
I have one idea. Quit calibre, rename the configuration directory, restart calibre. This will force calibre to create a brand new configuration folder. If something in your configuration folder is corrupt this might fix it.
|
Dwanthy,
Good idea. I renamed my configuration folder and also deleted and reinstalled Calibre. I changed (only) the TXT input processing to
Paragraph style: off
Formatting style: textile
Otherwise it is a vanilla Calibre installation now.
Disappointingly I get exactly the same non-textile-processed result.
I tried a fresh install on a Windows XP desktop that has never had Calibre on it before. I get the same non-textile-processed result yet again.
I then tried installing on a new Windows 7 Pro laptop. Still no go - and I was confident that this would work for sure.
Quote:
Originally Posted by Perkin
@getajob
Have you tried setting the 'Input character encoding' in the conversion-Look'n'feel, try converting with utf-8, and if that doesn't work try again with cp1252
I had a similar problem with a version just after Textile was introduced, but was the character encoding which was causing it.
Edit:
If I remember, I was converting with cp1252 but the file was utf-8.
|
Perkin,
Good idea. I changed Input Character Coding to 'utf-8' in Look & Feel but all this seemed to was to do was put two black-diamond-question-marks before the 'h1. Header 1' which was unprocessed....(see attached result below)
Is there any easy way to determine what your Input Character Coding actually is?
The only markup that is working is the '<hr />' - maybe this is a clue...
Thanks for your help so far. Any more things I can try?