Re: Replace `-dgs-load-fonts' to `--bigpdfs' in lilypond-book (issue 300280043 by truer...@gmail.com)
>> I've just tested successfully the following method, except item 1, >> which I've executed manually. [...] > > I've tried this way. [...] Thank you for your thorough testing, which obviously covers more situations than my limited tries. BTW, I see that your `extractpdfmark' tool has already reached version 1.0.1 – congratulations! https://github.com/trueroad/extractpdfmark Do you have time to integrate this into lilypond in the near future? Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 4988 straight-flags partly wrong claculated (issue 307600043 by thomasmorle...@gmail.com)
LGTM https://codereview.appspot.com/307600043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Add Greek and Cyrillic glyph aliases (issue 316800043 by truer...@gmail.com)
When you build current LilyPond, some TeX Gyre fonts are required. They are installed in LilyPond's directory. e.g. /usr/share/lilypond/current/fonts/otf Do you think that URW fonts should be installed in the same directory? Good question. Maybe yes. Or maybe a configuration option? https://codereview.appspot.com/316800043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Issue 4988 straight-flags partly wrong claculated (issue 307600043 by thomasmorle...@gmail.com)
Reviewers: , Description: Issue 4988 straight-flags partly wrong claculated The angles for straight-flags at down- and up-pointing stems are now accurately respected. This will cause some slight changes in the reg-tests. Please review this at https://codereview.appspot.com/307600043/ Affected files (+7, -4 lines): M scm/flag-styles.scm Index: scm/flag-styles.scm diff --git a/scm/flag-styles.scm b/scm/flag-styles.scm index 2b52f44cb23516eb2ce7924dda97ac37b376231c..82a21be3035f4c14a7cb5591405c53f9b44f125a 100644 --- a/scm/flag-styles.scm +++ b/scm/flag-styles.scm @@ -90,10 +90,13 @@ All lengths are scaled according to the font size of the note." (thickness-offset (cons 0 (* -1 thickness dir))) (spacing (* -1 flag-spacing factor dir )) (start (cons (- half-stem-thickness) (* half-stem-thickness dir))) - (points (list start - flag-end - (offset-add flag-end thickness-offset) - (offset-add start thickness-offset))) + (raw-points + (list + '(0 . 0) + flag-end + (offset-add flag-end thickness-offset) + thickness-offset)) + (points (map (lambda (coord) (offset-add coord start)) raw-points)) (stencil (ly:round-filled-polygon points half-stem-thickness)) ;; Log for 1/8 is 3, so we need to subtract 3 (flag-stencil (buildflag stencil (- log 3) stencil spacing)) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Add Greek and Cyrillic glyph aliases (issue 316800043 by truer...@gmail.com)
Reviewers: lemzwerg, Message: On 2016/10/25 06:29:32, lemzwerg wrote: LGTM. Note, however, that the new versions of URW fonts are considered problematic, since they differ too much from the original set of fonts (especially metrics) – this is the very reason that currently TeXLive doesn't use them. https://www.preining.info/blog/2015/08/sins-of-the-past/ Admittedly, this problem doesn't directly affect lilypond, especially if it delivers the fonts in a bundled form. Thank you for your information. URW fonts seem to have been released several times. http://git.ghostscript.com/?p=urw-core35-fonts.git;a=summary I do not know whether or not those problems have been resolved. However, there are still some problems. e.g. http://bugs.ghostscript.com/show_bug.cgi?id=697058 So I think that LilyPond main font should be TeX Gyre fonts. I'd like to use URW fonts in order to complement the missing glyphs. This patch is only to set the font alias for the missing glyphs. When you build current LilyPond, some TeX Gyre fonts are required. They are installed in LilyPond's directory. e.g. /usr/share/lilypond/current/fonts/otf Do you think that URW fonts should be installed in the same directory? Description: Add Greek and Cyrillic glyph aliases LilyPond default fonts (TeX Gyre) do not have Greek and Cyrillic glyphs. New URW 35 fonts which are contained in Ghostscript 9.20 have them. This commit makes that when you have the new URW fonts, you can use their Greek and Cyrillic glyphs as default fonts. Please review this at https://codereview.appspot.com/316800043/ Affected files (+32, -0 lines): M mf/00-lilypond-fonts.conf.in Index: mf/00-lilypond-fonts.conf.in diff --git a/mf/00-lilypond-fonts.conf.in b/mf/00-lilypond-fonts.conf.in index 899db67172e216fbc91da71cb6aa52dcd15a8f34..dc2c464f44a749907ef9a6a86dfa710ff595dfc4 100644 --- a/mf/00-lilypond-fonts.conf.in +++ b/mf/00-lilypond-fonts.conf.in @@ -11,10 +11,21 @@ LilyPond Serif + TeX Gyre Schola + + C059 + Century SchoolBook URW + Century Schoolbook L + DejaVu Serif + serif @@ -22,10 +33,20 @@ LilyPond Sans Serif + TeX Gyre Heros + + Nimbus Sans + Nimbus Sans L + DejaVu Sans + sans-serif @@ -33,10 +54,21 @@ LilyPond Monospace + TeX Gyre Cursor + + Nimbus Mono PS + Nimbus Mono + Nimbus Mono L + DejaVu Sans Mono + monospace ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Gub is failing to build fontconfig-2.12.1
> The host machine is 64 bit debian stable I believe. > This is the error I am getting: > > ail of target/mingw/log/fontconfig.log > Alternatively, you may set the environment variables FREETYPE_CFLAGS > and FREETYPE_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. [...snip...] > > I checked and freetype was in fact installed. I don't know why it can't see > the .pc file. If I understand correctly, it is due to building order. If you build zlib before pkg-config, zlib does not generate .pc file. FreeType's .pc file depends on zlib's .pc file. pkg-config found FreeType but did not found zlib. So it failed for FreeType. Would you see the whole of log file `target/mingw/log/fontconfig.log` ? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Akkordzither-tab in lilypond proper?
Am 22.10.2016 um 16:29 schrieb Simon Albrecht: On 22.10.2016 10:00, Thomas Morley wrote: Hi, I recently mentioned my work to create the very special notation for Akkordzither. http://lists.gnu.org/archive/html/lilypond-user/2016-10/msg00349.html I consider to put it in the source, probably in the same way we have gregorian.ly. I think Gregorian Chant is still far more common a usecase than music for Akkordzither. Well, that depends. I know no one that uses Gregorian Chant, but at least some people that play Akkordzither ;-) Just my 2 cents, Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Gub is failing to build fontconfig-2.12.1
Jeremiah Benham writes: > The host machine is 64 bit debian stable I believe. > This is the error I am getting: > > ail of target/mingw/log/fontconfig.log > Alternatively, you may set the environment variables FREETYPE_CFLAGS > and FREETYPE_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > Command barfed: cd > /home/jjbenham/src/gub/target/mingw/build/fontconfig-2.12.1 && chmod +x > /home/jjbenham/src/gub/target/mingw/src/fontconfig-2.12.1/configure && sh > /home/jjbenham/src/gub/target/mingw/src/fontconfig-2.12.1/configure > --prefix=/usr --cache-file=config.cache --enable-shared --disable-static > --disable-silent-rules --build=i686-linux --host=i686-mingw32 > --target=i686-mingw32 --prefix=/usr --sysconfdir=/usr/etc > --includedir=/usr/include --infodir=/usr/share/info --mandir=/usr/share/man > --libdir=/usr/lib --with-arch=i686-mingw32 > --with-freetype-config="/home/jjbenham/src/gub/target/mingw/root/usr/cross/bin/freetype-config > --prefix=/home/jjbenham/src/gub/target/mingw/root/usr " > Tail of target/mingw/log/fontconfig.log > > > I checked and freetype was in fact installed. I don't know why it can't see > the .pc file. Wrong architecture? Of either libfreetype-dev _or_ fontconfig? -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
