Il 01/11/2011 20:32, Francisco Vila ha scritto:
I do not see this output especially abnormal. As you know, from this
output you will obtain one of
-- changes to lilypond code. You should ignore it.
-- changes to translations doctitleXX or texidocXX other than yours.
Ignore those, too.
2011/11/3 Federico Bruni fedel...@gmail.com:
On the other hand, I thought (and still think) that the right committish,
which keeps tracking information AND gives a terse check-translation output,
should exist for these files.
Not necesarily, because snippets change. That is where garbage comes
On Tue, Nov 01, 2011 at 03:02:14PM +, Adam Spiers wrote:
Sorry for hijacking this thread, but I just noticed that what you are
discussing may relate to a problem I just mentioned elsewhere in the
RFC: \hideNote thread - running makelsr.py introduces spurious blank
lines prior to lines
Il 31/10/2011 21:05, Francisco Vila ha scritto:
you haven't applied it yet, right?
Now it is; please pull, test it and tell me.
Ok, thanks.
Well, I had tested it before and I knew what it would have happened.
'make check-translation' is a mess now.
If you run this command you'll see what I
Hi Francisco,
Il 24/10/2011 10:17, Francisco Vila ha scritto:
I will apply it [when at home] and let's see.
you haven't applied it yet, right?
I think that as long as the docs compile, your translations are there
and up to date, and we have not too many warnings, it is enough
headache for
2011/10/31 Federico Bruni fedel...@gmail.com:
Hi Francisco,
Il 24/10/2011 10:17, Francisco Vila ha scritto:
I will apply it [when at home] and let's see.
you haven't applied it yet, right?
Now it is; please pull, test it and tell me.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org ,
2011/10/23 Federico Bruni fedel...@gmail.com:
I've almost gave up here.
I don't have skills nor time to spend on this issue, sorry.
I understand it. It is probably my fault, to be unable of explaining
it more clearly. _I_ am sorry.
The attached patch fixes the bad object error.
I have no
I've almost gave up here.
I don't have skills nor time to spend on this issue, sorry.
The attached patch fixes the bad object error.
I have no idea if it's correct and how the updating of .texidoc files works.
make check-translation still looks weird to me, but I won't care for now
What
Il 10/10/2011 00:28, Francisco Vila ha scritto:
2011/10/9 Federico Brunifedel...@gmail.com:
I've tried:
cd Documentation/it/texidocs
sed -i
's/514674cb00c18629242dfcde0c1a4976758adc56/34607d3e36a93030690ccd780a7ffce621ca1e0f/g'
*.texidoc
But it doesn't seem to be the right committish.
What
2011/10/10 Federico Bruni fedel...@gmail.com:
But it doesn't seem to be the right committish.
What exactly did you do to find out this committish? That could be
right, it matches a commit by you in which you run makelsr.py, so it
shouldn't give any bad object messages.
I checked the log of
2011/10/9 Federico Bruni fedel...@gmail.com:
I've tried:
cd Documentation/it/texidocs
sed -i
's/514674cb00c18629242dfcde0c1a4976758adc56/34607d3e36a93030690ccd780a7ffce621ca1e0f/g'
*.texidoc
But it doesn't seem to be the right committish.
What exactly did you do to find out this
11 matches
Mail list logo
