Re: Doc: more comprehensive documentation of layout block (2560) (issue 6354085)

http://codereview.appspot.com/6354085/diff/1/Documentation/notation/spacing.itely File Documentation/notation/spacing.itely (right): http://codereview.appspot.com/6354085/diff/1/Documentation/notation/spacing.itely#newcode1098 Documentation/notation/spacing.itely:1098: If this block: On

utf-8-strings

Hi, together with Arnold I worked on a method how to compress or stretch a text, limiting it to the space between characters, i.e. the letters itself shouldn't be scaled. (Comes out of a discussion at the german LilyPond-Forum: http://www.lilypondforum.de/index.php?topic=1152.0 ) The difficulty

Re: utf-8-strings

Thomas Morley thomasmorle...@googlemail.com writes: Hi, together with Arnold I worked on a method how to compress or stretch a text, limiting it to the space between characters, i.e. the letters itself shouldn't be scaled. (Comes out of a discussion at the german LilyPond-Forum:

New French PO file for 'lilypond' (version 2.15.41)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the French team of translators. The file is available at: http://translationproject.org/latest/lilypond/fr.po (We can arrange things so

Re: utf-8-strings

2012/7/8 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: Hi, together with Arnold I worked on a method how to compress or stretch a text, limiting it to the space between characters, i.e. the letters itself shouldn't be scaled. (Comes out of a discussion at

Re: utf-8-strings

Hi Harm, I managed to drop about 300 lines, reducing it to a quarter of the original. Unfortunately, I'm getting Invalid UTF-8 string... warnings when I run your revised file. (I don't with the original...) -David ___ lilypond-devel mailing list

Re: utf-8-strings

2012/7/8 David Nalesnik david.nales...@gmail.com: Hi Harm, I managed to drop about 300 lines, reducing it to a quarter of the original. Unfortunately, I'm getting Invalid UTF-8 string... warnings when I run your revised file. (I don't with the original...) -David Hi David, are you

Re: utf-8-strings

Thomas Morley thomasmorle...@googlemail.com writes: 2012/7/8 David Kastrup d...@gnu.org: This can basically be done using charsets. I tried doing this with regexps, but curiously enough, in contrast to Guile proper, those appear to be already utf-8 aware, so #(use-modules (ice-9 regex))

Re: utf-8-strings

Thomas Morley thomasmorle...@googlemail.com writes: 2012/7/8 David Nalesnik david.nales...@gmail.com: Hi Harm, I managed to drop about 300 lines, reducing it to a quarter of the original. Unfortunately, I'm getting Invalid UTF-8 string... warnings when I run your revised file. (I don't

Re: utf-8-strings

2012/7/8 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: 2012/7/8 David Kastrup d...@gnu.org: This can basically be done using charsets. I tried doing this with regexps, but curiously enough, in contrast to Guile proper, those appear to be already utf-8

2.15.41 Regtests

I've been doing a bit of work with my pixel comparator, and now have a mechanism to generate a web page from commented results. Running the checker on 15.41 versus 15.40 gives about 100 changed files, most of which are subtle changes, some of which come from a changed forte mark. I've got a

Re: utf-8-strings

Thomas Morley thomasmorle...@googlemail.com writes: Seems I have to extend my scheme-vocabulary. I didn't know/remember `append-map' and `string-concatenate'. Picked them from the Guile manuals. I really have to learn more of the predefined guile-procedures. (new-args (list-join

Cross-staff stems again

As I said in an earlier mail, I'd like to include the cross-staff stem functions that Pavel developed as a part of standard lily functionality. It relies on quite a bit of scheme and a final function like this: crossStaff = #(define-music-function (parser location notes) (ly:music?) #{

Re: 2.15.41 Regtests

Phil Holmes em...@philholmes.net writes: I've been doing a bit of work with my pixel comparator, and now have a mechanism to generate a web page from commented results. Running the checker on 15.41 versus 15.40 gives about 100 changed files, most of which are subtle changes, some of which

Re: utf-8-strings

2012/7/8 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: Seems I have to extend my scheme-vocabulary. I didn't know/remember `append-map' and `string-concatenate'. Picked them from the Guile manuals. I know. I tend to define my own helpers if I don't find sth

Re: utf-8-strings

Thomas Morley thomasmorle...@googlemail.com writes: 2012/7/8 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: Seems I have to extend my scheme-vocabulary. I didn't know/remember `append-map' and `string-concatenate'. Picked them from the Guile manuals. I

bug with 2.15.39 fixed with 2.15.42: good job but no reg test

The following snippet does not give 1/32 notes grouped together as expected with 2.15.39: \new Staff { \clef treble \key bf \major \time 3/4 \set Score.beamExceptions = #'( ( end . ( ( (1 . 32) . (4 4 4 4

Re: Cross-staff stems again

Phil Holmes wrote Sunday, July 08, 2012 4:43 PM As I said in an earlier mail, I'd like to include the cross-staff stem functions that Pavel developed as a part of standard lily functionality. It relies on quite a bit of scheme and a final function like this: crossStaff =

Re: Cross-staff stems again

Phil Holmes wrote Sunday, July 08, 2012 9:13 PM From: Trevor Daniels t.dani...@treda.co.uk To: Phil Holmes em...@philholmes.net; Devel lilypond-devel@gnu.org Sent: Sunday, July 08, 2012 9:05 PM Subject: Re: Cross-staff stems again music-functions-init.ly looks good. You'll need to add a

Re: utf-8-strings

On Sun, Jul 8, 2012 at 8:00 AM, David Kastrup d...@gnu.org wrote: Thomas Morley thomasmorle...@googlemail.com writes: 2012/7/8 David Nalesnik david.nales...@gmail.com: Hi Harm, I managed to drop about 300 lines, reducing it to a quarter of the original. Unfortunately, I'm

Re: utf-8-strings

2012/7/8 David Nalesnik david.nales...@gmail.com: On Sun, Jul 8, 2012 at 8:00 AM, David Kastrup d...@gnu.org wrote: Thomas Morley thomasmorle...@googlemail.com writes: 2012/7/8 David Nalesnik david.nales...@gmail.com: Hi Harm, I managed to drop about 300 lines, reducing it to a

Re: utf-8-strings

David Nalesnik david.nales...@gmail.com writes: On Sun, Jul 8, 2012 at 8:00 AM, David Kastrup d...@gnu.org wrote: Thomas Morley thomasmorle...@googlemail.com writes: 2012/7/8 David Nalesnik david.nales...@gmail.com: Hi Harm,  I managed to drop about 300

Re: utf-8-strings

2012/7/9 David Kastrup d...@gnu.org: David Nalesnik david.nales...@gmail.com writes: On Sun, Jul 8, 2012 at 8:00 AM, David Kastrup d...@gnu.org wrote: Thomas Morley thomasmorle...@googlemail.com writes: 2012/7/8 David Nalesnik david.nales...@gmail.com: Hi Harm,

Re: utf-8-strings

Thomas Morley thomasmorle...@googlemail.com writes: An observation: Setting export LANG=en_US and compiling the file gives: GNU LilyPond 2.15.42 Processing `utf-8-strings-rev-03.ly' Parsing... (process:10496): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

Re: utf-8-strings

On Sun, Jul 8, 2012 at 6:21 PM, Thomas Morley thomasmorle...@googlemail.com wrote: 2012/7/9 David Kastrup d...@gnu.org: David Nalesnik david.nales...@gmail.com writes: On Sun, Jul 8, 2012 at 8:00 AM, David Kastrup d...@gnu.org wrote: Thomas Morley thomasmorle...@googlemail.com

Re: utf-8-strings

David Nalesnik david.nales...@gmail.com writes: out/bin/lilypond scheme-sandbox GNU LilyPond 2.15.42 Processing `/usr/local/tmp/lilypond/out/share/lilypond/current/ly/scheme-sandbox. ly' Parsing... guile (setlocale LC_CTYPE) en_US.UTF-8 guile

New Esperanto PO file for 'lilypond' (version 2.15.41)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the Esperanto team of translators. The file is available at: http://translationproject.org/latest/lilypond/eo.po (We can arrange things so

PATCH: Countdown to 20120710

For 20:00 MDT Tuesday July 10th Documentation: Issue 2557 http://code.google.com/p/lilypond/issues/detail?id=2557: alignAboveContext was removed from the NR - R 6353079 http://codereview.appspot.com/6353079/ Issue 2560 http://code.google.com/p/lilypond/issues/detail?id=2560:

Re: Doc: document \on-the-fly (2579) (issue 6347062)

LGTM http://codereview.appspot.com/6347062/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: bug with 2.15.39 fixed with 2.15.42: good job but no reg test

commit f6b1f6ebcd527e6262add9c9cf3e4df5b3e5d63f Refine mid-measure beams in 3/4 time; Issue 2566 includes several regtests. Are you sure this is not covered? I have looked at the different *beam* regtests but let me look at this particular commit. I will tell you. Thanks, Frédéric

Re: Doc: more comprehensive documentation of layout block (2560) (issue 6354085)

I'm content to take your word for the changes, but our general custom these days is to upload a new draft once edits are made. I mention this mainly so that you can check how git-cl handles this; it should be easy but it's been a while since I've done it myself.

Re: Document use of alignAboveContext and alignBelowContext (issue 6353079)

LGTM. Ignore my other message that talked about using git-cl to upload an edited patch; I hadn't noticed that you did that here. http://codereview.appspot.com/6353079/diff/6001/Documentation/notation/changing-defaults.itely File Documentation/notation/changing-defaults.itely (right):