svg error

curiousgeorge · 12-03-2012, 04:38 PM

Ive gone through and through again but for some reason validation says this is wrong:

Code:

<svg xmlns="http://www.w3.org/2000/svg" 
	xmlns:xlink="http://www.w3.org/1999/xlink" 
	version="1.1" 
	width="410"
	height="616" 
	viewBox="0 0 410 616" 
	preserveAspectRatio="none">
        <image width="410" height="616" xlink:href="cover.jpeg"/>
</svg>

it fails for invalid preserveAspectRatio="none">. Ive written several variations and still nothing. Maybe another eye can tell me!

curiousgeorge · 12-03-2012, 04:40 PM

curiousgeorge · 12-07-2012, 01:48 PM

ideas?

theducks · 12-08-2012, 07:07 PM

Quote:

Originally Posted by curiousgeorge

ideas?

"xMinYMin meet" validates and works

I think all those need a argument 'meet' is mine

meet is the default and supposed to be optional

rtmyers · 12-14-2012, 07:33 AM

Which validator is complaining?

dgatwood · 12-19-2012, 06:10 PM

I've filed several bugs about the SVG support in the W3C HTML validator. It's a known weak spot, and you can probably just ignore it. That said, you can also probably do explicit namespace prefixes. Or just include the SVG from a separate file using the <object> tag. That tends to be cleaner.

curiousgeorge · 12-21-2012, 02:14 PM

After much searching I found the issue was within the google's validation:

Code:

preserveAspectRatio="none"

must be replaced as

Code:

preserveAspectRatio="none "

I have verified this and the validator will validate based on that.

the ebook still works regardless of "none" or "none "

12-03-2012, 04:38 PM	#1
curiousgeorge Connoisseur Posts: 53 Karma: 10 Join Date: Aug 2012 Location: Nashville, Tn Device: ipad, Kindle Fire	svg error Ive gone through and through again but for some reason validation says this is wrong: Code: <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" width="410" height="616" viewBox="0 0 410 616" preserveAspectRatio="none"> <image width="410" height="616" xlink:href="cover.jpeg"/> </svg> it fails for invalid preserveAspectRatio="none">. Ive written several variations and still nothing. Maybe another eye can tell me! Last edited by curiousgeorge; 12-07-2012 at 01:46 PM.

12-03-2012, 04:40 PM	#2
curiousgeorge Connoisseur Posts: 53 Karma: 10 Join Date: Aug 2012 Location: Nashville, Tn Device: ipad, Kindle Fire	If I remove preserveAspectRatio="none" it will validate. If I add anything in regards to \|xMinYMin\|xMidYMin\|xMaxYMin\|xMinYMid\|xMidYMid\|xMax YMid\|xMinYMax\|xMidYMax\|xMaxYMax it works. Last edited by curiousgeorge; 12-07-2012 at 01:48 PM.

12-21-2012, 02:14 PM	#7
curiousgeorge Connoisseur Posts: 53 Karma: 10 Join Date: Aug 2012 Location: Nashville, Tn Device: ipad, Kindle Fire	After much searching I found the issue was within the google's validation: Code: preserveAspectRatio="none" must be replaced as Code: preserveAspectRatio="none " I have verified this and the validator will validate based on that. the ebook still works regardless of "none" or "none "

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
MathML TO SVG	saravanan.p	ePub	2	08-11-2011 12:38 PM
Validation error: svg cover	graycyn	Sigil	2	07-24-2011 08:34 PM
calibre, version 0.8.8 ERROR: Error: Error communicating with device no such column:	e-bookuser	Devices	1	07-03-2011 05:09 PM
Kindle and SVG?	Tom Wood	News	1	09-03-2010 09:06 PM
Problems with SVG	ninni	ePub	11	06-18-2010 12:58 PM

12-07-2012, 01:48 PM	#3
curiousgeorge Connoisseur Posts: 53 Karma: 10 Join Date: Aug 2012 Location: Nashville, Tn Device: ipad, Kindle Fire	ideas?

12-14-2012, 07:33 AM	#5
rtmyers Member Posts: 24 Karma: 10 Join Date: Aug 2012 Device: iPad	Which validator is complaining?

12-19-2012, 06:10 PM	#6
dgatwood Curmudgeon Posts: 629 Karma: 1623086 Join Date: Jan 2012 Device: iPad, iPhone, Nook Simple Touch	I've filed several bugs about the SVG support in the W3C HTML validator. It's a known weak spot, and you can probably just ignore it. That said, you can also probably do explicit namespace prefixes. Or just include the SVG from a separate file using the <object> tag. That tends to be cleaner.