It actually turns out most problems are caused by the quality of the Visio
SVG output.
Biggest problem is the unit-less definition of font-size in the text/css
section, which results in extremely small text. Visio svg also omits xlink
namespace definition and has problems with arrow heads.
After
On 04/04/13 20:28, Marcel Tromp wrote:
I am curious about other people's approach to using SVG in Epub2.
IIRC Epub2, the spec, doesn't mention SVG? Perhaps that is why
most readers don't render well?
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
SVG is part of epub 2.0:
http://www.idpf.org/epub/20/spec/OPS_2.0.1_draft.htm#Section2.5.1
MT
--
On Thu, Apr 4, 2013 at 11:36 PM, davep da...@dpawson.co.uk wrote:
On 04/04/13 20:28, Marcel Tromp wrote:
I am curious about other people's approach to using SVG in Epub2.
IIRC Epub2, the
I've not read Epub3 best practices yet: I was planning to stick with Epub2
for the time being because of a lack of 3.0 readers.
I will try Epub3, but I expect similar results: when I use Streamium (an
Epub3 capable reader) to render my Epub2, the svg is rendered incorrectly
as well.
Fall back
I am curious about other people's approach to using SVG in Epub2.
We rely heavily on SVG for our Docbook to pdf flow and Fop is rendering SVG
(mostly exported from Visio) without major problems.
However, all the epub readers we have tried do a horrible job of rendering
SVG. We have tried Nook
