On 12/25/09 8:13 PM, "Mark Polesky" wrote:
> Carl Sorensen wrote:> As I think more about this, I wonder if there should be
> a
>> short and sweet summary for experienced Linux developers,
>> followed by a gentle (and longer) introduction for the
>> Windows guys.
>
> Actually, I'm thinking the
Carl Sorensen wrote:> As I think more about this, I wonder if there should be a
> short and sweet summary for experienced Linux developers,
> followed by a gentle (and longer) introduction for the
> Windows guys.
Actually, I'm thinking there should be a short and sweet
summary for the GUI-based co
The attached patch lets me build xrefs by looking at
Documentation/*.tely
directly, instead of looking at the corresponding
Documentation/out-www/*.texi
files.
This would be very nice for the website, since we can't build all of
lilypond on the server. (the alternative is to generate the xref
Le jeudi 24 décembre 2009 à 20:45 +, Graham Percival a écrit :
> Looks fine to me, and nothing broken while doing an out-of-tree build
> from scratch.
Pushed. I finally decided to keep the diff generation, because this
allows us to reliably catch hash collisions, and with last doc build I
onl
Le vendredi 25 décembre 2009 à 23:56 +, Graham Percival a écrit :
> I agree that if we make the change, we'd need to have lots of warning about
> it.
>
> If we want to do the change, there's two possibilities:
>
> 1) ask the savannah people to change the name.
If we go for this, which I wou
2009/12/25 John Mandereau :
> Le vendredi 25 décembre 2009 à 22:04 +, Graham Percival a écrit :
>> Should we ask the -user-fr
>> people to accept a name change to lilypond-fr ?
>
> This is perfectly acceptable, and I think a confirmation of Valentin,
> the other administrator, will be enough
2009/12/25 John Mandereau :
> Then the software should be fixed. The lack of proper UTF-8 support is
> really a pity in 2009 (2010 soon).
Oh, I definitely agree! But that's outside my control.
> I'd rather not attach too many things to google code project, for the
> sake of our independence, wh
Le vendredi 25 décembre 2009 à 22:04 +, Graham Percival a écrit :
> My tentative answer is that we could create an official
> language-specific list for any translation that finished the
> top-priority items (IIRC, the website + Learning 1 Tutorial).
> Thoughts?
This is basically what happened
Le vendredi 25 décembre 2009 à 22:08 +, Graham Percival a écrit :
> 3) Given that there's some kind of problems with accents with
> savannah lists (I haven't grasped what it is, but read
> https://savannah.gnu.org/task/?9148
> if you're interested), is it really good to have these non-English
Le vendredi 25 décembre 2009 à 22:17 +, Graham Percival a écrit :
> The regtests are not used in the docs. Period.
>
> It's possible that a new feature might a file in
> Documentation/snippets/new/ which is an exact copy of a new
> regtest (actually, I've encouraged this), but we don't have m
On Fri, Dec 25, 2009 at 11:21:17AM +0100, John Mandereau wrote:
> Le jeudi 24 décembre 2009 à 22:21 +0100, Reinhold Kainhofer a écrit :
> > I would definitely like that option. Every now and then, when working with
> > lilypond-book based projects, I also need to send e.g. an image per mail or
>
On Fri, Dec 25, 2009 at 11:02:03AM +0100, John Mandereau wrote:
> Le jeudi 24 décembre 2009 à 20:52 +, Graham Percival a écrit :
> > I can now confirm that the regtest comparison is done on the files in
> > input/regression/out-test/ , which are created via "make test".
>
> More precisely, the
On Fri, Dec 25, 2009 at 10:04 PM, Graham Percival
wrote:
> But before we do this, I'd like to
> settle a few questions:
Oops, I forgot to add
3) Given that there's some kind of problems with accents with
savannah lists (I haven't grasped what it is, but read
https://savannah.gnu.org/task/?9148
On Thu, Dec 24, 2009 at 12:55 AM, Carl Sorensen wrote:
>
> On 12/23/09 5:37 PM, "Francisco Vila" wrote:
>
>> "Ask the LilyPond mantainer to create the list in their project. "
>
> So all we need to do is get Graham, Jan, or Han-Wen to add a list
> lilypond-es. I think we could get one of them
Le vendredi 25 décembre 2009 à 14:57 +, Graham Percival a écrit :
> I was wondering if I was wrong about texinfo. It's been known to
> happen.
Texinfo is not a well-defined language, it's defined only by what the
formatters support and to some extent by Texinfo manual, so it's
practically imp
On Fri, Dec 25, 2009 at 03:54:06PM +0100, John Mandereau wrote:
> Le vendredi 25 décembre 2009 à 14:29 +, Graham Percival a écrit :
> > > ..but see Texi2HTML warnings if "@insertcopying{}" is used.
> >
> > I know about those warnings.
>
> Then, why the mao do you waste our time with this thre
Le vendredi 25 décembre 2009 à 14:29 +, Graham Percival a écrit :
> > ..but see Texi2HTML warnings if "@insertcopying{}" is used.
>
> I know about those warnings.
Then, why the mao do you waste our time with this thread? :-)
> I guess that in this case, it doesn't really matter.
Indeed, th
On Fri, Dec 25, 2009 at 11:22:21AM +0100, John Mandereau wrote:
> Le jeudi 24 décembre 2009 à 21:17 +, Graham Percival a écrit :
> > commit 6c1cdaa331972442a8fd62d98da5adebfaa9a17b
> >
> > I thought that texinfo macros were supposed to have a {} after them --
> > I mean, it's not /required/ fo
Le jeudi 10 décembre 2009 à 15:50 +, Graham Percival a écrit :
> Ok. Let's just agree to disagree: you think it's important, but I
> don't think it's important. If somebody (be it you or Denes)
> writes a patch, I'm willing to test it on GUB.
I just tried factorizing French macro definitions
Best wishes to you and the development team as well!
Op vrijdag 25-12-2009 om 11:13 uur [tijdzone +0100], schreef John
Mandereau:
> Le vendredi 25 décembre 2009 à 08:52 +0100, Erwin Poeze a écrit :
> > Sorry, about this. It was done by me, the TP coordinator. I have the
> > habit of checking for n
Le jeudi 24 décembre 2009 à 21:17 +, Graham Percival a écrit :
> commit 6c1cdaa331972442a8fd62d98da5adebfaa9a17b
>
> I thought that texinfo macros were supposed to have a {} after them --
> I mean, it's not /required/ for arguments without any macros, but...?
..but see Texi2HTML warnings if "
Le jeudi 24 décembre 2009 à 22:21 +0100, Reinhold Kainhofer a écrit :
> I would definitely like that option. Every now and then, when working with
> lilypond-book based projects, I also need to send e.g. an image per mail or
> insert an image into some word-processing app. In these cases, such an
Le jeudi 24 décembre 2009 à 10:18 -0800, Patrick McCarty a écrit :
> Thank you for noticing this, John. I'll admit I did not think through
> the issue carefully enough when I made that commit.
>
> I'm not qualified to comment on your patch to fix the issue, but I
> trust your judgment here.
OK,
Le vendredi 25 décembre 2009 à 08:52 +0100, Erwin Poeze a écrit :
> Sorry, about this. It was done by me, the TP coordinator. I have the
> habit of checking for newer domain versions on an irregular base and
> noticed that the 2.13.7 was newer that the 2.13.3 version in the TP.
> Getting new versio
Le jeudi 24 décembre 2009 à 19:30 +, Graham Percival a écrit :
> Ah, we're talking about two different kinds of hashes. One hash
> decides if the snippet should be (re)processed -- I don't care
> about that one. Do whatever seems sensible for that.
>
> The other kind of hashing produces the
Le jeudi 24 décembre 2009 à 20:52 +, Graham Percival a écrit :
> I can now confirm that the regtest comparison is done on the files in
> input/regression/out-test/ , which are created via "make test".
More precisely, the comparison is done between
input/regression/out-test/ and input/regressio
On Fri, Dec 25, 2009 at 12:25 AM, James Bailey
wrote:
>
> On 24.12.2009, at 23:57, Joe Neeman wrote:
>>
>>> profile-property-access.ly errors and fails when I try to compile it.
>>> Additionally, the properties shown in the output are all 0
>>
>> You need to configure with --disable-optimising in
On 24.12.2009, at 23:57, Joe Neeman wrote:
profile-property-access.ly errors and fails when I try to compile it.
Additionally, the properties shown in the output are all 0
You need to configure with --disable-optimising in order for property
access profiling to work.
Okay, since I can't com
28 matches
Mail list logo
