SVG coding in EPUB

roger64 · 10-01-2014, 02:37 AM

Hi

I look for a very basic answer. I used a nice tutorial made by GrannyGrump and advices from Rubén to produce two EPUBs using svg images and I am utterly confused. I made use of

1. - A complex code in the complex.epub (a title page)
2. - A plain code in the plain.epub (like the one used for standard png images)

The first one looks rather unintuitive to use, the second one is very easy to implement.

My question is: why should I use the first kind of complex code when I seem to achieve the same results using a plain one?

I just wish a plain (you guessed it) answer.

RbnJrg · 10-01-2014, 12:22 PM

Hi Roger;

Your "complex" .epub is used to diagram a title page so you can see it no matter if the ereader is in portrait or landscape mode (you always will see the full page) without loosing quality (and also no matter the font size the user is employing). For other hand, the method in your "simple" .epub is to add .svg images to your ebook.
You could be wondering: why not using the second method for a title page? Well, do the try to use it, in order to get a page of 800x600 (or the size you want) and the resulting page would be heavier (because you'll be using "paths" for text). However, sometimes could be neccesary to use "paths" for text when you want to "mimic" a copyrighted font. Of that way you could have the font you wish (for the title page) and the same time you won't be using a registered font.
But in principle, you should see both methods as complementary and not excluyent

roger64 · 10-01-2014, 01:05 PM

Hi Rubén

Thanks for your reply.

I'll make a personal assessment.
- Trying to get at a title page which should look fine both on portrait and landscape mode is not a top requirement.
- If this title page is heavier (because of inserted paths), this is not a major problem.
These two things are compensated by the fact that I can use a much easier code, using % and not having to worry about positioning with excruciating precision some tiny elements.

Of course, I understand that it's everybody choice and that the use of "complex" code can bring some technical but - for me - not decisive advantages. At least I am happy to get a confirmation that the "plain" method presents no hidden technical drawback and that I can deal with svg having just to take care of an usual image display.

10-01-2014, 12:22 PM	#2
RbnJrg Wizard Posts: 1,749 Karma: 8700123 Join Date: Mar 2013 Location: Rosario - Santa Fe - Argentina Device: Kindle 4 NT	Hi Roger; Your "complex" .epub is used to diagram a title page so you can see it no matter if the ereader is in portrait or landscape mode (you always will see the full page) without loosing quality (and also no matter the font size the user is employing). For other hand, the method in your "simple" .epub is to add .svg images to your ebook. You could be wondering: why not using the second method for a title page? Well, do the try to use it, in order to get a page of 800x600 (or the size you want) and the resulting page would be heavier (because you'll be using "paths" for text). However, sometimes could be neccesary to use "paths" for text when you want to "mimic" a copyrighted font. Of that way you could have the font you wish (for the title page) and the same time you won't be using a registered font. But in principle, you should see both methods as complementary and not excluyent Last edited by RbnJrg; 10-01-2014 at 04:27 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
svg wrappers for epub covers	Derek R	ePub	9	03-14-2013 09:12 AM
SVG mess in my epub	Iznogood	ePub	2	12-31-2012 08:55 PM
epub-kindle conversion blanks svg with text	bobb40	Conversion	2	09-28-2012 08:05 AM
epub from SVG files	sachin	ePub	7	05-11-2012 09:04 AM
EPub: Bilder mit <svg> einbinden	mmat1	Erste Hilfe	10	02-27-2012 09:46 AM

10-01-2014, 01:05 PM	#3
roger64 Wizard Posts: 2,624 Karma: 3120635 Join Date: Jan 2009 Device: Kindle PW3 (wifi)	Hi Rubén Thanks for your reply. I'll make a personal assessment. - Trying to get at a title page which should look fine both on portrait and landscape mode is not a top requirement. - If this title page is heavier (because of inserted paths), this is not a major problem. These two things are compensated by the fact that I can use a much easier code, using % and not having to worry about positioning with excruciating precision some tiny elements. Of course, I understand that it's everybody choice and that the use of "complex" code can bring some technical but - for me - not decisive advantages. At least I am happy to get a confirmation that the "plain" method presents no hidden technical drawback and that I can deal with svg having just to take care of an usual image display.

Advert