Thread: LIT output
View Single Post
Old 01-17-2009, 01:52 PM   #17
llasram
Reticulator of Tharn
llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.llasram ought to be getting tired of karma fortunes by now.
 
llasram's Avatar
 
Posts: 618
Karma: 400000
Join Date: Jan 2007
Location: EST
Device: Sony PRS-505
Quote:
Originally Posted by =X= View Post
Okay here are some of the issues I'm seeing. It seems the fonts are not taking. See my two LIT books to see what I mean. one was created using calibre the other was using WordRMR.
It looks like what's happening is that the calibre any2* layer is moving all CSS font-size into rules using ID selectors, which it seems MSReader doesn't handle. When Kovid finishes merging the oeb2mobi support, I included in the branch flattening all CSS rules to just single class selectors, and added that to LIT generation. So you might get a whole new set of bugs, but issues with CSS not "taking" in MSReader should go away.

Quote:
Originally Posted by =X= View Post
Also I'm getting an error building a LIT book from a word generated HTML. Not sure what is different from this HTML that would cause it to break.
That looks not to be an HTML problem, but a Windows vs. POSIX path issue. Could you post/attach the full stack trace for when you get that error?
llasram is offline   Reply With Quote