Christian Stimming <christian@xxxxxxxxxxxx> writes: > Dear Pratyush, > > thanks for the first evaluation. > > Am Samstag, 25. Januar 2020, 17:56:29 CET schrieb Pratyush Yadav: >> > Subject: Re: [PATCH 2/3] git-gui: update german translation >> >> Nitpick: capitalise "german". So, s/german/German/ > > Of course I can do that... however, the capitalization of the headline is > somewhat different every time in the repository. The first word is lower case, > yes, but e.g. the language adjective is sometimes upper case, sometimes lower > case. > >> On 24/01/20 10:33PM, Christian Stimming via GitGitGadget wrote: >> > From: Christian Stimming <christian@xxxxxxxxxxxx> >> > >> > Switch several terms from uncommon translations back to english >> > vocabulary, most prominently commit (noun, verb) and repository. Adapt >> > glossary and translation accordingly. >> >> Can you also explain _why_ these uncommon translations are changed to >> English vocabulary? > > I've written an explanation in the cover letter email. Do you want to have it > copied into the commit message? It is unclear to me how these translation patches were split into three. I am sort-of guessing that 1/3 is only to cover the new entries in .pot that have no corresponding entries in translation, and the rest is to update/fix existing translations, but I do not know how these changes are split between 2/3 and 3/3. In any case, "we must update original translation that does not match accepted computer lingo" you wrote in the cover letter sounds like a very good justification to record in the commit that updates/fixes the existing entries.
