Conversion time

JeffElkins · 03-30-2009, 05:01 PM

Using any2epub is generally very speedy, but every once in a while you hit a speedbump and the time increases a bunch. I haven't run tests, but I've seen individual books take 30 or more minutes to convert. Usually, this seems to happen with 'rationalizing fonts.'

Just out of curiosity, what's going on here? What is 'Rationalizing Fonts?'

kovidgoyal · 03-30-2009, 05:04 PM

Rationalizing fonts is rescaling all fonts so that the most common font size in the document is equal to the specified base font size and all other font sizes are rescaled appropriately.

sirbruce · 04-02-2009, 04:15 PM

Quote:

Originally Posted by kovidgoyal

Rationalizing fonts is rescaling all fonts so that the most common font size in the document is equal to the specified base font size and all other font sizes are rescaled appropriately.

I've set Base font size the 0. According to the GUI, this disables the rescaling of fonts. But I just converted an RTF to MOBI and it's still took 14+ minutes, 10+ of those spent on "[INFO] Flattening CSS and remapping font sizes..."

kovidgoyal · 04-02-2009, 04:28 PM

setting to 0 will only work for conversion to EPUB, not MOBI

sirbruce · 04-02-2009, 04:40 PM

Is that a bug or ...? Doesn't seem to happen with LIT files, but maybe they're already in the base font size? What's the base font size for MOBI? Seems like it would be quicker to change the font in Word to the right font size before conversion in the RTF case.

kovidgoyal · 04-02-2009, 04:42 PM

It's probably a bug, I don't care about it though as the whole conversion infrastructure is changing, so this bug will cease to exist automatically.

birdbrainbb · 04-04-2009, 04:01 PM

Quote:

Originally Posted by kovidgoyal

It's probably a bug, I don't care about it though as the whole conversion infrastructure is changing, so this bug will cease to exist automatically.

Oh, yay! I've been having the same problem as JeffElkins, so it'll be great to, er, not have to worry about it anymore.

03-30-2009, 05:01 PM	#1
JeffElkins Guru Posts: 780 Karma: 1416 Join Date: Jan 2008 Device: Kobo Clara 2E/HD, Kindle PW	Conversion time Using any2epub is generally very speedy, but every once in a while you hit a speedbump and the time increases a bunch. I haven't run tests, but I've seen individual books take 30 or more minutes to convert. Usually, this seems to happen with 'rationalizing fonts.' Just out of curiosity, what's going on here? What is 'Rationalizing Fonts?'

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Conversion Time	joedi923	Calibre	3	04-15-2010 06:46 PM
Hilton, James: Time and Time Again, v.1, 29 Feb 2008.	hn_88	BBeB/LRF Books (offline)	0	02-29-2008 12:24 PM
Conversion time?	M0zza	Sony Reader	5	11-17-2007 08:34 AM
iLiad An idea to mitigate boot time (and app launch time) -- For future use	Antartica	iRex Developer's Corner	14	11-05-2006 02:16 AM

03-30-2009, 05:04 PM	#2
kovidgoyal creator of calibre Posts: 43,858 Karma: 22666666 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Rationalizing fonts is rescaling all fonts so that the most common font size in the document is equal to the specified base font size and all other font sizes are rescaled appropriately.

04-02-2009, 04:28 PM	#4
kovidgoyal creator of calibre Posts: 43,858 Karma: 22666666 Join Date: Oct 2006 Location: Mumbai, India Device: Various	setting to 0 will only work for conversion to EPUB, not MOBI

04-02-2009, 04:40 PM	#5
sirbruce Provocateur Posts: 1,859 Karma: 505847 Join Date: Feb 2009 Location: Columbus, OH Device: Kindle Touch, Kindle 2, Kindle DX, iPhone 3GS	Is that a bug or ...? Doesn't seem to happen with LIT files, but maybe they're already in the base font size? What's the base font size for MOBI? Seems like it would be quicker to change the font in Word to the right font size before conversion in the RTF case.

04-02-2009, 04:42 PM	#6
kovidgoyal creator of calibre Posts: 43,858 Karma: 22666666 Join Date: Oct 2006 Location: Mumbai, India Device: Various	It's probably a bug, I don't care about it though as the whole conversion infrastructure is changing, so this bug will cease to exist automatically.

Advert

Advert