On Fri, Feb 12, 2010 at 08:37:00PM +0100, James Bailey wrote:
>
> One thing I find very helpful is to have a short list of things to check
> for when doing these kinds of quick version test. I haven't really worked
> very hard on it, but here's kinda the things I do so far when looking at
> chec
Hello, I have a small suggestion.
When a translator faces this commit and tries to update her
translations accordingly,
e600412e50db9e8ee3b9e408527322b84b946f52 Doc build: make
screenshot-tutorials shared.
one tends to think that only blocks of text were moved or files
renamed. It is impossibl
2010/2/12 Francisco Vila :
> 2010/2/12 Graham Percival :
>> On Fri, Feb 12, 2010 at 08:55:10PM +0100, Francisco Vila wrote:
>>> Runaway argument?
>>> version "@w...@version{}}"^...@{^^mc' e' g' e'^...@}^^m@end
>>> example^^m...@etc.
>>> ./included/generating-output.texi:238: Paragraph ended before
2010/2/12 Graham Percival :
> On Fri, Feb 12, 2010 at 08:55:10PM +0100, Francisco Vila wrote:
>> Runaway argument?
>> version "@w...@version{}}"^...@{^^mc' e' g' e'^...@}^^m@end
>> example^^m...@etc.
>> ./included/generating-output.texi:238: Paragraph ended before \ was complete.
>
> I remember se
On Fri, Feb 12, 2010 at 10:57 AM, Graham Percival
wrote:
> I've tweaked the list of dirs to remove from
> share/ghostscript/Resources. The resulting files are (on average) 5
> megs smaller. linux-x86 works here for me.
>
> Could we get a few tests for various OSes?
> http://lilypond.org/~grah
Graham Percival wrote Friday, February 12, 2010 6:57 PM
I've tweaked the list of dirs to remove from
share/ghostscript/Resources. The resulting files are (on average)
5
megs smaller. linux-x86 works here for me.
Could we get a few tests for various OSes?
On Vista:
Yes - the .exe is 20.5
On Fri, Feb 12, 2010 at 08:55:10PM +0100, Francisco Vila wrote:
> Runaway argument?
> version "@w...@version{}}"^...@{^^mc' e' g' e'^...@}^^m@end example^^m...@etc.
> ./included/generating-output.texi:238: Paragraph ended before \ was complete.
I remember seeing this earlier in the week. Make sur
John, Sorry for bugging you again. I still have the problem
[apparently] with incuded/generating-output.itexi.
This could be of help:
make[1]: Entering directory `/home/fravd/source/lilypond/Documentation/es'
cd ./out-www && \
texi2pdf --batch -I
/home/fravd/source/lilypond/Documentat
On 12.02.2010, at 20:37, James Bailey wrote:
…
lilypond-book --latex-program=pdflatex --pdf -o out pdflatex-lily-
book-sample.lytex
should have been:
lilypond-book --pdf -o out pdflatex-lily-book-sample.lytex
…old file version…
___
lilypond-dev
So, when I'm not doing lilypond things, I test stuff. I'm a game
tester. One thing I find very helpful is to have a short list of
things to check for when doing these kinds of quick version test. I
haven't really worked very hard on it, but here's kinda the things I
do so far when looking
Hi Graham,
> Could we get a few tests for various OSes?
>http://lilypond.org/~graham/
Mac OS X 10.6 is aok.
It also seemed that "first compile" was almost instantaneous, as compared with
earlier upgrades -- is this a change, or am I imagining things?
Cheers,
Kieren.
___
On Fri, Feb 12, 2010 at 7:06 PM, Kieren MacMillan
wrote:
> Hi Graham,
>
>> Could we get a few tests for various OSes?
>> http://lilypond.org/~graham/
>
> Mac OS X 10.6 is aok.
> It also seemed that "first compile" was almost instantaneous, as compared
> with earlier upgrades -- is this a chang
I've tweaked the list of dirs to remove from
share/ghostscript/Resources. The resulting files are (on average) 5
megs smaller. linux-x86 works here for me.
Could we get a few tests for various OSes?
http://lilypond.org/~graham/
(mingw is "mingw-new.exe", to avoid a clash with the nsis 2.4.6
I've bumped nsis to 2.4.6. Could somebody check if it still installs
+ uninstalls in a manner which is no worse than 2.13.12 ?
http://lilypond.org/~graham/
PLEASE NOTE: I haven't tried using any of the new functions in nsis
2.4.6; I don't expect this version to be *better* than 2.13.12. If
it's
Hi all,
I've been using a Lilypond for a month now and I really impressed with its
complex and beautiful rendering.
However, I live in the country where most of the people cannot read music in
notation model. Instead, we are reading music in the solfegio: do, re, mi
fa, sol, la, ti. And when we
Reinhold Kainhofer:
...
> In my view there are two different kinds of include uses:
> 1) To include package-like .ily files, which define additional functionality.
> There many utility functions really might/should be in their own namespace,
> but many definitions (and in particular all \header,
16 matches
Mail list logo
