Re: `:' vs `.' in doc files

> > you've changed a lot of `.' at the end of paragraphs into `:' if > > the text is followed by an example. I think this is wrong. IIRC, > > it is better style in English to close with a full stop. > > Sorry, I don't know good English style, I'd better changed nothing. Similar to you I'm no exp

Re: segfault on input/regression/lyric-extender-no-heads.ly

Joe Neeman escreveu: > This is with latest git: > > $ ./out/bin/lilypond input/regression/lyric-extender-no-heads.ly > > GNU LilyPond 2.11.10 > Processing `input/regression/lyric- extender-no-heads.ly > ' > Parsing... > Interpreting music.

Re: adding installation for windows in German

Han-Wen Nienhuys wrote: see btw, lilypond.org/~hanwen/annotated-demo.pdf maybe this should get a place somewhere on the website? Nice! /Mats ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/

Re: adding installation for windows in German

Mats Bengtsson escreveu: > > > Han-Wen Nienhuys wrote: >> >> see btw, >> lilypond.org/~hanwen/annotated-demo.pdf >> >> maybe this should get a place somewhere on the website? > Nice! I've added it to the website (including SVG source), but would appreciate it someone would do the work of ma

Updated spanish translation

Three things: First: I attach the patch for the latest updated spanish translation in bzipped format. Second: There's a typo in site/about/automated-engraving/input-format.html . Where it says: The above is another expression, and therefore, it many combined again with a simultaneous expres

assertion failure in mozart-hrn-3

With latest git, make web fails on mozart-hrn-3.ly: $ ./out/bin/lilypond input/mutopia/W.A.Mozart/mozart-hrn-3.ly GNU LilyPond 2.11.10 Processing `input/mutopia/W.A.Mozart/mozart-hrn-3.ly' Parsing... Interpreting music... [8][16][24][32][40][48][56][64][72][80][88][96] warning: cannot find start

Re: makeinfo with utf-8 support

> [EMAIL PROTECTED]: > > Le jeudi 04 janvier 2007 à 00:33 +0100, Karl Hammar a écrit : > > > Hmm, when building I get: > > > > > > out/lilypond.nexi:62: warning: unrecognized encoding name `utf-8'. > ... > > > Does anybody know where the makeinfo with utf-8 support is, a patch ? > > > > AFAIK

Re: Backporting doc changes to stable/2.10 [was: Re: Docs check-translation]

Le 08.01.2007 01:45, John Mandereau disait : Graham Percival wrote: Thanks, these look good. However, there are some problems with your other updates: 1. Wrapping paragraphs in texinfo is pointless, because texinfo ignores whitespace. Lines that are too long are annoying for people using

Re: test coverage

On 1/2/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Hi, I've been running coverage tests of the input/regression/ suite, to see which parts of the code are not excercised. This has already turned up some bugs. You can get a full overview by running buildscripts/build-coverage.sh, but here

Styles [Was Re: Barline scans]

[moving this from bug-lilypond] [EMAIL PROTECTED]: > Karl Hammar wrote: > > Maybe we should have a "my style" section in the doc. > > Like section 4.3 Style sheets ? There you tell us how to do it. But perhaps more like the snippet respository, examples of different styles. Right now we "only" h

Re: Styles [Was Re: Barline scans]

Karl Hammar wrote: [moving this from bug-lilypond] [EMAIL PROTECTED]: Karl Hammar wrote: Maybe we should have a "my style" section in the doc. Like section 4.3 Style sheets ? There you tell us how to do it. But perhaps more like the snippet respository, examples of different styles. Right n

Re: skyline vertical spacing

On 1/6/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Joe Neeman escreveu: > > Hi, > > I have added scripts for profiling, see buildscripts/build- profile.sh. > > It turns out that the skyline related routines have replaced > Grob::get_property() as the top-contender in the prof

Re: Backporting doc changes to stable/2.10 [was: Re: Docs check-translation]

Jean-Charles wrote: All the documents that I have read about typography and "good use" show examples introduced with a colon (:) throughout their content. So I think it is normal French typography to do like this. To be honest, I'm not certain where the no-colon rule came from. I just check

Re: Backporting doc changes to stable/2.10 [was: Re: Docs check-translation]

Graham Percival escreveu: > Jean-Charles wrote: >> All the documents that I have read about typography and "good use" >> show examples introduced with a colon (:) throughout their content. >> So I think it is normal French typography to do like this. > > To be honest, I'm not certain where the no

Document add-on suggestion for 13.1.1 Command line options

Hi, I'd like to change a little the page 13.1.1-Command Line Options to make the syntax clearer for newbies. I didn't understand myself the syntax of these, I had to give some time to test different options and to leave some messages to the users' group because of that. >From the line beginning w