This file contains invisible Unicode characters that may be processed differently from what appears below. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to reveal hidden characters.
<html><head><metahttp-equiv="Content-Type"content="text/html; charset=UTF-8"><title>Summary of findings</title><linkrel="stylesheet"type="text/css"href="manual.css"><metaname="generator"content="DocBook XSL Stylesheets V1.76.0"><linkrel="home"href="index.html"title="JpGraph Manual"><linkrel="up"href="apk.html"title="AppendixK.Why it is not possible to add a SVG backend to JpGraph"></head><bodybgcolor="white"text="black"link="#0000FF"vlink="#840084"alink="#0000FF"><divclass="navheader"><tablewidth="100%"summary="Navigation header"><tr><thcolspan="3"align="center">Summary of findings</th></tr><tr><tdwidth="20%"align="left"></td><thwidth="60%"align="center">AppendixK.Why it is not possible to add a SVG backend to JpGraph</th><tdwidth="20%"align="right"></td></tr></table><hr></div><divclass="sect1"title="Summary of findings"><divclass="titlepage"><div><div><h2class="title"style="clear: both"><aname="id2655321"></a>Summary of findings</h2></div></div></div>
<p>To our surprise we have to conclude that with the current SVG standard 1.1 as well
as with the upcoming 1.2 (based on SVG-T) it will not be possible to implement a
full backend in SVG. </p>
<p>The primary hinder is the lack of adequate text manipulation in the current SVG
standard. In addition the implementation of the text supporting feature in current
SVG viewers range from poor and erroneous to non-existing. </p>
<p>The only way to solve this would be to drastically reduce some functionality of
the library in regards to text handling and require the user of the library to
supply text sizes to be used in many places of the library where that is needed.
