Issue 4591: Fix font-name overriding

Issue 4591: Fix font-name overriding

Issue 4591 / 5: NR: Add font-name description

    This commit addsing font-name description.

Issue 4591 / 4: NR: Enhance font-name overriding sample

    font-name can be described
    a comma separated list of font families and
    a whitespace separated list of font styles (shape, series etc.).

Issue 4591 / 3: Fix font-name overriding wrong name

    Some font family do not exist.
    This commit replaces them with correct font family names.

Issue 4591 / 2: Fix font-name overriding deprecated name

    Generic font family alias `Sans' is deprecated.

    This commit replaces it with `LilyPond Sans Serif'
    that is a font family alias of LilyPond's default sans serif font.

Issue 4591 / 1: Fix font-name overriding `Times New Roman'

    A comma is required
    for font family name "Times New Roman"'s explicit termination.
    If there is no comma, Pango interpret "Times New Roman" as
    "Times New" family with "Roman" style.

[pkx, 2015-09-07 14:34:48]

Suggested change to the English wording.

https://codereview.appspot.com/262330043/diff/1/Documentation/notation/text.i...
File Documentation/notation/text.itely (right):

https://codereview.appspot.com/262330043/diff/1/Documentation/notation/text.i...
Documentation/notation/text.itely:1547: If first font family in the list exists,
it is used basically.
@var{font-name} can be described using a comma-separate list for font
@q{families} and a white-space separated list for font @q{styles}.  As long as
the @q{family} in the list is installed it will be used, otherwise the
@emph{next} font in the list will be used instead.

[trueroad, 2015-09-07 15:12:27]

Change English wording

[trueroad, 2015-09-07 15:16:29]

I've updated the patch.

https://codereview.appspot.com/262330043/diff/1/Documentation/notation/text.i...
File Documentation/notation/text.itely (right):

https://codereview.appspot.com/262330043/diff/1/Documentation/notation/text.i...
Documentation/notation/text.itely:1547: If first font family in the list exists,
it is used basically.
On 2015/09/07 14:34:48, pkx wrote:
> @var{font-name} can be described using a comma-separate list for font
> @q{families} and a white-space separated list for font @q{styles}.  As long as
> the @q{family} in the list is installed it will be used, otherwise the
> @emph{next} font in the list will be used instead.

Thank you.

Because the font is selected from the list for each glyph, I've changed a
little.

[thomasmorley651, 2015-09-07 21:11:49]

Some nitpick, see below.

Otherwise
LGTM

https://codereview.appspot.com/262330043/diff/20001/Documentation/snippets/ne...
File Documentation/snippets/new/unfretted-headword.ly (right):

https://codereview.appspot.com/262330043/diff/20001/Documentation/snippets/ne...
Documentation/snippets/new/unfretted-headword.ly:119: \set Score.markFormatter  
  =  #format-mark-box-numbers
Here and below: Do we really want several spacers before "="?

[dak, 2015-09-07 21:31:46]

https://codereview.appspot.com/262330043/diff/20001/Documentation/snippets/ne...
File Documentation/snippets/new/unfretted-headword.ly (right):

https://codereview.appspot.com/262330043/diff/20001/Documentation/snippets/ne...
Documentation/snippets/new/unfretted-headword.ly:119: \set Score.markFormatter  
  =  #format-mark-box-numbers
On 2015/09/07 21:11:48, thomasmorley651 wrote:
> Here and below: Do we really want several spacers before "="?

Well, it's commit
commit 13da8b27aabc5d5a752d00ed1e2b99ad20f0f264
Author: David Kastrup <dak@gnu.org>
Date:   Mon Oct 29 16:25:02 2012 +0100

    Rerun scripts/auxiliar/update-with-convert-ly.sh

for version 2.17.6 which made a hash of the indentations:
@@ -126,9 +126,9 @@ ViolinSolo = \relative c' {
   \voiceOne
 
   \set Score.markFormatter     =  #format-mark-box-numbers
-  \override Score.VoltaBracket #'font-name                  = #"sans"
-  \override Score.VoltaBracket #'extra-offset               = #'(0 . 1)
-  \override SpacingSpanner     #'uniform-stretching         = ##t
+  \override Score.VoltaBracket.font-name                  = #"sans"
+  \override Score.VoltaBracket.extra-offset               = #'(0 . 1)
+  \override SpacingSpanner.uniform-stretching         = ##t
 
 
   %% Measure 1
@@ -220,7 +220,7 @@ ViolinSolo = \relative c' {
       \new Staff \ViolinSolo
     >>
 
-    \override Score.Rest #'transparent = ##t
+    \override Score.Rest.transparent = ##t
     \set Score.defaultBarType          = "-"
   >>
 
Conversions like that lead to the question how much sense there is in this sort
of block aligns in the first place.

[thomasmorley651, 2015-09-07 21:39:16]

https://codereview.appspot.com/262330043/diff/20001/Documentation/snippets/ne...
File Documentation/snippets/new/unfretted-headword.ly (right):

https://codereview.appspot.com/262330043/diff/20001/Documentation/snippets/ne...
Documentation/snippets/new/unfretted-headword.ly:119: \set Score.markFormatter  
  =  #format-mark-box-numbers
On 2015/09/07 21:31:45, dak wrote:
> On 2015/09/07 21:11:48, thomasmorley651 wrote:
> > Here and below: Do we really want several spacers before "="?
> 
> Well, it's commit
> commit 13da8b27aabc5d5a752d00ed1e2b99ad20f0f264
> Author: David Kastrup <mailto:dak@gnu.org>
> Date:   Mon Oct 29 16:25:02 2012 +0100
> 
>     Rerun scripts/auxiliar/update-with-convert-ly.sh
> 
> for version 2.17.6 which made a hash of the indentations:
> @@ -126,9 +126,9 @@ ViolinSolo = \relative c' {
>    \voiceOne
>  
>    \set Score.markFormatter     =  #format-mark-box-numbers
> -  \override Score.VoltaBracket #'font-name                  = #"sans"
> -  \override Score.VoltaBracket #'extra-offset               = #'(0 . 1)
> -  \override SpacingSpanner     #'uniform-stretching         = ##t
> +  \override Score.VoltaBracket.font-name                  = #"sans"
> +  \override Score.VoltaBracket.extra-offset               = #'(0 . 1)
> +  \override SpacingSpanner.uniform-stretching         = ##t
>  
>  
>    %% Measure 1
> @@ -220,7 +220,7 @@ ViolinSolo = \relative c' {
>        \new Staff \ViolinSolo
>      >>
>  
> -    \override Score.Rest #'transparent = ##t
> +    \override Score.Rest.transparent = ##t
>      \set Score.defaultBarType          = "-"
>    >>
>  
> Conversions like that lead to the question how much sense there is in this
sort
> of block aligns in the first place.

At least in this case I'd be more happy with _one_ space before "=".
I don't like this sort of block align, but ofcourse it's only me...

[trueroad, 2015-09-08 13:05:56]

Clean up

[trueroad, 2015-09-08 13:08:07]

I've added cleaning up etc.

Issue 4591 / 6: Clean up
    Alignment spacing only.

[trueroad, 2015-09-10 11:16:54]

Change some term

[trueroad, 2015-09-10 12:18:26]

I've noticed that LilyPond' font-family and Pango/Fontconfig's font family are
quite a different thing.
To prevent confusion, I've changed some term.

[trueroad, 2015-09-10 13:21:41]

Issue 4591 / 6: Clean up

    Alignment spacing only.

Issue 4591 / 5: NR: Add font-name description

    This commit adds font-name description.

Issue 4591 / 4: NR: Enhance font-name overriding sample

    font-name can be described using a comma-separated list of fonts
    and a white-space separated list of styles (shape, series etc.).

Issue 4591 / 3: Fix font-name overriding wrong name

    Some font names do not exist.
    This commit replaces them with correct font names.

Issue 4591 / 2: Fix font-name overriding deprecated name

    FontConfig's generic font family alias `sans' is deprecated.

    This commit replaces it with `LilyPond Sans Serif'
    that is a font alias of LilyPond's default sans serif font.

Issue 4591 / 1: Fix font-name overriding `Times New Roman'

    A comma is required
    for font name "Times New Roman"'s explicit termination.
    If there is no comma, Pango interpret "Times New Roman" as
    "Times New" family with "Roman" style.

[trueroad, 2015-09-17 14:41:12]

I've uploaded to staging.

Issue 4591 / 1: Fix font-name overriding `Times New Roman'
author    Masamichi Hosoda <trueroad@trueroad.jp>
          Mon, 7 Sep 2015 11:04:50 +0000 (20:04 +0900)
committer Masamichi Hosoda <trueroad@trueroad.jp>
          Thu, 17 Sep 2015 14:28:14 +0000 (23:28 +0900)
commit    64d2c3f619587207c1dcd22f573b9ff4ff34d04f

Issue 4591 / 2: Fix font-name overriding deprecated name
author    Masamichi Hosoda <trueroad@trueroad.jp>
          Mon, 7 Sep 2015 11:59:19 +0000 (20:59 +0900)
committer Masamichi Hosoda <trueroad@trueroad.jp>
          Thu, 17 Sep 2015 14:28:14 +0000 (23:28 +0900)
commit    1e8a9855c7b9455b6bb95c6894b79eead3f5f7b3

Issue 4591 / 3: Fix font-name overriding wrong name
author    Masamichi Hosoda <trueroad@trueroad.jp>
          Mon, 7 Sep 2015 13:12:56 +0000 (22:12 +0900)
committer Masamichi Hosoda <trueroad@trueroad.jp>
          Thu, 17 Sep 2015 14:28:15 +0000 (23:28 +0900)
commit    d0980c892d79010a9506aa5b7da504181ba5b632

Issue 4591 / 4: NR: Enhance font-name overriding sample
author    Masamichi Hosoda <trueroad@trueroad.jp>
          Mon, 7 Sep 2015 13:30:23 +0000 (22:30 +0900)
committer Masamichi Hosoda <trueroad@trueroad.jp>
          Thu, 17 Sep 2015 14:28:15 +0000 (23:28 +0900)
commit    15c207fe1e0c7a70184ec82e9f060d3ae599326d

Issue 4591 / 5: NR: Add font-name description
author    Masamichi Hosoda <trueroad@trueroad.jp>
          Mon, 7 Sep 2015 13:49:14 +0000 (22:49 +0900)
committer Masamichi Hosoda <trueroad@trueroad.jp>
          Thu, 17 Sep 2015 14:28:16 +0000 (23:28 +0900)
commit    c6035c9f68d892a37855edf6acb5e9d0fbec7267

Issue 4591 / 6: Clean up
author    Masamichi Hosoda <trueroad@trueroad.jp>
          Tue, 8 Sep 2015 12:57:06 +0000 (21:57 +0900)
committer Masamichi Hosoda <trueroad@trueroad.jp>
          Thu, 17 Sep 2015 14:28:16 +0000 (23:28 +0900)
commit    2a4c5137870acf1b1fd2f3307d98973a52cfc8b9