Re: Issue 887 in lilypond: PDF point-and-click URI links with special chars wrongly encoded depending on the OS

2009-11-23 Thread lilypond
Comment #9 on issue 887 by pnorcks: PDF point-and-click URI links with special chars wrongly encoded depending on the OS http://code.google.com/p/lilypond/issues/detail?id=887 Also, on GNU/Linux, are you setting up point-and-click functionality according to http://lilypond.org/doc/v2.13/D

Re: Issue 887 in lilypond: PDF point-and-click URI links with special chars wrongly encoded depending on the OS

2009-11-23 Thread lilypond
Comment #8 on issue 887 by pnorcks: PDF point-and-click URI links with special chars wrongly encoded depending on the OS http://code.google.com/p/lilypond/issues/detail?id=887 Just an update here... I can reproduce the problem now. Thanks for the more detailed explanation. This appears t

Re: Issue 903 in lilypond: Enhancement: a more user-friendly way to specify notename languages

2009-11-23 Thread lilypond
Comment #15 on issue 903 by veryfurryfur: Enhancement: a more user-friendly way to specify notename languages http://code.google.com/p/lilypond/issues/detail?id=903 there will be no syntax changes within stable numbers (i.e. 2.12.x, 2.14.y). Sorry, what do you mean? According to the downl

Re: Issue 903 in lilypond: Enhancement: a more user-friendly way to specify notename languages

2009-11-23 Thread lilypond
Comment #14 on issue 903 by percival.music.ca: Enhancement: a more user-friendly way to specify notename languages http://code.google.com/p/lilypond/issues/detail?id=903 Historically, we have changed the syntax whenever the whim struck us. This policy is changing; there will be no syntax c

Re: Issue 872 in lilypond: Changes split-page has broken images

2009-11-23 Thread lilypond
Updates: Status: Fixed Comment #3 on issue 872 by percival.music.ca: Changes split-page has broken images http://code.google.com/p/lilypond/issues/detail?id=872 Jan fixed this by fixing the typo in a91dd4c245aa148bf003b28f2990b1e45d62dcc9. -- You received this message because you

Re: Issue 903 in lilypond: Enhancement: a more user-friendly way to specify notename languages

2009-11-23 Thread lilypond
Comment #13 on issue 903 by veryfurryfur: Enhancement: a more user-friendly way to specify notename languages http://code.google.com/p/lilypond/issues/detail?id=903 Thanks. Again, I am most likely wrong because I'm new here, but I'm trying to understand. What do you mean by "noiceable vers

Re: Issue 903 in lilypond: Enhancement: a more user-friendly way to specify notename languages

2009-11-23 Thread lilypond
Comment #12 on issue 903 by hanwenn: Enhancement: a more user-friendly way to specify notename languages http://code.google.com/p/lilypond/issues/detail?id=903 Would the language feature be feasible to implement as a music function with no arguments? (the function implementation has chang

Re: Issue 903 in lilypond: Enhancement: a more user-friendly way to specify notename languages

2009-11-23 Thread lilypond
Comment #11 on issue 903 by d...@gnu.org: Enhancement: a more user-friendly way to specify notename languages http://code.google.com/p/lilypond/issues/detail?id=903 "Tool x can process Lilypond files of version y or later" - that's sensible for an announcement. convert-ly also has to work

Re: Issue 903 in lilypond: Enhancement: a more user-friendly way to specify notename languages

2009-11-23 Thread lilypond
Comment #10 on issue 903 by veryfurryfur: Enhancement: a more user-friendly way to specify notename languages http://code.google.com/p/lilypond/issues/detail?id=903 I don't mean it in a confrontational way, but may I ask what the rationale is please? -- You received this message because y

Re: Issue 903 in lilypond: Enhancement: a more user-friendly way to specify notename languages

2009-11-23 Thread Ian Hulin
Neil Puttock wrote: 2009/11/22 Francisco Vila : 2009/11/22 Ian Hulin : If you do this as a function, I suggest you call it \notenames, \notenames "italiano" \notenames "deutsch" etc. \language suggests you may be dynamically changing the whole language environment of Lilypond, including error

Re: Issue 898 in lilypond: Enhancement: rests should be taken into account when determining beaming intervals

2009-11-23 Thread lilypond
Comment #1 on issue 898 by d...@gnu.org: Enhancement: rests should be taken into account when determining beaming intervals http://code.google.com/p/lilypond/issues/detail?id=898 It would also make sense to have an option to allow automatic beaming across rests when a note instead of a rest

Re: Issue 903 in lilypond: Enhancement: a more user-friendly way to specify notename languages

2009-11-23 Thread lilypond
Comment #9 on issue 903 by d...@gnu.org: Enhancement: a more user-friendly way to specify notename languages http://code.google.com/p/lilypond/issues/detail?id=903 A major change in general input syntax, even optional, should be accompanied by a noticeable version number change. -- You re

Re: Issue 903 in lilypond: Enhancement: a more user-friendly way to specify notename languages

2009-11-23 Thread lilypond
Comment #8 on issue 903 by veryfurryfur: Enhancement: a more user-friendly way to specify notename languages http://code.google.com/p/lilypond/issues/detail?id=903 I really cannot see any risks involved to warrant waiting for a major release. If you disagree, please come forward with speci