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): http://co

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. http://codereview.appspot.com/635

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: 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

PATCH: Countdown to 20120710

For 20:00 MDT Tuesday July 10th Documentation: Issue 2557 : alignAboveContext was removed from the NR - R 6353079 Issue 2560 : Doc

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 t

Re: utf-8-strings

David Nalesnik 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> > >

Re: utf-8-strings

On Sun, Jul 8, 2012 at 6:21 PM, Thomas Morley wrote: > 2012/7/9 David Kastrup : > > David Nalesnik writes: > > > >> On Sun, Jul 8, 2012 at 8:00 AM, David Kastrup wrote: > >> > >> > >> Thomas Morley writes: > >> > >> > 2012/7/8 David Nalesnik : > >> >> Hi Harm, > >> >> > >>

Re: utf-8-strings

Thomas Morley 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() > > (process:10496):

Re: utf-8-strings

2012/7/9 David Kastrup : > David Nalesnik writes: > >> On Sun, Jul 8, 2012 at 8:00 AM, David Kastrup wrote: >> >> >> Thomas Morley writes: >> >> > 2012/7/8 David Nalesnik : >> >> Hi Harm, >> >> >> >>> I managed to drop about 300 lines, reducing >> >>> it to a quarter of

Re: utf-8-strings

David Nalesnik writes: > On Sun, Jul 8, 2012 at 8:00 AM, David Kastrup wrote: > > > Thomas Morley writes: > > > 2012/7/8 David Nalesnik : > >> Hi Harm, > >> > >>>  I managed to drop about 300 lines, reducing > >>> it to a quarter of the original. > >> >

Re: utf-8-strings

2012/7/8 David Nalesnik : > > > On Sun, Jul 8, 2012 at 8:00 AM, David Kastrup wrote: >> >> Thomas Morley writes: >> >> > 2012/7/8 David Nalesnik : >> >> Hi Harm, >> >> >> >>> I managed to drop about 300 lines, reducing >> >>> it to a quarter of the original. >> >> >> >> >> >> Unfortunately, I'm

Re: utf-8-strings

On Sun, Jul 8, 2012 at 8:00 AM, David Kastrup wrote: > Thomas Morley writes: > > > 2012/7/8 David Nalesnik : > >> 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 w

Re: Cross-staff stems again

Phil Holmes wrote Sunday, July 08, 2012 9:13 PM > From: "Trevor Daniels" > To: "Phil Holmes" ; "Devel" > 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 doc >> string. > > > I'm happy to document it in

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

Frédéric Bron writes: > 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 . > ( >

Re: Cross-staff stems again

- Original Message - From: "Trevor Daniels" To: "Phil Holmes" ; "Devel" 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 doc string. I'm happy to document it in the NR. Is this what you mean, or some

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 = > #(define-

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 4

Re: utf-8-strings

Thomas Morley writes: > 2012/7/8 David Kastrup : >> Thomas Morley 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

Re: utf-8-strings

2012/7/8 David Kastrup : > Thomas Morley 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 useful in the guile-manual in a s

Re: 2.15.41 Regtests

"Phil Holmes" 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 come from a chang

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?) #{ \overri

Re: utf-8-strings

Thomas Morley 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 args-rev " ")) >> >> lis

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 w

Re: utf-8-strings

2012/7/8 David Kastrup : > Thomas Morley writes: > >> 2012/7/8 David Kastrup : >>> >>> 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 reg

Re: utf-8-strings

Thomas Morley writes: > 2012/7/8 David Nalesnik : >> 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...) >> >> -Dav

Re: utf-8-strings

Thomas Morley writes: > 2012/7/8 David Kastrup : >> >> 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)) >> >> #(define (utf8-substring

Re: utf-8-strings

2012/7/8 David Nalesnik : > 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 sure? I teste

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 lis

Re: utf-8-strings

2012/7/8 David Kastrup : > Thomas Morley 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 that

Re: utf-8-strings

Thomas Morley 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: > http://www.lilypondforum.de/index

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 i

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 2012/07/