Re: [PATCH] SVG backend: Output a single SVG file for each page

[Patrick McCarty]

On Thu, Aug 06, 2009 at 11:44:17AM +0200, Valentin Villenave wrote:
> 2009/8/6 Patrick McCarty <address@hidden>:
> > Any comments or suggestions are welcome.  This patch is one of the
> > final steps towards producing SVG output that is both valid and
> > compatible across all user agents I have tested (Inkscape, Firefox,
> > etc.)
> 
> Though single-page SVG output is a sensible default, perhaps we could
> keep the multi-page SVG output as a -d option just in case some users
> might indeed want to have one single output file?

I wouldn't be against that idea, but the *current* output of
multi-page SVG files is not usable.  For example, Inkscape cannot even
open an SVG file with <pageSet> or <page> in it.  So IMO, single SVG
files that contain multiple pages are not an option.

Would you rather have a -d option that could be used to only output
the *first* page?  That would be really easy.  What should the -d
option be called?

Of course, an output-preview-framework (for use with -dpreview) is
planned, and that would output the first system (plus titles and
headers) in a single SVG file, just like with the PostScript backend.
It might be a while before I attempt to do this though.  :-)

Thanks,
Patrick