Re: State of the pond

2012-04-21 Thread Jean-Charles Malahieude
Le 20/04/2012 23:42, Graham Percival disait : On Fri, Apr 20, 2012 at 07:38:06PM +0200, Jean-Charles Malahieude wrote: Le 19/04/2012 21:30, Graham Percival disait : - nobody touches the release/unstable branch, other than translators, who may merge with that if they want to and don't

Re: Regarding LSR translation work

2012-04-21 Thread Federico Bruni
Il 17/04/2012 23:40, Francisco Vila ha scritto: 2012/4/17 Federico Brunifedel...@gmail.com: Another solution could be keeping the current structure and changing only check-translation.py so that, when looking at the files in Documentation/snippets, it should check only the changes inside

Re: State of the pond

2012-04-21 Thread David Kastrup
Jean-Charles Malahieude lily...@orange.fr writes: Le 20/04/2012 23:42, Graham Percival disait : On Fri, Apr 20, 2012 at 07:38:06PM +0200, Jean-Charles Malahieude wrote: Le 19/04/2012 21:30, Graham Percival disait : - nobody touches the release/unstable branch, other than translators, who

Re: Regarding LSR translation work

2012-04-21 Thread Jean-Charles Malahieude
Le 21/04/2012 10:57, Federico Bruni disait : Il 17/04/2012 23:40, Francisco Vila ha scritto: 2012/4/17 Federico Brunifedel...@gmail.com: Another solution could be keeping the current structure and changing only check-translation.py so that, when looking at the files in

Re: Regarding LSR translation work

2012-04-21 Thread James
Hello, On 21 April 2012 10:13, Jean-Charles Malahieude lily...@orange.fr wrote: ... This makes me believe it would be a good opportunity to have the English version follow the same rule as translations. Err.. not sure what you mean by that technically but it's complicated enough with snippets

Re: Regarding LSR translation work

2012-04-21 Thread Graham Percival
On Sat, Apr 21, 2012 at 11:33:49AM +0100, James wrote: Err.. not sure what you mean by that technically but it's complicated enough with snippets as it is, to follow the translation method adds even more complexity (if the CG is anything to go by). +1 We want to encourage contributors not

Re: State of the pond

2012-04-21 Thread Bernard Hurley
On Sat, Apr 21, 2012 at 11:08:00AM +0200, Werner LEMBERG wrote: [1] why oh why does the main GNU editor not use the official extension language for the GNU operating system?? Same reason why its keyboard shortcuts are only so-so compatible with CUA and/or GNOME: its development was

Re: State of the pond

2012-04-21 Thread David Kastrup
Bernard Hurley bern...@marcade.biz writes: On Sat, Apr 21, 2012 at 11:08:00AM +0200, Werner LEMBERG wrote: [1] why oh why does the main GNU editor not use the official extension language for the GNU operating system?? Same reason why its keyboard shortcuts are only so-so compatible

Re: Regarding LSR translation work

2012-04-21 Thread Jean-Charles Malahieude
Le 21/04/2012 12:33, James disait : Hello, On 21 April 2012 10:13, Jean-Charles Malahieudelily...@orange.fr wrote: ... This makes me believe it would be a good opportunity to have the English version follow the same rule as translations. Err.. not sure what you mean by that technically but

Re: State of the pond

2012-04-21 Thread Bernard Hurley
On Sat, Apr 21, 2012 at 01:49:38PM +0200, David Kastrup wrote: Bernard Hurley bern...@marcade.biz writes: On Sat, Apr 21, 2012 at 11:08:00AM +0200, Werner LEMBERG wrote: [1] why oh why does the main GNU editor not use the official extension language for the GNU operating system??

Re: State of the pond

2012-04-21 Thread David Kastrup
Bernard Hurley bern...@marcade.biz writes: On Sat, Apr 21, 2012 at 01:49:38PM +0200, David Kastrup wrote: Bernard Hurley bern...@marcade.biz writes: That sounds interesting. Personally I would rather see Emacs re-implemented using Common Lisp instead of Emacs Lisp.

New template for 'lilypond' made available

2012-04-21 Thread Translation Project Robot
Hello, gentle maintainer. This is a message from the Translation Project robot. (If you have any questions, send them to coordina...@translationproject.org.) A new POT file for textual domain 'lilypond' has been made available to the language teams for translation. It is archived as:

Re: beam.cc:pure-rest-collision-callback Place on staff lines; issue 2468 (issue 6035053)

2012-04-21 Thread dak
On 2012/04/15 20:06:55, Keith wrote: On 2012/04/15 16:45:54, Keith wrote: An improvement would be to round-to-larger Done, along with other cleanup following the similar function rest_collision_callback() The cleanup would seem to break layout totally.

Re: beam.cc:pure-rest-collision-callback Place on staff lines; issue 2468 (issue 6035053)

2012-04-21 Thread k-ohara5a5a
On 2012/04/21 16:10:09, dak wrote: The cleanup would seem to break layout totally. URL:http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/71476 That's disappointing. The property 'previous_offset' sometimes has values comparable to the page height. On the early returns I'll

scheme: working in guile but not in lilypond?

2012-04-21 Thread Thomas Morley
Hi, the following code gives me the expected output in guile: (define-public lst `()) (define (set-new-alist! ls-1 ls-2 proc) (for-each (lambda (x) (set! ls-1 (acons x proc ls-1))) ls-2) ls-1) (set-new-alist! lst '(1 2 3) X) == ((3 . X) (2 . X) (1 . X)) trying similiar in lily: \version

Re: scheme: working in guile but not in lilypond?

2012-04-21 Thread David Kastrup
Thomas Morley thomasmorle...@googlemail.com writes: Hi, the following code gives me the expected output in guile: (define-public lst `()) (define (set-new-alist! ls-1 ls-2 proc) (for-each (lambda (x) (set! ls-1 (acons x proc ls-1))) ls-2) ls-1) (set-new-alist! lst '(1 2 3) X) ==

Re: State of the pond

2012-04-21 Thread Francisco Vila
2012/4/20 Graham Percival gra...@percival-music.ca: We do not have a long history of flawless git actions from translations, so my preference would be not to touch anything. Good idea! The definitive recipe for eternal flawless development is not to touch anything, ever. Better safe than sorry.

Re: scheme: working in guile but not in lilypond?

2012-04-21 Thread Gilles
\version 2.15.36 #(define-public lst `()) #(define (set-new-alist! ls-1 ls-2 proc) (for-each (lambda (x) (set! ls-1 (acons x proc ls-1))) ls-2) ls-1) #(set-new-alist! lst '(1 2 3) X) #(display lst) returns: () What am I missing? %% Well, if you change #(set-new-alist! lst '(1 2 3) X)

Re: State of the pond

2012-04-21 Thread James
Hello, On 22 April 2012 00:02, Francisco Vila paconet@gmail.com wrote: 2012/4/20 Graham Percival gra...@percival-music.ca: We do not have a long history of flawless git actions from translations, so my preference would be not to touch anything. Good idea! The definitive recipe for

Re: Footnote documentation error

2012-04-21 Thread James
Hello, On 22 April 2012 04:12, Mark Mathias d8val...@gmail.com wrote: So... as far as the Bug Squad is concerned, are we still waiting for something or does this need to get added to the tracker? Thanks, Mark As far as the bug squad are concerned - being one myself - we'd like a