[mtravellerh]

Originally Posted by nrapallo

Georges:

Within the last few .epubs posted (see Reid, Mayne: The Plant Hunters v1 6 feb 2009 as well), any .html contains an odd line ending html tag for a carriage return/line feed, namely, &# 13; (ignore my space between the &# and 13, or else you'll see hard line breaks like the end of the below paragraph and no html code):

<!--mozToc h2 1--><h2 id="calibre_chapter_1">CHAPTER&# 13;
I</h2>&# 13;
&# 13;
<h3>One Column Less</h3>&# 13;
&# 13;
<p>NICK BURNEY, Rock City correspondent for the Las Verdes&# 13;
Sentinel, sat nervously in the battered *Ford&# 13;
*pick-up *while *his *wife, Sue,&# 13;
stopped and started as the lights along Tremont Street turned red and

green and red again. Although midnight had long since passed, Las

Verdes, the gambling metropolis situated in a shallow desert bowl so

big that the mountains seemed small in the distance, was still going

strong.</p>

While it appears that an html browser ignores them, they do cause issues when trying to convert directly to .imp from .epub, as they are treated as "hard" line breaks. A soft line breaks like the "\n" line ending is normal, but a "&# 13;" appears non-standard. BTW, Charlie's .epubs created by Calibre do not exhibit the same line-endings or issues.

Did you recently change settings on your text/html editor? Know what's causing them to be output this way?

Regards,

Oh yes, this is an autogenerated Calibre code. I have seen that when I edited epubs directly. I have changed my way of working lately, creating epubs and lrfs from html/zip directly and using another slightly changed html source for mobi-> imp. So the coding of the epubs does not interfere on imps.

So better ask Kovid about those. It's definitely not my code. Maybe he knows a workaround for your epub2imp engine.