LIT output

[=X=]

Hi llasram,
I just tested the LIT file great job! The LIT progress is coming along great, I think soon your final LIT will be better than what we get from professional LIT files!


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.


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. Anyhow below is the error message

 IOError: [Errno 22] invalid mode ('wb') or filename: u'C:\\Documents and Settings\\<username>\\ D:\\Documents and Settings\\<username>\\My Documents\\My Books\\eBookClass
ics\\TiranBlanc.lit'

I've attached the html, command line options, and error in a zip file

[llasram]

Originally Posted by =X=

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.

Originally Posted by =X=

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?

[=X=]

Ok are you asking for a calibre stack trace

[llasram]

Originally Posted by =X=

Ok are you asking for a calibre stack trace

Yes, indeedy.

[=X=]

Okay I just tested the LIT creation. Great Job! You fixed all the issues I was reporting. CSS rules are now. I think these respect the rules too good, I had to fix some of my CSS to work properly

You've also resolved the Table of Content problem, that's awesome it looks great!

Also here is the irony, the latest version has broken the coverpage option.

You've seemed to resolve the issue I was having with creating "Tirrant lo Blanc" so I wont be posting the stack trace.

Last comment. On the page break LIT is inserting what looks like a <hr> preceding the break. That is fine if you want to leave that there but is there a way to disable that feature for those of us who do not wish to see it.

Thank you,
Again Great job I knew the final product would produce better LIT than the commercial products
=X=

[llasram]

Originally Posted by =X=

Also here is the irony, the latest version has broken the coverpage option.

Huh. Well, one more thing to take a look at this evening... On second thought, would you mind opening a ticket about it on the Calibre trac so that I don't forget?

Originally Posted by =X=

You've seemed to resolve the issue I was having with creating "Tirrant lo Blanc" so I wont be posting the stack trace.

That actually doesn't give me the warmest of fuzzies. The error looked like something wasn't merging Windows paths properly, which I don't think I fixed anywhere. But *fingers crossed*.

Originally Posted by =X=

Last comment. On the page break LIT is inserting what looks like a <hr> preceding the break. That is fine if you want to leave that there but is there a way to disable that feature for those of us who do not wish to see it.

I can't think of what that could be... Could you open a ticket on the Calibre trac and attach an example input which results in such output?

[kovidgoyal]

Originally Posted by =X=

Last comment. On the page break LIT is inserting what looks like a <hr> preceding the break. That is fine if you want to leave that there but is there a way to disable that feature for those of us who do not wish to see it.

This will happen in you set --chapter-mark to both instead of pagebreak

[=X=]

Originally Posted by kovidgoyal

This will happen in you set --chapter-mark to both instead of pagebreak

Okay, I did set the follwing switch << --chapter-mark="pagebreak" >> before running any2lit, so there should not be a HR inserted correct?

Also what is the default behavior if this value is not set?

=X=

[kovidgoyal]

The default is pagebreak, but defaults can be overriden via the GUI. Your current default will be in the file epub.py

[=X=]

Ok I belive this is an issue with any2lit. This only shows up with this tool, other formats where created in almost an identical process without the rule line showing.
Thank you
=X=

[yekim54]

Originally Posted by =X=

Ok I belive this is an issue with any2lit. This only shows up with this tool, other formats where created in almost an identical process without the rule line showing.

I also get the rule line between at a chapter break when converting from epub to LRF using the Windows GUI (v0.4.129). The epub file does not have the rule line. My epub.py shows the following:

# chapter mark
# Specify how to mark detected chapters. A value of "pagebreak" will insert page breaks before chapters. A value of "rule" will insert a line before chapters. A value of "none" will disable chapter marking and a value of "both" will use both page breaks and lines to mark chapters.
chapter_mark = u'pagebreak'

[kovidgoyal]

Originally Posted by yekim54

I also get the rule line between at a chapter break when converting from epub to LRF using the Windows GUI (v0.4.129). The epub file does not have the rule line. My epub.py shows the following:

# chapter mark
# Specify how to mark detected chapters. A value of "pagebreak" will insert page breaks before chapters. A value of "rule" will insert a line before chapters. A value of "none" will disable chapter marking and a value of "both" will use both page breaks and lines to mark chapters.
chapter_mark = u'pagebreak'

That's weird. Can you attach a sample epub showing this problem.

[yekim54]

Originally Posted by kovidgoyal

That's weird. Can you attach a sample epub showing this problem.

I opened a ticket (#1660) with sample files attached.

[=X=]

llasram,
I just wanted to give you some positive feedback. The LIT (any2LIT) is working great. The LIT files your tool is producing are excellent.

Thank you
=X=

[chorpler]

Hi! I've been using Calibre's tools for a few months now, and wanted to say ... you guys are awesome. This is one amazing package. And the fact that it updates so often is REALLY cool! I think I'll kick a few bucks your way.

Anyway, on to my question. I just started using Calibre's LIT creation tools; normally I've been converting my source files, usually HTML, to OEB (you know, an .OPF file plus the XHTML and image files, basically) via html2oeb and then from there to MobiPocket. But now I'm experimenting with making LIT files, because I've been reading some threads about how MobiPocket's HTML 3-era support is a lot worse for tables and whatnot than LIT's HTML 4-era support, so I want to see how LITs look.

Anyway, so I took an OPF file that worked fine for conversion to MobiPocket and tried to run oeb2lit on it, and I got the following:

WARNING: No metadata table of contents found
INFO: Applying case-transforming CSS...
INFO: Flattening CSS and remapping font sizes...
INFO: Source base font size is 10.80000pt
INFO: Rasterizing SVG images...
INFO: Trimming unused files from manifest...
WARNING: More than six anchors in file 'Crystal.html'. Some links may not work properly.
INFO: Output written to c:\ebooks\Crystal.lit

It does create a .lit file, but opening it crashes MS Reader, sadly.

So I have two questions.

First, what does it mean about there being no metadata table of contents? There is a <guide> entry for the table of contents, and I'm not sure where else you can put a table of contents in the .OPF file ... I don't see any other place in the OPF 2.0 specs here. Where else should I put a table of contents?

Second, why is it complaining about there being more than six anchors? Surely LIT files aren't limited to just six links, right...?

Thanks for any help here!