Dave,
Sal Mangano has a section on this in his O'Reilly book XSLT Cookbook. Its in
the XML to SVG section.
His style is take an existing SVG file and make it have variable data. He also
take it further and makes generic components.
So concepts like what he has done make work here.
Regards,
Seems to me that this is part of the point of using namespaces. There
is no reason why DocBook per se has to support this; if there is a
well-defined charting XML namespace, a custom stylesheet can easily
import both the DocBook stylesheets and a stylesheet for handling charting.
~Chris
--
DeanNelson wrote:
I wonder if this could be translated into SVG
http://code.google.com/p/graph2svg/
--
--
Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz
On 07/22/2009 07:10 AM, Christopher R. Maden wrote:
Seems to me that this is part of the point of using namespaces. There
is no reason why DocBook per se has to support this; if there is a
well-defined charting XML namespace, a custom stylesheet can easily
import both the DocBook stylesheets
On 07/22/2009 07:55 AM, Jirka Kosek wrote:
DeanNelson wrote:
I wonder if this could be translated into SVG
http://code.google.com/p/graph2svg/
Drat, beat me to it again!
grin/ Jiri isn't it Jirka?
I'm just playing with it.
Looks quite sophisticated!
Lots of examples, various
Dave Pawson wrote:
grin/ Jiri isn't it Jirka?
Yes. Jiří is official form, but I tend to use more informal Jirka
which doesn't use those funny characters. It was problem to transmit
those characters 15 years ego.
Lots of examples, various types of graphs
Just that we need Jirka and
?xml version=1.0 encoding=UTF-8?
!DOCTYPE xygr SYSTEM xygr.dtd
xygr xmlns=http://graph2svg.googlecode.com;
titleFrequency, By date/title
curve color=yellow
point x=5 y=11 color=black pointType=point/
point x=6 y=14 color=black pointType=point/
Dave Pawson wrote:
Jirka, how does this idea fit with 'extending' docbook, vs incorporation
via a namespace vs incorporating into docbook processing?
There are many possibilities, depends on your usage scenario, for example.
1) Incorporate graph2svg markup directly into DocBook
2) Keep
On 07/22/2009 09:14 AM, Jirka Kosek wrote:
Dave Pawson wrote:
Jirka, how does this idea fit with 'extending' docbook, vs incorporation
via a namespace vs incorporating into docbook processing?
There are many possibilities, depends on your usage scenario, for example.
1) Incorporate
Dave Pawson wrote:
btw Jirka, the namespace isn't declared in the DTD,
on the root element?
That's bug. graph2svg was added into namespace in the last stage and
Jakub probably forgot to update DTDs. But you don't need to reference
DTDs from your graph2svg files.
--
On 07/22/2009 04:22 AM, Dave Pawson wrote:
In the long term, I like Chris's idea.
Consider it 'another namespace' content and process it
as ... an extension? But that will have to wait until
the XSLT 2.0 docbook stylesheets I guess.
Not having looked closely at it, I wonder if an alternative
And using a macrodef with ant, it's easy to generate n svg files.
!-- = --
!-- Macro definition to run xslt 2, n times--
!-- == --
macrodef name=call-xslt2 backtrace=true
attribute
Am I the only one that would like an easier way of generating simple
graphs (perhaps line and bar chart) in docbook?
It seems such a pain to go out to an SVG tool and draw it when
XML XSLT could do it for us from a (slightly modded) table?
Anyone else?
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
Yes, Dave, I have had the same thoughts. I wonder if there is an XML based
graph and chart thingy that could handle something like
graph type=line
title Profits /title
data
x30/x
x40/x
x50/x
y10/y
y20/y
y30/y
/data
/graph
I wonder if this could be translated into SVG
Dean Nelson
On 07/22/2009 06:26 AM, DeanNelson wrote:
Yes, Dave, I have had the same thoughts. I wonder if there is an XML
based graph and chart thingy that could handle something like
graph type=line
title Profits /title
data
x30/x
x40/x
x50/x
y10/y
y20/y
y30/y
/data
/graph
I wonder if this could be
15 matches
Mail list logo
