Of course. It is certainly more consistent to translate all comments,
and we could add a small notice saying
//Original comments are in English; you can read them in the English
version of this page (scroll to the bottom to find the link).//
Do translators agree on this?
sounds like a go
Use git to determine when the translation last changed instead of
relying on the "GIT Committish" line.
The downside of this patch is that a simple typo fix in the original
documentation still requires an update of the translation; otherwise
"make check-translation" will continue to complain abou
Johannes Schindelin <[EMAIL PROTECTED]> writes:
> Use git to determine when the translation last changed instead of
> relying on the "GIT Committish" line.
Thanks for helping to solve this silly Git issue. However, I do not
understand, how can Git know what original version was translated?
It i
A bit off-topic:
Well, I don't know anything about python, but have to say that the
current script doesnt't work for me or I didn't understand it so far.
That is, I just did the check-translation and it showed fatal error
about some git comment numbers. So I changed *all* commitishes that were
John Mandereau wrote:
The only common thing between lilypond.org sources and LilyPond sources
is the git.sv.gnu.org repository. It's better to create another local
repository for the LilyPond sources, so you can work simultaneously on
the site and on the program sources without switching branc
Le samedi 13 janvier 2007 à 14:29 +0200, Till Rettig a écrit :
>
> > Of course. It is certainly more consistent to translate all comments,
> > and we could add a small notice saying
> >
> > //Original comments are in English; you can read them in the English
> > version of this page (scroll to th
Le samedi 13 janvier 2007 à 14:56 +0100, Jan Nieuwenhuizen a écrit :
> Johannes Schindelin <[EMAIL PROTECTED]> writes:
>
> > Use git to determine when the translation last changed instead of
> > relying on the "GIT Committish" line.
>
> Thanks for helping to solve this silly Git issue. However,
Le samedi 13 janvier 2007 à 16:45 +0200, Till Rettig a écrit :
> A bit off-topic:
> Well, I don't know anything about python, but have to say that the
> current script doesnt't work for me or I didn't understand it so far.
If you find something unclear or missing in the README, please let me
know.
Le samedi 13 janvier 2007 à 16:49 +0200, Till Rettig a écrit :
> Hi John,
>
> just updated the German pages in three steps, also included now two
> other files (de/switch/new-notation.html and de/documentation.html).
>
> but two issues remain:
>
> I always get patch files from older patches tha
Le samedi 13 janvier 2007 à 02:30 +0100, Francisco Vila a écrit :
> ... And the patch itself is here attached.
Thanks, applied.
> El sáb, 13 de ene de 2007, a las 02:24:55 +0100, Francisco Vila dijo:
> > This first patch is a kind of test to see y I am doing it well. I
> > think that have followe
Le samedi 13 janvier 2007 à 00:04 -0600, Daniel Tonda Castillo a écrit :
> Ok, I attach the es.po. Found out the problem, whenever I load the es.po
> in kbabel, and open the header, it changes the encoding field to
> ISO-8859-1. I made sure that the file was saved as UTF-8. Then checked
> with l
Hi,
something seems completely wrong here:
\version "2.11.7"
\relative c {
#(set-octavation 1)
b4~
#(set-octavation 2)
b4~
#(set-octavation 1)
b4~
#(set-octavation 0)
b4
}
all pitches should be the same (and lilypond obviously thinks so as it
prints the slurs) but the octaves are messed up
12 matches
Mail list logo
