lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fix svg backend explanation (issue 262380043 by address@hidden)


From: pkx166h
Subject: Re: Fix svg backend explanation (issue 262380043 by address@hidden)
Date: Tue, 15 Sep 2015 17:39:48 +0000

Hosada-san,

See my suggestions below.

(I hope they are correct).


https://codereview.appspot.com/262380043/diff/20001/Documentation/usage/running.itely
File Documentation/usage/running.itely (right):

https://codereview.appspot.com/262380043/diff/20001/Documentation/usage/running.itely#newcode488
Documentation/usage/running.itely:488: @end multitable
I suggest this:

" This creates a single SVG file for every page of output.  Font
information is not embedded so the SVG viewer will require the fonts be
available for optimal rendering.  It is recommended that you do not use
@q{font aliases} or @q{font lists} in case your SVG viewer is not able
to handle them.  Also see the @code{svg-woff} option.

https://codereview.appspot.com/262380043/diff/20001/Documentation/usage/running.itely#newcode496
Documentation/usage/running.itely:496: See @ruser{Entire document
fonts}.
I suggest we say this:

"LilyPond's default fonts (@code{LilyPond Serif}, @code{LilyPond Sans
Serif} and @code{LilyPond Monospace}) are just @emph{local} font
aliases; so when using the @code{svg} backend command it is required
that you explicitly set the default fonts;

https://codereview.appspot.com/262380043/diff/20001/Documentation/usage/running.itely#newcode509
Documentation/usage/running.itely:509:
The put here:

@noindent
Also see @ruser{Entire document fonts}.

https://codereview.appspot.com/262380043/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]