Thomas Rast venit, vidit, dixit 15.09.2010 11:47: > Hi Christian > > Christian Stimming wrote: >> >> As you might guess, as the (initial) translator of git-gui I've been >> through this discussion before [1] and as you have noticed, I have >> decided to take a translation approach different from what you have >> recently discussed here. I deliberately tried to translate as much of >> the terms into German as possible. I do not agree about the importance >> of statements on this mailing list like "This translation translates >> too much terms - I cannot find the commands I'm used to". > [...] >> Instead, a translation is for people who do neither know nor >> understand the English wording for the git concepts. For this target >> audience, the goal is to find a set of terms for the different git >> concepts which makes the concepts most easily accessible for their >> language. This may or may not include terms which are left at English >> words. > > Maybe there should be two sets of translations then. > > I'm only half serious, but the problem here is what I said earlier in > the thread (referring to Jan's draft): > > } In any case it roughly matches (or still stays slightly on the > } more-German side of) the colloquial usage in my group, if that is > } any indication. > > "My group" is a bunch of CS researchers, so I can't say they fall > outside the description above. However, in our work we observe a very > funny split between translating and keeping the terms in English: > > graph Graph > vertex Knoten > edge Kante > directed gerichtet > DAG (directed acyclic graph) DAG > independent set independent set > cut (vertex, edge) cut (vertex, edge) > degree Grad > matching Matching > tree Baum > MST (minimum spanning tree) MST (minimaler Spannbaum) > > There are German terms for all the untranslated ones, but I rarely > hear them in practical usage. Books probably go for a full > translation since they want to be normative (how should I know, it's > been a while since I used a German book), but lectures stick to the > half-translated version. Any active graduate student or researcher is used to English articles and books and doesn't need a translation at all, or could do completely with a translated glossary. I assume we do the (extensive!) translation work for people who could not use Git without a translation. And that mandates translating as much as possible (including man pages...). As far as the various disciplines go, CS is always on the side of importing more terms from English rather than translating. If we agree that a group of CS researchers is the target I'm fine with it - but it would imply backing out l10n ;) Note that I don't want to create any bad feelings against the l10n efforts. If it is done then I want it to be done right and not rushed, a bad one does more harm than anything. I probably won't be contributing to translations of commands, but I'm in for the glossary to help it have a sound start. Michael -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html