URW++ has been released URW++ core 35 fonts 2017-07-20.
It has some bugfixes.
This commit makes configure script can find latest URW++ OTF files (2017-07-20).
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=1f28a6fcd2176256a995db907d9ffe6e1b9b83e9
Doc: add comment about automatically generated documentation
This is mainly for translators. See this discussion:
http://lilypond-translations.3384276.n2.nabble.com/Doubt-about-ref-Align-in-text-itely-of-the-notationn-manual-td7572987.html
Masamichi Hosoda [Tue, 13 Jun 2017 12:16:45 +0000 (21:16 +0900)]
Issue 5147: Add whether to use OTF feature depending on Pango version
Issue 1388 requires Pango 1.38+ for using OpenType font feature.
However, LilyDev 4.1 has Pango 1.36.8.
So it cannot compile Issue 1388.
This commit makes LilyPond can be configured
without OpenType font feature if Pango is old.
Therefore, LilyPond become to be able to compile
even by LilyDev 4.1 that has old Pango.
However, the binary that compiled by LilyDev 4.1
cannot use OpenType font feature.
It is required Pango 1.38+ if you'd like to use the feature.
Paul Morris [Mon, 22 May 2017 19:02:52 +0000 (15:02 -0400)]
lilypond-manuals.css: edit color scheme and some spacing
Simplifies the color scheme. Main motivation is to avoid fully
saturated bright colors on code box borders, which distract from
the content, and to use stronger/darker colors in table of
contents sidebars instead of lighter pastel colors.
Affects table of contents sidebars, borders around code boxes,
footers, note boxes, advanced boxes, main/top page for a manual,
and grey navigation bars/rows/strips.
David Kastrup [Mon, 12 Jun 2017 18:33:40 +0000 (20:33 +0200)]
Issue 5146: Don't use \line in the implementation of \concat
It doesn't really make any sense to override word-space temporarily
and it does not make sense to heed text-direction when putting together
stuff without actual word boundaries.
Namely: ad-hoc written functions (probably most useful when written
using macros) can be employed as markup commands when preceded with $
as long as they have a suitable markup command signature attached.
This feature is mainly added for consistency with music functions.
David Nalesnik [Thu, 27 Apr 2017 17:13:30 +0000 (12:13 -0500)]
Issue 5127: Implement extra-offset for system positioning
Add the property 'extra-offset to 'line-break-system-details.
It is possible to position systems absolutely using the
properties 'X-offset and 'Y-offset of 'line-break-system-details.
Placement using 'Y-offset, in particular, often requires
considerable trial and error, since it is reckoned from the top
of the usable space.
To remedy this, an 'extra-offset property allows easy movement of
systems relative to where they currently are on the page--whether
there through default or absolute positioning.
This property supports displacements in both axes, though
movement in the Y direction is more generally useful.
System separators will be properly positioned. (Thanks go to Thomas
Morley.)
Antonio Ospite [Sat, 19 Nov 2016 14:27:15 +0000 (15:27 +0100)]
Issue 5130 Fix the encoding of the PDF metadata when using guile-2.0
Postscript files are encoded in Latin1, but PDF metadata has to be
encoded in UTF-16BE.
ly:encode-string-for-pdf takes care of that but it was not working
properly with guile-2.0 because the internal representation of strings
in guile-2.0 has changed and the actual destination encoding has to be
specified explicitly, especially when it's different from the current
locale.
Passing the encoded metadata as Latin1 corresponds to pass its raw byte
representation, and this is enough to make things work.
This also gets rid of a misleading warning:
"`scm_take_str' is deprecated. Use scm_take_locale_stringn instead."
This change is compatible with guile-1.8 so the FIXME comment in
lily/pdf-scheme.cc has been removed. A note was added to
scm/framework-ps.scm to suggest a possible implementation in scheme of
ly_encode_for_pdf(), just in case of a possible future cleanup.
Issue 5128: Prevent granados.ly image rotation in web.pdf
granados.ly used 'landscape symbol for page settings.
As a result, granados.pdf which was generated from granados.ly
contained `/Rotate 90` that is not supported by XeTeX's PDFs including.
So the image in web.pdf which was generated by XeTeX
was rotated 90 degree counter-clockwise.
This commit makes the page settings does not have 'landscape symbol.
We append `landscape` to the name of the paper size itself.
So granados.ly image rotation in web.pdf is prevented.
Amir Czwink [Thu, 4 May 2017 22:13:43 +0000 (00:13 +0200)]
Slashed Half-flat and add. scales for Arabic music
-Introduced a glyph list so that the slashed half-flat is used
(always) instead of the mirrored one (the latter is never used
for Arabic sheet music)
-Added two scales (Maqamat) of major importance for Arabic music
For arabic music score writing:
-Introduced new glyph list, so that by default the slashed
half-flat is used instead of the mirrored half-flat, which isn't
used in Arabic score writing. This makes the use of the cumbersome
\dwn symbol needless and obsolete
-Added Hijaz and Hijaz-Kar maqamat
Federico Bruni [Wed, 3 May 2017 16:33:04 +0000 (18:33 +0200)]
Doc-cs: remove broken links to missing czech PDF files
Czech PDFs are not built so we should provide working links
to the up-to-date english PDF files. Discussed here:
http://lists.gnu.org/archive/html/bug-lilypond/2017-02/msg00012.html
Thomas Morley [Sat, 22 Apr 2017 17:48:13 +0000 (19:48 +0200)]
Issue 5123 Improve elbowed-hairpin
Let the lines be printed by the new make-connected-line-procedure,
using ly:line-interface::line. The new stencil now reacts on
overrides for style and dash-period/fraction.
Not closing Hairpins created by elbowed-hairpin are possible now.
Single disadvantage: The point-list needs to have (0 . 0) first,
if a closing Hairpin is wished.
The previous used make-connected-path did that automatically and
thus was not flexible enough.
Give the final stencil proper extents.
Cleanup, more descriptive naming, extent docstring.