Hi John,
Would it be possible to add a link to the
http://lilypond.org/web/devel/participating/documentation-adding
page in the HTML footer? I'm thinking of something like
If you have any suggestions for the documentation, please see
_documentation suggestions_
(where _foo_ is the actual lin
Erik Sandberg escreveu:
> Hi,
>
> Any plans to relicense lily under GPL v3? (you have my permission to do that
> for all code I've written; to me v3 looks strictly better than v2)
>
> If not, I suggest the GPL link at http://lilypond.org/web/about/faq is
> changed
> to http://www.gnu.org/licen
2007/7/2, John Mandereau <[EMAIL PROTECTED]>:
To fix this, we must use ugettext instead of gettext in lilylib.py.
Unfortunately, this fix implies that each gettexted string must be
converted from Python internal Unicode to stdout/stderr encoding before
being written to stdout/stderr.
May I comm
Hi,
I've hit character encoding issues when calling lilypond-book compiled
locally. It seems that optparse implementation has changed between
Python 2.4 and 2.5 in a way that OptionParser.print_help wants to
convert string encoding before writing to stdout. The problem is,
Python knows only two
> > However, in normal text, @q{foo} should make correct use of curly
> > quotes, both in PDF and HTML output.
>
> It doesn't (more exactly it produces ugly output) on my computer:
> see
> http://lists.gnu.org/archive/html/bug-texinfo/2007-07/msg0.html
I've seen that, and I hope that this bug
Le mardi 03 juillet 2007 à 00:38 +0200, Werner LEMBERG a écrit :
> However, in
> normal text, @q{foo} should make correct use of curly quotes, both in
> PDF and HTML output.
It doesn't (more exactly it produces ugly output) on my computer: see
http://lists.gnu.org/archive/html/bug-texinfo/2007-07/
Le lundi 02 juillet 2007 à 21:16 +0100, Anthony W. Youngman a écrit :
> In message <[EMAIL PROTECTED]>, John Mandereau
> <[EMAIL PROTECTED]> writes
> >[1] Our current texinfo.tex don't replace quotes with curly quotes. In
> >current official texinfo.tex, it's possible to do the same if we add
>
> > Bit late, I know, but do we WANT to replace quotes with curly
> > quotes? It's quite easy to cut-n-paste from pdf into a lily file,
> > and then lily will choke on the pasted code ... (and some of us
> > don't work on line, and some of this html manuals are the work of
> > the devil ... :-)
>
Anthony W. Youngman wrote:
In message <[EMAIL PROTECTED]>, John Mandereau
<[EMAIL PROTECTED]> writes
[1] Our current texinfo.tex don't replace quotes with curly quotes. In
current official texinfo.tex, it's possible to do the same if we add
Bit late, I know, but do we WANT to replace quotes w
In message <[EMAIL PROTECTED]>, John Mandereau
<[EMAIL PROTECTED]> writes
[1] Our current texinfo.tex don't replace quotes with curly quotes. In
current official texinfo.tex, it's possible to do the same if we add
Bit late, I know, but do we WANT to replace quotes with curly quotes?
It's quit
> The historical reason is that in the beginning, all event classes
> were named in CamelCase, but when all music event 'types were added
> as classes, I kept the lisp-style naming. I agree that it's the
> naming of StreamEvent that should change.
Will you do that?
Werner
Hi,
On Mon, 2 Jul 2007, [EMAIL PROTECTED] wrote:
>
>
>
is there _any_ good reason to enforce html, and not even giving a
plain-text eqivalent of your message?
Ciao,
Dscho
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.o
On Monday 02 July 2007, [EMAIL PROTECTED] wrote:
> I am also interested in the research in tuning systems other than equal
> temperament, which allows unusual frequency ratios to be heard in chords
> and melodies, which gives composers new possibilities to explore. See also
> http://www.midicode.c
On Wednesday 27 June 2007, Werner LEMBERG wrote:
> There's a single event class, StreamEvent, which uses uppercase
> letters in its name. Wouldn't be stream-event a better name, similar
> to all others?
The historical reason is that in the beginning, all event classes were named
in CamelCase, bu
Hi,
Any plans to relicense lily under GPL v3? (you have my permission to do that
for all code I've written; to me v3 looks strictly better than v2)
If not, I suggest the GPL link at http://lilypond.org/web/about/faq is changed
to http://www.gnu.org/licenses/old-licenses/gpl-2.0.html, for clarit
rational_music_notation.xhtml
Description: application/xhtml
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
16 matches
Mail list logo
