Thread: LRF output
View Single Post
Old 07-10-2007, 01:16 AM   #248
bkilian
Zealot
bkilian can name that song in three notesbkilian can name that song in three notesbkilian can name that song in three notesbkilian can name that song in three notesbkilian can name that song in three notesbkilian can name that song in three notesbkilian can name that song in three notesbkilian can name that song in three notesbkilian can name that song in three notesbkilian can name that song in three notesbkilian can name that song in three notes
 
Posts: 131
Karma: 24870
Join Date: Oct 2006
Device: Sony PRS/505
Quote:
Originally Posted by kovidgoyal View Post
It shouldn't leave a blank line between paragraphs unless there's an extra <br /> or </p> tag. For e.g. there wont be a blank line converting the following html
<p>para one</p>
<p>para two</p>
Ooh, you're right, it's the crazy baen html. They add a <p> between every other <p> like this:

Code:
  <p>
   <a id="p9" name="p9">
   </a>
  </p>
  <p onmouseover="PNo(9)">"Don't just stand there like a whore at a wedding, Master Holderman! Trim that foresheet! It's slacker than those idlers you call seamen!" </p>
  <p>
   <a id="p10" name="p10">
   </a>
  </p>
What exactly does the --baen option do? Will it strip out this silliness? (For some reason, Microsoft reader completely ignores the extra <p> and renders with no gaps)

Quote:
Originally Posted by kovidgoyal View Post
Adding per book settings to the OPF file seems like a good way to go. Open a bug report and I'll get around to it eventually. It's going to have to wait till I write a proper OPF parser, which in turn is probably not going to happen till after 0.4.0.

Also open a bug report for the <spine> and I'll add a --use-spine option.

And finally open a bug report for the declaration lists so I dont forget.
Willdo.
bkilian is offline   Reply With Quote