Re: \markup \sans ... does not always give sans-serif output in svgs in 2.19.36

[Paul Morris]

> On Feb 16, 2016, at 4:17 PM, James Lowe <address@hidden> wrote:
> 
> From usage:
> 
> http://lilypond.org/doc/v2.19/Documentation/usage-big-page#advanced-command-line-options-for-lilypond
>  
> <http://lilypond.org/doc/v2.19/Documentation/usage-big-page#advanced-command-line-options-for-lilypond>
> Note for backend svg output: LilyPond’s default fonts (LilyPond Serif, 
> LilyPond Sans Serif and LilyPond Monospace) are just local font aliases. 
> Therefore, when using the backend svg command you must explicitly define the 
> default fonts in your source file;
> 
Thanks James, I hadn’t seen that explanation and workaround.

It still seems like it would be better if these local aliases didn’t make it 
into the svg files by default (when fonts are not user specified).  Seems like 
LilyPond's svg backend code could simply substitute:

“serif” for “LilyPond Serif”
“sans-serif” for “LilyPond Sans Serif”
“monospace” for “LilyPond Monospace”

That would produce svgs that had valid defaults and met expectations, svgs like 
those produced by 2.18.

(Well, instead of “serif” in 2.18 you would get "Century Schoolbook L” but I 
think “serif” is the better default.  Or we could specify both a specific font 
and a generic fallback like "TeX Gyre Schola, serif”.  That’s an option with 
the svg font-family property.)

So this seems like a regression to me, or at least a good feature request.

-Paul