Re: SVG export
Bass writes: > SVG export puts space between "translate" and "(" in transform > attribute of element. > > IE 6.0 registers this as an error. Removing space in SVG document > opens SVG file sucessfully. Thanks for investigating this. What does the SVG spec say, is this a LilyPond or an IE 6.0 bug? Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: SVG export
Jan Nieuwenhuizen writes: > Thanks for investigating this. What does the SVG spec say, is this a > LilyPond or an IE 6.0 bug? Looking at this page http://www.w3.org/TR/SVG/coords.html and especially translate: "translate" wsp* "(" wsp* number ( comma-wsp number )? wsp* ")" reveals that this is a bug in IE 6.0. Would you please report your bug with Microsoft instead? I am quite reluctant to implement workarounds for bugs in Microsoft software. This is something that I feel should at least be discussed. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: SVG export
On Monday 23 January 2006 11.40, Jan Nieuwenhuizen wrote: > Jan Nieuwenhuizen writes: > > Thanks for investigating this. What does the SVG spec say, is this a > > LilyPond or an IE 6.0 bug? > > Looking at this page > > http://www.w3.org/TR/SVG/coords.html > > and especially > > translate: > "translate" wsp* "(" wsp* number ( comma-wsp number )? wsp* ")" > > reveals that this is a bug in IE 6.0. Would you please report your > bug with Microsoft instead? I am quite reluctant to implement > workarounds for bugs in Microsoft software. This is something that I > feel should at least be discussed. It looks like Han-Wen fixed this particular issue already (I haven't tested though). The following is in the ChangeLog: 2006-01-22 Han-Wen Nienhuys <[EMAIL PROTECTED]> * scm/output-svg.scm (placebox): no GNU coding standards in SVG output. -- Erik ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: svg export differs from pdf export
Le 20/08/2021 à 12:09, Matthias Steup a écrit : I recently updated lilypond from 2.18 to 2.22. Since then the rendered svg files differ from the pdf files. The fonts used in title, composer, poet, lyrics change the distance of staffs so that a song that is rendered to one page in pdf, is rendered to two pages in svg. In lilypond 2.18 pdf and svg files where exactly the same. Any help? Could you provide an example? It's a known issue that the current SVG backend does not embed fonts in the output files, leading to rendering discrepancies; however, I find differing numbers of pages surprising, and that might hide another bug. You may want to try out experimental binaries using the Cairo backend: https://lists.gnu.org/archive/html/lilypond-devel/2021-07/msg00070.html With these, the fonts are embedded. You need to run lilypond with --svg -dbackend=cairo. These binaries come with all the warnings related to experimental code. Best, Jean ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond