Quote:
Originally Posted by =X=
Also again on the TOC topic. I know you mentioned you have no intention of adding the level of support that exist for any2lrf or any2epub, but can you add a switch option where the user can pass in their own HREF to a toc element in the opf file. That is how WordRMR handles it and it works for the most part and is a simple solution.
|
Woah woah woah! I have every intention of adding the level of support which exists for any2lrf/any2epub. I'm just doing it kind of backwards... I pushed the current state to Kovid because I thought it would be useful to people to have *some* LIT-generation ability, but I see now that was a mistake. I'm almost done with Mobipocket generation, which I'm doing much more completely and I've implemented in a way which lets LIT and Mobipocket (and any other format) share everything which is common between. After that gets merged, I'm going to go back to LIT support and implement LIT-specific markup and CSS mangling, bringing it up to the level of the other supported formats.
As for your two specific issues -- MSReader should be picking up on an included stylesheet, with the caveat that MSReader doesn't support any contextual selectors. If you post one of the created LIT files I can hopefully figure out what's going on.
The TOC stuff I'm not 100% sure how to handle... If you generate your own OPF, then you can have a //guide/reference[@type="toc"] which MSReader will just pick up on. If you're letting any2* generate your OPF, I'm less sure... Kovid has been handling that layer, but I believe it just means adding an option to any2epub. I'll take a look at that this evening, as it would definitely be useful for Mobipocket support as well.