Re: [PATCH] Fix typos on pt_BR/gittutorial.txt translation

[Junio C Hamano <gitster@pobox.com>]

Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com> writes:

> On Thu, Jul 30, 2009 at 04:53:39PM -0700, Junio C Hamano wrote:
>> Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com> writes:
>> 
>> > I'd rather remove the linux example and use something else (like git
>> > itself), since the Documentation is not about linux, as Juno says and
>> > that would stop the disagreements.
>>
>> That is unacceptable, _if_ you are adding a _translated_ version of our
>> primary documentation.
>
> I can't agree more. In that view, would you agree to remove any mention
> to linux in the primary version?

You must be kidding.

If the situation were that the word "Linux kernel" cannot be translated
correctly to many languages, it may make good sense to use a more commonly
known example in the original (and translated) text.  But as far as I can
tell from this thread so far, Portuguese speakers in the tech field would
understand which project you are referring to when you say either "kernel
do linux" or "o kernel linux" just fine.  Avoiding the "Linux kernel"
example only because you have some language lawyering tendency feels just
plain silly.

First of all, I never said anything about "stopping the disagreements".

You can do your disagreement with other people in Portuguese speaking
community all you want.  I only asked you to do your disagreeing with them
in _other forums_.  Do it in your blog, in your own Linux tutorial or git
documentation, or whatever.  I really do not care, and I do not want to
get involved.

But not in our documentation, whose original uses the Linux kernel as an
example, simply because that's the original proeject git came from.

Pick whichever word you feel is the most appropriate translation, and send
in an update (or a pull request), and let's get this round of typofixes
over with in the first place.  I do not care if that version said "kernel
do linux" or "o kernel linux".

If enough people care deeply about one way or another like you seem to do,
they can send in further updates and I may (or may not) pick it up to
reverse whatever choice you make in that version.  But that will be in a
later round.  Let's not let this block other noncontroversial and
obviously correct updates, Ok?