Re: Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation

Updates: Status: Fixed Labels: -Patch-push Comment #8 on issue 2137 by pkx1...@gmail.com: Patch: Doc: NR improve 'visibility' of 'q' operation http://code.google.com/p/lilypond/issues/detail?id=2137 Wed, 4 Jan 2012 07:52:39 + (07:52 +) commit 4269f54b663421ca

Issue 2176 in lilypond: Move auto-beaming before the engraving stage.

Status: Accepted Owner: mts...@gmail.com Labels: Type-Enhancement New issue 2176 by mts...@gmail.com: Move auto-beaming before the engraving stage. http://code.google.com/p/lilypond/issues/detail?id=2176 I've seen several problems come up with auto beaming over the past two years that could

Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular

Comment #7 on issue 2148 by m...@apollinemike.com: object outlines shouldn't be rectangular http://code.google.com/p/lilypond/issues/detail?id=2148 The good news is that the code is not too big and complicated in LilyPond - it's well segmented, and most of what'd need to be changed is the S

Re: Issue 2162 in lilypond: Patch: Doc: NR added @knownissue for beam properties

Updates: Labels: -Patch-needs_work Patch-push Comment #4 on issue 2162 by k-ohara5...@oco.net: Patch: Doc: NR added @knownissue for beam properties http://code.google.com/p/lilypond/issues/detail?id=2162 The discussion was all: "LGTM, but don't we need more..." and James clarified wha

Re: Issue 2166 in lilypond: Copy pdf docs to new website folder

Updates: Labels: -Patch-countdown Patch-push Comment #4 on issue 2166 by colinpkc...@gmail.com: Copy pdf docs to new website folder http://code.google.com/p/lilypond/issues/detail?id=2166 Counted down to 20120103, please push ___ bug

Re: Issue 2162 in lilypond: Patch: Doc: NR added @knownissue for beam properties

Updates: Labels: -Patch-countdown Patch-needs_work Comment #3 on issue 2162 by colinpkc...@gmail.com: Patch: Doc: NR added @knownissue for beam properties http://code.google.com/p/lilypond/issues/detail?id=2162 THis looks as though it is still a work in process, per discussion on Ri

Re: Issue 2153 in lilypond: piano pedal bracket should stop at requested moment

Updates: Labels: -Patch-countdown Patch-push Comment #6 on issue 2153 by colinpkc...@gmail.com: piano pedal bracket should stop at requested moment http://code.google.com/p/lilypond/issues/detail?id=2153 Counted down to 20120103, please push

Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files

Updates: Labels: -Patch-countdown Patch-needs_work Comment #4 on issue 2158 by colinpkc...@gmail.com: Patch: Sketch of not remaking html files http://code.google.com/p/lilypond/issues/detail?id=2158 Phil is working on this one, per comment #3 on Rietveld. ___

Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate.

Updates: Labels: -Patch-countdown Patch-needs_work Comment #17 on issue 2149 by colinpkc...@gmail.com: Patch: Creates non-negative-integer? predicate. http://code.google.com/p/lilypond/issues/detail?id=2149 It seems that the discussion on naming the baby continues. Let's call this o

Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR

Updates: Labels: -Patch-countdown Patch-push Comment #14 on issue 1935 by colinpkc...@gmail.com: Doc: internal ledger lines need to be documented in NR http://code.google.com/p/lilypond/issues/detail?id=1935 Counted down to 20120103, please push

Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch

Updates: Labels: -Patch-countdown Patch-push Comment #12 on issue 2092 by colinpkc...@gmail.com: lily-git.tcl should using a "working" branch http://code.google.com/p/lilypond/issues/detail?id=2092 Counted down to 20120103, p

Re: Issue 2152 in lilypond: Patch: Removes ugly side bars from learning

Updates: Labels: -Patch-countdown Patch-push Comment #4 on issue 2152 by colinpkc...@gmail.com: Patch: Removes ugly side bars from learning http://code.google.com/p/lilypond/issues/detail?id=2152 Counted down to 20120103, please push

Re: Issue 2164 in lilypond: Learning Manual: Better explanation with updated example for \once tweak

Updates: Labels: -Patch-countdown Patch-push Comment #5 on issue 2164 by colinpkc...@gmail.com: Learning Manual: Better explanation with updated example for \once tweak http://code.google.com/p/lilypond/issues/detail?id=2164 Counted down to 20120103, please push

Re: Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation

Updates: Labels: -Patch-countdown Patch-push Comment #7 on issue 2137 by colinpkc...@gmail.com: Patch: Doc: NR improve 'visibility' of 'q' operation http://code.google.com/p/lilypond/issues/detail?id=2137 Counted down to 2

Re: Issue 1629 in lilypond: Tuplet line collides with fingering

Updates: Labels: -Patch-countdown Patch-push Comment #5 on issue 1629 by colinpkc...@gmail.com: Tuplet line collides with fingering http://code.google.com/p/lilypond/issues/detail?id=1629 Counted down to 20120103, please push ___ bug

Re: Issue 1948 in lilypond: Windows install clobbered system PATH

lilypond-4 wrote: > > > Comment #12 on issue 1948 by philehol...@gmail.com: Windows install > clobbered system PATH > http://code.google.com/p/lilypond/issues/detail?id=1948 > > I've spent quite a while looking at this today, and can report the > following strange stuff. > > When lily is

Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular

Comment #6 on issue 2148 by milimet...@gmail.com: object outlines shouldn't be rectangular http://code.google.com/p/lilypond/issues/detail?id=2148 Mike, could you please explain, why your Python script will help in fixing Lilypond? As I suspect, you have written the whole code that computed

Re: Issue 2174 in lilypond: Patch: CG: clarify what countdown means

Updates: Status: Fixed Labels: -Patch-review Comment #3 on issue 2174 by janek.li...@gmail.com: Patch: CG: clarify what countdown means http://code.google.com/p/lilypond/issues/detail?id=2174 pushed as c1a1f9684b6cfab2e4b4d813db6058c7d22b9b0a

Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented

Updates: Labels: Patch-review Comment #13 on issue 2093 by lilypond...@gmail.com: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented http://code.google.com/p/lilypond/issues/detail?id=2093#c13 Patchy the autobot says: LGTM.

Re: Issue 2174 in lilypond: Patch: CG: clarify what countdown means

Updates: Labels: Patch-review Comment #2 on issue 2174 by lilypond...@gmail.com: Patch: CG: clarify what countdown means http://code.google.com/p/lilypond/issues/detail?id=2174#c2 Patchy the autobot says: LGTM. ___ bug-lilypond mailing lis

inconsistent handling of lilypond cmd with or without -h when LANG=… is not en

if you have defined a language with e.g. SET LANG=it you get different output for the command lilypond & lilypond -h - GNU LilyPond 2.15.23 Uso: lilypond [OPZIONE]... [FILE]... Stampa partitura oppure crea MIDI da FILE. LilyPond produce bella notazione musicale. Per maggiori informazioni

Issue 2175 in lilypond: Patch: explain how to add git-cl to PATH

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2175 by janek.li...@gmail.com: Patch: explain how to add git-cl to PATH http://code.google.com/p/lilypond/issues/detail?id=2175 explain how to add git-cl to PATH i know modifying PATH is basic knowledge, but i'm windows man

Issue 2174 in lilypond: Patch: CG: clarify what countdown means

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2174 by janek.li...@gmail.com: Patch: CG: clarify what countdown means http://code.google.com/p/lilypond/issues/detail?id=2174 CG: clarify what countdown means CG currently sounds like "countdown is the time when developers

Re: Issue 2160 in lilypond: document LILYPOND_WEB_MEDIA_GIT

Comment #1 on issue 2160 by gra...@percival-music.ca: document LILYPOND_WEB_MEDIA_GIT http://code.google.com/p/lilypond/issues/detail?id=2160 the patch for issue 2166 fixes this. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu

Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented

Comment #12 on issue 2093 by pkx1...@gmail.com: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented http://code.google.com/p/lilypond/issues/detail?id=2093#c12 Doc: NR added snippet for Alt Bar Numbering Tracker item 2093 Added snippet showing #'numbers and #'numbers-w

Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented

Updates: Labels: Patch-new Comment #11 on issue 2093 by pkx1...@gmail.com: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented http://code.google.com/p/lilypond/issues/detail?id=2093#c11 Doc: NR added snippet for Alt Bar Numbering Tracker item 2093 Added snippe

Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest

Updates: Status: Fixed Labels: -Patch-push Comment #8 on issue 2109 by janek.li...@gmail.com: do not tinker with the position of a pitched rest http://code.google.com/p/lilypond/issues/detail?id=2109 pushed as 9f24e79a945ec4ab000d3e09ff2d2ac8208e2246 Sorry for the delay and ma

Re: Issue 1948 in lilypond: Windows install clobbered system PATH

Comment #14 on issue 1948 by gra...@percival-music.ca: Windows install clobbered system PATH http://code.google.com/p/lilypond/issues/detail?id=1948 At first glance, Keith's suggestion from comment 8 would solve this issue, but nobody's tested it yet. I think that's the place to start.

Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient

On Tue, Jan 03, 2012 at 07:53:32PM +, lilyp...@googlecode.com wrote: > > Graham, > > by "grab the patch and fix it" do you mean "download a patch, fix it > according to your taste and upload it in a new Rietveld issue"? Yes. (well, mostly Keith's taste, and anybody else who clarifies git stu

Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient

Comment #14 on issue 2100 by janek.li...@gmail.com: Patch: CG: explanation of branches for the impatient http://code.google.com/p/lilypond/issues/detail?id=2100 Graham, by "grab the patch and fix it" do you mean "download a patch, fix it according to your taste and upload it in a new Rietv

Re: Issue 1948 in lilypond: Windows install clobbered system PATH

On Tue, 03 Jan 2012 10:10:55 -0800, wrote: Comment #11 on issue 1948 by PhilEHolmes: Windows install clobbered system http://code.google.com/p/lilypond/issues/detail?id=1948 for some bizarre reason running a DOS box doesn't return that value - it returns the old one. You need to reboot to g

Re: Issue 1948 in lilypond: Windows install clobbered system PATH

Comment #13 on issue 1948 by philehol...@gmail.com: Windows install clobbered system PATH http://code.google.com/p/lilypond/issues/detail?id=1948 OK - it looks like there is nsis code designed to delete the extra entry in the path statement, but it's not working AFAICS. I need GUB to be ru

Re: Issue 2173 in lilypond: Deal with file names not encoded in UTF-8

Updates: Labels: Type-Enhancement Comment #5 on issue 2173 by k-ohara5...@oco.net: Deal with file names not encoded in UTF-8 http://code.google.com/p/lilypond/issues/detail?id=2173 1) Probably not the issue: In Windows the encoding used by the console is chosen by the user. This is

Re: Issue 1948 in lilypond: Windows install clobbered system PATH

Comment #12 on issue 1948 by philehol...@gmail.com: Windows install clobbered system PATH http://code.google.com/p/lilypond/issues/detail?id=1948 I've spent quite a while looking at this today, and can report the following strange stuff. When lily is installed, the installer writes the pa

Re: Issue 2165 in lilypond: Patch: Modifies broken hairpin height

Comment #5 on issue 2165 by prze...@gmail.com: Patch: Modifies broken hairpin height http://code.google.com/p/lilypond/issues/detail?id=2165 Thanks for making it. There is still the problem of padding (i.e. lack of it), mentioned in the same comment 38 of issue 2057 (suggesting sane defaul

Re: Issue 2173 in lilypond: Deal with file names not encoded in UTF-8

Comment #4 on issue 2173 by d...@gnu.org: Deal with file names not encoded in UTF-8 http://code.google.com/p/lilypond/issues/detail?id=2173 That just means that Windows supports byte streams. Pango is not a Windows component. UTF-8 support would mean supporting UTF-8 on the command line,

Re: Issue 2173 in lilypond: Deal with file names not encoded in UTF-8

Comment #3 on issue 2173 by philehol...@gmail.com: Deal with file names not encoded in UTF-8 http://code.google.com/p/lilypond/issues/detail?id=2173 Windows certainly supports UTF-8 characters. As a general rule, adding an accented character to a file and saving as non-UTF-8 gives a "lil

Re: Issue 1566 in lilypond: Beam properties won't be changed after the start of the beam

Updates: Status: Started Owner: pkx1...@gmail.com Comment #6 on issue 1566 by pkx1...@gmail.com: Beam properties won't be changed after the start of the beam http://code.google.com/p/lilypond/issues/detail?id=1566 On 1 January 2012 23:38, Keith OHara wrote: On Sun, 01 Jan 20

Re: Issue 2173 in lilypond: Deal with file names not encoded in UTF-8

Comment #2 on issue 2173 by d...@gnu.org: Deal with file names not encoded in UTF-8 http://code.google.com/p/lilypond/issues/detail?id=2173 http://msdn.microsoft.com/en-us/library/x99tb11d%28v=VS.100%29.aspx> appears to suggest that Windows can't to UTF-8. If that's true, we will need to

Re: Issue 2173 in lilypond: Deal with file names not encoded in UTF-8

Comment #1 on issue 2173 by d...@gnu.org: Deal with file names not encoded in UTF-8 http://code.google.com/p/lilypond/issues/detail?id=2173 We have static void setup_localisation () { #if HAVE_GETTEXT /* Enable locales */ setlocale (LC_ALL, ""); /* FIXME: check if this is still true.