LRF output - Page 53

JSWolf · 02-12-2009, 08:25 PM

Quote:

Originally Posted by llasram

Those are known-but-annoying issues with calibre’s ad-hoc CSS parsing and rendering. With the Reader getting EPUB support LRF formatting issues are downgraded a bit, but that one bugs me too and if you open a ticket I’ll see if I can’t at least improve the situation.

I've put in a ticket for the <blockquote> issue in LRF generation.

Ticket #1839 (new defect)

I hope this can be fixed.

netseeker · 02-18-2009, 04:50 PM

I guess i've found one or two issues in Calibres LRF-Output:

Instructions for spacing between paragraphs get ignored, e.g.
p { margin-bottom:8pt; }
Calibre adds far too much space above headlines

Both issues don't occur when converting to ePub or to mobi.

I did attach an excerpt of a html-file as well as the lrf-result of the conversation which shows both issues.

Does sombody know a simple workaround for the two problems? Should i open a ticket?

kovidgoyal · 02-18-2009, 05:58 PM

The LRF Output code is pretty much in maintenance mode where I wont fox anything other than critical bugs. This is because LRF as a format is neccesary only on the PRS 500. So you can open a ticket, but it's not likely that it will be looked at anytime soon.

JSWolf · 02-18-2009, 06:05 PM

Any word on how the blockquote fix is coming along?

kovidgoyal · 02-18-2009, 06:24 PM

Quote:

Originally Posted by JSWolf

Any word on how the blockquote fix is coming along?

That's llasram's baby

netseeker · 02-18-2009, 07:07 PM

Quote:

Originally Posted by kovidgoyal

The LRF Output code is pretty much in maintenance mode where I wont fox anything other than critical bugs. This is because LRF as a format is neccesary only on the PRS 500.

Ok. Seems as it's time for me to switch to ePub. First i didn't like ePub but now i can't even remember why.

Quote:

Originally Posted by kovidgoyal

So you can open a ticket, but it's not likely that it will be looked at anytime soon.

Tickets #1881 and #1882 opened.
(Because according to the "Which E-book device do you have?"-Poll there are still enough PRS-500 users around)

I guess i can find a workaround for the pragraph spacing issue meanwhile (like inserting a paragraph with a very small line height between the "real" paragraphs or something like that)...

llasram · 02-18-2009, 07:30 PM

Quote:

Originally Posted by JSWolf

Any word on how the blockquote fix is coming along?

My offer to look at that was from waaay long ago. At this point to be honest I mostly just want LRF to go away. I'll check tomorrow if there might be a quick fix, but if not then I'm afraid you're on your own.

JSWolf · 02-20-2009, 05:12 PM

Quote:

Originally Posted by llasram

My offer to look at that was from waaay long ago. At this point to be honest I mostly just want LRF to go away. I'll check tomorrow if there might be a quick fix, but if not then I'm afraid you're on your own.

Thing is, what about all the 500 owners who probably would like this fix? They don't have ePub. They have LRF. And the problem with ePub is the really annoying page numbers on the side that overwrite the text. And I've found that buy trying to set a good base font size using ePub's settings, the headers get to be way too huge. So overall, ePub needs work.

bkilian · 02-23-2009, 03:51 PM

Quote:

Originally Posted by kovidgoyal

The LRF Output code is pretty much in maintenance mode where I wont fox anything other than critical bugs. This is because LRF as a format is neccesary only on the PRS 500. So you can open a ticket, but it's not likely that it will be looked at anytime soon.

Aah, but so far I have been singularly unimpressed with the ePub format on the Sony. It was designed for LRF, and works extremely well with LRF. Why make LRF a second class citizen because of nominal support of another standard? I mean, it supports PDF and RTF too, so why not just standardize on RTF, the ebook supports it fine...

kovidgoyal · 02-23-2009, 05:03 PM

Because EPUB is a techincally superior standard that is much easier to code for and has support for advanced features that will be useful in the future.

llasram · 02-23-2009, 05:10 PM

Quote:

Originally Posted by bkilian

Aah, but so far I have been singularly unimpressed with the ePub format on the Sony.

OOC, what have you been "unimpressed with" about EPUB? Ok, fine, DE on the Reader as of this moment doesn't do fully-justified text. Is there absolutely anything else which is a problem?

pepak · 02-23-2009, 05:32 PM

Quote:

Originally Posted by llasram

OOC, what have you been "unimpressed with" about EPUB? Ok, fine, DE on the Reader as of this moment doesn't do fully-justified text. Is there absolutely anything else which is a problem?

Several things, actually.

Aside from the stability, which seems to be a lot better with LRF (on my books, anyway), there's also international font support (embedded fonts are NOT an answer if I have to embed them into every single book separately) and the speed of intra-document links.

I do not deny that EPUB is a better format and these issues will likely be fixed in the future, but as it is now, LRF is still the more usable of the two.

pepak · 02-23-2009, 05:34 PM

Oh, and one other reason: The bugs I notice with LRF support are not really LRF-specific bugs. They are general parser bugs that will appear in every format that performs conversions, and need to be fixed for that reason alone.

llasram · 02-23-2009, 06:00 PM

Quote:

Originally Posted by pepak

Several things, actually.

Aside from the stability, which seems to be a lot better with LRF (on my books, anyway), there's also international font support (embedded fonts are NOT an answer if I have to embed them into every single book separately)

That's not really a format issue so much as an "implementation" issue -- the font Sony bundled just has more glyphs than the one Adobe bundled. Is the @font-face rule with a 'res://' src insufficient for you, or would you like to see specific support for that? Will embedding a font in each book still be not an answer once Calibre has support for it and can just embed your default font selections automatically?

Quote:

and the speed of intra-document links.

I can see how this might be an issue, as Adobe doesn't seem to cache any pagination information to help it jump into a flow more easily. I admit that I'm not sure what could be done here on Calibre's part.

Quote:

I do not deny that EPUB is a better format and these issues will likely be fixed in the future, but as it is now, LRF is still the more usable of the two.

Well then lets make EPUB more usable :-). I'd much much much rather put time into EPUB usability improvements than fixes to the all-but-dead LRF generator.

-Marshall

kovidgoyal · 02-23-2009, 06:56 PM

Quote:

Originally Posted by pepak

Oh, and one other reason: The bugs I notice with LRF support are not really LRF-specific bugs. They are general parser bugs that will appear in every format that performs conversions, and need to be fixed for that reason alone.

The LRF converter has a separate parser from all the other conversion engines.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Change font of header for LRF Output on PRS 505	duckbill	Calibre	3	05-15-2010 11:07 AM
Pissed off with LRF formatting: LRF/LRS clean tool?	grimborg	LRF	8	02-15-2010 01:14 PM
Fonts for LRF output	krischik	Calibre	1	10-03-2009 05:01 AM
CBZ > LRF (LRF>HTML/MOBI????)	sideburnt	Calibre	4	09-15-2009 06:44 AM
libprs500 Issues Converting .LIT to .LRF - .LRF crashes everything	vasbinde	Calibre	6	02-14-2008 12:16 PM

02-18-2009, 05:58 PM	#783
kovidgoyal creator of calibre Posts: 45,355 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	The LRF Output code is pretty much in maintenance mode where I wont fox anything other than critical bugs. This is because LRF as a format is neccesary only on the PRS 500. So you can open a ticket, but it's not likely that it will be looked at anytime soon.

02-18-2009, 06:05 PM	#784
JSWolf Resident Curmudgeon Posts: 79,757 Karma: 145864619 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	Any word on how the blockquote fix is coming along?

02-23-2009, 05:03 PM	#790
kovidgoyal creator of calibre Posts: 45,355 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Because EPUB is a techincally superior standard that is much easier to code for and has support for advanced features that will be useful in the future.

02-23-2009, 05:34 PM	#793
pepak Guru Posts: 610 Karma: 4150 Join Date: Mar 2008 Device: Sony Reader PRS-T3, Kobo Libra H2O	Oh, and one other reason: The bugs I notice with LRF support are not really LRF-specific bugs. They are general parser bugs that will appear in every format that performs conversions, and need to be fixed for that reason alone.

Advert

Advert