On 2015/03/26 17:21:38, david.nalesnik wrote:
Aside from whitespace issue, LGTM. I assume this could be fixed when
pushing,
and there's no need to put this back on review?
Thanks, that works for me, but someone just let me know if I should
submit another patch for review for this.
https://c
https://codereview.appspot.com/220090043/diff/1/input/regression/staff-ledger-positions-dotted-notes.ly
File input/regression/staff-ledger-positions-dotted-notes.ly (right):
https://codereview.appspot.com/220090043/diff/1/input/regression/staff-ledger-positions-dotted-notes.ly#newcode2
input/reg
https://codereview.appspot.com/217260043/diff/1/scm/output-lib.scm
File scm/output-lib.scm (right):
https://codereview.appspot.com/217260043/diff/1/scm/output-lib.scm#newcode165
scm/output-lib.scm:165: (use-modules (ice-9 pretty-print))
On 2015/03/25 13:59:20, david.nalesnik wrote:
On 2015/03/2
Hello,
triggered by a discussion on -user I have begun to implement a new
\language command which in addition to setting the note names input
language also automatically translates the default text fields in
tagline and table of contents, or may be used for both tasks separately.
By now, with
Hmmm... it seems that these changes have not yet shown up on the website.
Anyone know what the story is? They are just changes to css files and
adding two images. After they land there should be a green background in
both top corners (not just the top left).
Thanks,
-Paul
--
View this messag
Aside from whitespace issue, LGTM. I assume this could be fixed when
pushing, and there's no need to put this back on review?
https://codereview.appspot.com/220090043/diff/1/input/regression/staff-ledger-positions-dotted-notes.ly
File input/regression/staff-ledger-positions-dotted-notes.ly (rig
Urs Liska writes:
> The issues discussed in this thread have quite diversified:
>
> - Updating GUB to a newer Ghostscript
> - Ligatures not being produced on all platforms
> - Updating Pango which solved this
> - Pango picking system fonts, resulting in unpredictable output
> - thinking about cho
Am 26.03.2015 um 16:12 schrieb David Kastrup:
Masamichi HOSODA writes:
I've succeed GUB's ``make lilypond'' by pango-1.28.3 in this branch.
https://github.com/trueroad/gub/tree/pango-1.28
I've checked again.
I've installed DejaVuSans to all environments.
linux-64 binary on Ubuntu 14.04
Masamichi HOSODA writes:
> I've succeed GUB's ``make lilypond'' by pango-1.28.3 in this branch.
> https://github.com/trueroad/gub/tree/pango-1.28
>
> I've checked again.
> I've installed DejaVuSans to all environments.
>
> linux-64 binary on Ubuntu 14.04 LTS 64 bit:
> linux-x86 binary on Ubun
Am 26.03.2015 um 15:55 schrieb Masamichi HOSODA:
I've succeed GUB's ``make lilypond'' by pango-1.28.3 in this branch.
https://github.com/trueroad/gub/tree/pango-1.28
I've checked again.
I've installed DejaVuSans to all environments.
linux-64 binary on Ubuntu 14.04 LTS 64 bit:
linux-x86
I've succeed GUB's ``make lilypond'' by pango-1.28.3 in this branch.
https://github.com/trueroad/gub/tree/pango-1.28
I've checked again.
I've installed DejaVuSans to all environments.
linux-64 binary on Ubuntu 14.04 LTS 64 bit:
linux-x86 binary on Ubuntu 14.04 LTS 64 bit:
linux-x86 binary o
Am 2015-03-26 um 00:11 schrieb Marc Hohl :
> Is there any recommendation whether to use sans serif fonts for chord names?
> I used the text font (serif) in the latest projects of mine where chord
> symbols were needed.
I don’t know, but I tried several fonts for chord names, and if you use a s
12 matches
Mail list logo
