[translations] Re: Translation of the website to German

[Till Paala <till.rettig@xxxxxx>]

Hi John,

John Mandereau schrieb:

Le lundi 18 janvier 2010 à 23:17 +0200, Till Paala a écrit :
  

thanks for the fast answer now I got the right address :-)
    

What do you mean?  If you write to lilypond-user, I will most likely
miss your mail, as I only have a quick glance at subject titles now and
then; if you write to -devel, which I read much more, I may overlook it
too...  I just added a (maybe dense) note in the CG (Contributors'
Guide) for this.
  

Sorry about the misunderstanding: I sent the mail from an own address not known to the lilynet group so it never appeared there. I don't know why you didn't get it personally, but I don't care anymore since you got it now.

You should remove all text in English in nodes you didn't translate at
all; then, if node names of empty nodes (i.e. nodes containing only
"@untranslated") are already translated and the associated sectioning
command is immediately followed with @translationof, then it's OK, this
is the first strategy (and the old one) proposed in the Note I mentioned
just above.
  

Ok, I guess it is fine that I will mark translated text after the @untranslated with @ignore tags so it is kind of empty.

There is no problem per se with translating section Community, although
it may not make sense translating everything, and you may take distance
from the original text, depending on what you know the community in your
language is willing to support, which is possible only if you
personnally assume this support, or there exists a public forum or
mailing list listed in Community for LilyPond in your language:

- "Bug reports" should be translated only if you know that every bug
report sent on your language's mailing list or forum will be handled by
someone who will translate it to English and send it on bug-lilypond or
add an issue in the tracker, then translate back the reply from
developers.

- "Help us" should be translated very freely: ask help for contributing
to LilyPond for tasks that LilyPond community in your language is able
and going to handle.

I just added this piece of info to the CG BTW.
  

Thanks for the hints, I will see into that at some point. For now the text is just a translation of what was there in English, but I will add warnings about sending only English messages to appropriate addresses/mailing lists. I think the text shouldn't though leave out anything mentioned on the English pages -- it might be just more convenvient for a German speaking person to read the instructions in German but act in English. A hint might also be appropriate that encourages asking help for a bug report on the German lilypond forum etc.

Can you tell me exactly what you couldn't figure out?  If it's Git
vocabulary, look it up from Git documentation (man pages and manuals;
especially, "git rebase" man page shows commented graphs that might make
help you understand the hints I gave you).  I can't find in the CG where
I propose to modify the committishes after having rebased, where have
you seen it?  In the CG, it is also clearly recommended to not pull with
rebasing (2.3.2 Pushing and rebasing) for translators, and there is no
real need to require rebasing anyway, so I can't support you more on
this issue than the hints I already gave you.
  

Yes, I pulled with -r option so this would mean "rebasing". I did it because otherwise there are numerous "merging" commitishes coming from me. Once pushed after a rebase I guess I just can add the current commitish to all modified files and push again. This would surely mean that I miss some commitments that have happened in the time I was editing the files. So another way would be to pick some commitish about five days ago and take this one. Please remark if my commitishes won't work with the translation status check!

Greetings
Till

Best,
John