> > I'm hoping someone can help me figure out what's wrong when I try
> > to build the docs. I've never been able to build them
> > successfully. The program always builds perfectly, but the
> > documentation fails. Here's the last bit of the terminal output
> > before it aborts:
>
> Sadly, do
Graham Percival wrote:
Sadly, doc build errors are usually 100-200 lines before the end
of the build log. That makes it difficult to spot. :(
./0c/lily-a8f95448-systems.texi:1: epsf.tex not found, images will be
ignored.
@image ...f.tex not found, images will be ignored}
On Mon, Dec 01, 2008 at 07:59:01PM -0600, Jonathan Kulp wrote:
> I'm hoping someone can help me figure out what's wrong when I try to
> build the docs. I've never been able to build them successfully. The
> program always builds perfectly, but the documentation fails. Here's
> the last bit
I'm hoping someone can help me figure out what's wrong when I try to
build the docs. I've never been able to build them successfully. The
program always builds perfectly, but the documentation fails. Here's
the last bit of the terminal output before it aborts:
Compiling
/home/jon/lilypond/
Le lundi 01 décembre 2008 à 17:26 +0100, Werner LEMBERG a écrit :
> What's the correct calling sequence to regenerate lilypond.pot (not
> lilypond-doc.pot)?
At top of the source tree with no uncommitted changes
make po-replace
git commit -m "Update lilypond.pot" po/lilypond.pot
git reset --hard
> > 2003, 2004, 2005, 2006, 2007, 2008
> >
> > Very inconvenient, but apparently in accordance with US law.
>
> But LP is 12 years old now!
Time flies...
> Anyway, I am not concerned about the stated year of the copyright
> notice in the files, but rather with the printed notice made by the
> p
Hi Neil,
On Sat, Nov 29, 2008 at 12:28:49PM +, Neil Puttock wrote:
>
> Are there still issues remaining following this commit:
> bcf8411a8147595cf6e7f06ef20e931918368f67?
Yes. I'm not sure which ones involve the 32<->64 bit conversions, but I've
just catalogued all conversion warnings in t
What's the correct calling sequence to regenerate lilypond.pot (not
lilypond-doc.pot)?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
El día 1 de diciembre de 2008 17:14, Francisco Vila
<[EMAIL PROTECTED]> escribió:
> 2008/12/1 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
>> Looks good to me. Can you send me the patch as an attachment, so I
>> can easily hook it into Gub?
>>
>> thanks!
>
> Sure, here it is.
It is based on
http://lilyp
2008/12/1 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> Looks good to me. Can you send me the patch as an attachment, so I
> can easily hook it into Gub?
>
> thanks!
Sure, here it is.
It is apparently in ISO-8859, if there is any problem please tell me.
--
Francisco Vila. Badajoz (Spain)
http://www.p
Looks good to me. Can you send me the patch as an attachment, so I
can easily hook it into Gub?
thanks!
2008/12/1 Jan Nieuwenhuizen <[EMAIL PROTECTED]>:
>
> --
> Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
> http://www.xs4all.nl/~jantien | http://www.lilypon
2008/12/1 Graham Percival <[EMAIL PROTECTED]>:
> - have a bi-weekly newsletter (this will hopefully continue after
> Aug)
The LilyReport *will* be back. (we can name it otherwise if you
prefer). I have one issue ready-to-release and pending, and I am still
willing (and able) to publish it on a w
2008/12/1 Werner LEMBERG <[EMAIL PROTECTED]>:
>> > This is *not* correct, according to the info I got from RMS on the
>> > Emacs list. The safest thing is to update all copyright years in
>> > all files to the year of the release.
>>
>> I could do it on all files for the --2008 part.
>>
>> As for
On Mon, Dec 01, 2008 at 10:58:01AM -0200, Han-Wen Nienhuys wrote:
> On Mon, Dec 1, 2008 at 2:57 AM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
>
> > I'm not sure I understand what you mean by "the getting help section of the
> > page". I haven't been able to find anything titled "getting help".
> > This is *not* correct, according to the info I got from RMS on the
> > Emacs list. The safest thing is to update all copyright years in
> > all files to the year of the release.
>
> I could do it on all files for the --2008 part.
>
> As for the year-- part, different files have different creat
On Mon, Dec 1, 2008 at 2:57 AM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
>>> What if we put a link under Quick Links on the main page, titled Getting
>>> Help, which pointed to a Getting Help page?
>>
>> How about adding some sort of story-line to the getting help-section
>> of the page? This
2008/12/1 Werner LEMBERG <[EMAIL PROTECTED]>:
>
>> There are tons of occurrences of the string "year--year" for a
>> variety of years, in all source files. This should only be updated
>> whenever the file itself gets updated.
>
> This is *not* correct, according to the info I got from RMS on the
>
2008/12/1 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> Looks good to me.
Thank you, applied.
> On Mon, Dec 1, 2008 at 7:45 AM, Francisco Vila <[EMAIL PROTECTED]> wrote:
>> Hello all,
>> This patch tries to improve/update the welcome files that are shown to
>> the new user.
--
Francisco Vila. Badajoz
Looks good to me.
On Mon, Dec 1, 2008 at 7:45 AM, Francisco Vila <[EMAIL PROTECTED]> wrote:
> Hello all,
> This patch tries to improve/update the welcome files that are shown to
> the new user.
>
> I have
> - suggested a name to save the file with. This is necessary because
> the save dialog of li
2008/12/1 Werner LEMBERG <[EMAIL PROTECTED]>:
> lilypad? Is it possible that you probably mean someone else?
Francisco: isn't Jan the author of the lilypad application?
Valentin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.
> There are tons of occurrences of the string "year--year" for a
> variety of years, in all source files. This should only be updated
> whenever the file itself gets updated.
This is *not* correct, according to the info I got from RMS on the
Emacs list. The safest thing is to update all copyrigh
Hello all,
This patch tries to improve/update the welcome files that are shown to
the new user.
I have
- suggested a name to save the file with. This is necessary because
the save dialog of lilypad gets the default name lost.
- changed accordignly the name of the PDF to open.
- updated the syntax
2008/12/1 Werner LEMBERG <[EMAIL PROTECTED]>:
>> Possibly the string "1996--2007" in copyright () in main.cc could also
>> be changed to "1996--2008" to update the lilypond -v message.
>
> Hmm. Shouldn't all files be updated w.r.t. the copyright year?
There are tons of occurrences of the string "
23 matches
Mail list logo
