Issue 755 in lilypond: SVG backend improvements

[codesite-noreply]

Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium OpSys-All

New issue 755 by v.villenave: SVG backend improvements
http://code.google.com/p/lilypond/issues/detail?id=755

Greetings,
I'm opening this issue to gather reports about SVG export problems and
ideas on how to improve our SVG backend.

In a detailed mail, Patrick McCarty has made several points. These are to
be found below, and you may read his mail on
http://www.mail-archive.com/address@hidden/msg13934.html (you may
also want to have a look at Issue 114).

"
1.) The `style' attribute should not be used anywhere in an SVG
file, as it does not conform to SVG Tiny 1.2.  Instead,
presentational attributes should be used: font-family, font-style,
font-variant, font-weight, text-anchor.

2.) An incorrect font-family name is used when font families have
multiple-word names.  Adding a comma after the font-family name in
PangoFontDescription strings would simplify the regex matching
process: it would delimit the font-family from the font-style,
font-variant, etc., if included.

3.) Elements should not be grouped with <g> tags.  This requires
Inkscape users to "ungroup" elements in order to move them around,
resize them, etc.

4.) The <page> and <pageSet> elements should be disabled until
Inkscape supports them.  Possible workarounds: (a) Process only
the first page of a multiple-page score, or (b) Process a single
page indicated by a new option -dprint-page-number.

5.) LilyPond creates an ill-formed SVG file when processing
bach-schenker.ly because scm/output-svg.scm does not have a
dashed-slur stencil routine.

6.) `west' is not a valid value for the text-anchor attribute.
Valid values include the following: start, middle, end.
"

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings