Re: Issue 788 in lilypond: simpler convert-ly rules

2010-10-23 Thread lilypond
Comment #5 on issue 788 by percival.music.ca: simpler convert-ly rules http://code.google.com/p/lilypond/issues/detail?id=788 Why the bloody mao are you talking about issue 855 in this one? In particular, read Mark's email in that issue, and the discussion. TL;DR version: wtf do you propose

Re: Issue 788 in lilypond: simpler convert-ly rules

2010-10-23 Thread lilypond
Comment #4 on issue 788 by v.villenave: simpler convert-ly rules http://code.google.com/p/lilypond/issues/detail?id=788 I had another suggestion in mind: how about: - where appropriate, we *only* index \foo entries. no more plain "foo" - in texi2html.init, we rewrite the @printindex command so t

Re: Issue 788 in lilypond: simpler convert-ly rules

2010-10-22 Thread lilypond
Comment #3 on issue 788 by tdanielsmusic: simpler convert-ly rules http://code.google.com/p/lilypond/issues/detail?id=788 I would strongly prefer removing the @funindex foo entries, and requiring all mention of such keywords in the text to be prefixed by \. It's an easy if laborious change

Re: Issue 788 in lilypond: simpler convert-ly rules

2010-10-22 Thread lilypond
Comment #2 on issue 788 by percival.music.ca: simpler convert-ly rules http://code.google.com/p/lilypond/issues/detail?id=788 Also, we currently have terms like @funindex \foo @funindex foo The latter version is *not* noticed by (most? some?) convert-ly rules. We should either disallow t

Re: Issue 788 in lilypond: simpler convert-ly rules

2010-01-03 Thread lilypond
Updates: Owner: --- Labels: -Type-Enhancement Type-Scripts Comment #1 on issue 788 by percival.music.ca: simpler convert-ly rules http://code.google.com/p/lilypond/issues/detail?id=788 (No comment was entered for this change.) -- You received this message because you are listed

Issue 788 in lilypond: simpler convert-ly rules

2009-07-06 Thread codesite-noreply
Status: Accepted Owner: gpermus Labels: Type-Enhancement Priority-Postponed Maintainability New issue 788 by gpermus: simpler convert-ly rules http://code.google.com/p/lilypond/issues/detail?id=788 This looks sub-optimal: -- def conv (str): str = re.sub (r"\\octave(?![a-zA-Z])", r"\\octa