grenoui...@lilynet.net writes:
> 01:00:02 (UTC) Begin LilyPond compile, previous commit at
> 7df3f88192dbfc331aba1e06e7114794a1e1209a
> 01:00:16 From git.savannah.gnu.org:/srv/git/lilypond
>71827c7..7270930 master -> master
>7df3f88..f5c01cc translation -> translation
> 01:00:16
- Original Message -
From: "David Kastrup"
To:
Sent: Sunday, October 21, 2012 5:29 PM
Subject: Re: 2.17.5?
"Phil Holmes" writes:
For everyone's information, please note that the website is in a
somewhat unusual state. Something (I don't know what - waiting on
GP's thoughts) seems
- Original Message -
From: "David Kastrup"
To:
Sent: Monday, October 22, 2012 9:12 AM
Subject: Re: Patchy report
grenoui...@lilynet.net writes:
01:00:02 (UTC) Begin LilyPond compile, previous commit at
7df3f88192dbfc331aba1e06e7114794a1e1209a
01:00:16 From git.savannah.gnu.org:/srv
2012/10/22 Phil Holmes :
> grenoui...@lilynet.net writes:
> WARNING: Unable to find node 'Alturas' in book snippets.
> [snip]
>
> WARNING: Unable to find node 'Anotaciones editoriales' in book snippets.
> *** Undefined node `Títulos y cabeceras' in @ref (in
> out-www/notation/editorial.texi l. 1293
2012/10/22 Francisco Vila :
> Yes the warnings are harmless but the undefined node is a real
> problem. I did some node renaming yesterday. My fault probably. In
> 12--14 hours I will have some time and will fix it.
BTW I am trying to do some translations at work, but I am behind a
stupid and slow
2012/10/21 David Kastrup :
> David Kastrup writes:
>
>>> I'll merge stable/2.16 into translation. That should be
>>> unproblematic.
>>
>> The only reaction to that was a mail from Francisco which did not much
>> to address this part of my plan.
>>
>> I did this right now, and afterwards discovere
Francisco Vila writes:
> 2012/10/21 David Kastrup :
>> David Kastrup writes:
>>
I'll merge stable/2.16 into translation. That should be
unproblematic.
>>>
>>> The only reaction to that was a mail from Francisco which did not much
>>> to address this part of my plan.
>>>
>>> I did this
2012/10/22 Phil Holmes :
> WARNING: Unable to find node 'Alturas' in book snippets.
> WARNING: Unable to find node 'Alturas' in book snippets.
> [snip]
> WARNING: Unable to find node 'Anotaciones editoriales' in book snippets.
That's issue 2266.
I added some comments in August with some hints abou
2012/10/22 Federico Bruni :
>> *** Undefined node `Títulos y cabeceras' in @ref (in
>> out-www/notation/editorial.texi l. 1293 in @funindex)
>> Max error number exceeded
>
> this should be the error which makes the build fail
Wait half a moment: there is no @ref{Títulos y cabeceras} in
Documentati
Francisco Vila writes:
> 2012/10/22 Federico Bruni :
>>> *** Undefined node `Títulos y cabeceras' in @ref (in
>>> out-www/notation/editorial.texi l. 1293 in @funindex)
>>> Max error number exceeded
>>
>> this should be the error which makes the build fail
>
> Wait half a moment: there is no @ref{
2012/10/22 David Kastrup :
> In Documentation/es/notation/text.itely I find
>
> en otras secciones específicas: @ref{Música vocal}, @ref{Títulos y
> cabeceras}.
>
> (the ref being distributed across two lines, so easy to miss using
> grep).
>
> Maybe that is the problem?
Yes. I'm sorry. That's why
2012/10/22 Francisco Vila :
> 2012/10/22 David Kastrup :
>> In Documentation/es/notation/text.itely I find
>>
>> en otras secciones específicas: @ref{Música vocal}, @ref{Títulos y
>> cabeceras}.
>>
>> (the ref being distributed across two lines, so easy to miss using
>> grep).
>>
>> Maybe that is t
Francisco Vila writes:
> 2012/10/22 Francisco Vila :
>> 2012/10/22 David Kastrup :
>>> In Documentation/es/notation/text.itely I find
>>>
>>> en otras secciones específicas: @ref{Música vocal}, @ref{Títulos y
>>> cabeceras}.
>>>
>>> (the ref being distributed across two lines, so easy to miss usi
Thanks for doing this.
Some comments (it's the one thing I feel competent enough to join in and
make suggestions on).
James
https://codereview.appspot.com/6742061/diff/2001/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
https://codereview.appspot.com/6
David Kastrup writes:
> If it is ok with people, I'd propose the following course in order to
> get the ball rolling again:
>
> I'll merge stable/2.16 into translation. That should be unproblematic.
> Then I'll merge translation into staging. This will require a bit of
> cleanup and conflict re
David Kastrup writes:
> David Kastrup writes:
>
>> If it is ok with people, I'd propose the following course in order to
>> get the ball rolling again:
>>
>> I'll merge stable/2.16 into translation. That should be unproblematic.
>> Then I'll merge translation into staging. This will require a
Graham Percival writes:
Dear Graham,
> I guess it's time to make it official: I'm stepping down as
> project manager.
Thank you so much for all your initiatives and the enormous amounts of
effort you spent on LilyPond. You started from some kind of vacuum and
created a vibrating community.
I'm
David Kastrup writes:
> David Kastrup writes:
>
>> David Kastrup writes:
>>
>>> If it is ok with people, I'd propose the following course in order to
>>> get the ball rolling again:
>>>
>>> I'll merge stable/2.16 into translation. That should be unproblematic.
>>> Then I'll merge translation i
2012/10/22 David Kastrup :
>> So that leaves the po files. Should I merge them over from translation
>> or not?
>>
>> Francisco, any idea?
>
> Turns out that running "make po-update" on the current version I arrived
> at leaves stuff unchanged.
Then do nothing. (Can you 'do nothing'?) I am not su
Reviewers: J_lowe,
Message:
James,
thanks for your remarks and corrections!
Some answers (partly preliminal) are listed below.
https://codereview.appspot.com/6742061/diff/2001/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
https://codereview.appspot.c
Here is another problem with translations that is rather curious:
commit bf1900d44f4937fe8e69e0e04e188a0c3daf5172
Author: Francisco Vila
Date: Thu May 31 11:18:26 2012 +0200
has some bit of English content in here that is totally out of place:
+@code{\tweak} now takes an optional layout objec
2012/10/22 David Kastrup :
>
> Here is another problem with translations that is rather curious:
> commit bf1900d44f4937fe8e69e0e04e188a0c3daf5172
> Author: Francisco Vila
> Date: Thu May 31 11:18:26 2012 +0200
>
> has some bit of English content in here that is totally out of place:
>
I first
Francisco Vila writes:
> 2012/10/22 David Kastrup :
>>
>> Here is another problem with translations that is rather curious:
>> commit bf1900d44f4937fe8e69e0e04e188a0c3daf5172
>> Author: Francisco Vila
>> Date: Thu May 31 11:18:26 2012 +0200
>>
>> has some bit of English content in here that is
Dear developers,
is there a reason that the forced accidental must not be written before
the octavation? It took me some time to figure out which order does compile.
(a) This works: cis'!='
(b) This doesn't: cis!'='
However, I would consider (b) more logical as the exclamation mark
forces the
Joram Berger writes:
> Dear developers,
>
> is there a reason that the forced accidental must not be written before
> the octavation? It took me some time to figure out which order does compile.
>
> (a) This works: cis'!='
> (b) This doesn't: cis!'='
>
> However, I would consider (b) more logic
2012/10/23 David Kastrup :
> Francisco Vila writes:
>
>> 2012/10/22 David Kastrup :
>>>
>>> Here is another problem with translations that is rather curious:
>>> commit bf1900d44f4937fe8e69e0e04e188a0c3daf5172
>>> Author: Francisco Vila
>>> Date: Thu May 31 11:18:26 2012 +0200
>>>
>>> has some
Francisco Vila writes:
> 2012/10/23 David Kastrup :
>
>> Well, the problem more or less is that changes.tely (in English or in
>> Spanish) does not have a \version header. I don't really know whether
>> this is intentional. It is possible that it is, in order to be able to
>> show before/after
Folks,
as discussed some weeks ago, I've now pushed the reformatted
GNUmakefile to staging. There are only whitespace changes.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
While investigating issue 2266, I found this wrong link in CG.
Find micro-patch attached
0001-CG-fixed-wrong-link-to-Contact-in-web.patch
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listi
Hi,
could the lilypond options to specify the output file format be unified?
Currently, depending on the format, there are different options:
--pdf or --formats=pdf (and ps and png)
-dbackend=svg (eps, scm, …)
Even though things are perhaps a little bit different, I would suggest
to include svg
30 matches
Mail list logo
