git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>,
	"Marcin Cieślak" <saper@saper.info>
Subject: Re: [PATCH] po/pl.po: Eliminate fuzzy translations
Date: Sat, 8 Oct 2011 00:11:14 +0200	[thread overview]
Message-ID: <201110080011.14757.jnareb@gmail.com> (raw)
In-Reply-To: <4E8AC294.2060608@in.waw.pl>

On Tue, 4 Oct 2011, Zbigniew Jędrzejewski-Szmek wrote:
> On 10/03/2011 11:37 PM, Jakub Narebski wrote:
>>
>> +# Terminologia dla kluczowych terminów z Subversion:

As I probably should write in the commit message, this terminology
is taken directly from Subversion's po/pl.po file.  Subversion has
IMHO quite good Polish translation.

On the other hand no other *.po file in Git has glossary in
comments...

>> +# path - ścieżka
>> +# URL - URL
>> +# file - plik
>> +# directory - katalog
>> +# update - aktualizacja
>> +# commit - zatwierdzenie, zatwierdzenie zmian
>
> This seems kind of awkward. E.g. 'initial commit' would become 
> 'początkowe zatwierdzenie zmian' or 'pierwsze zatwierdzenie', which just 
> doesn't sound right. What about starting with the mercurial term 
> 'changeset'? Git users also use 'commit' to mean 'change', so maybe
> the polish translation of this crucial term should be 'zmiana':
> 'initial commit' -- 'początkowa zmiana' or 'pierwsza zmiana'
> 'commit message' -- 'opis zmiany'

The problem is that "commit" might be a verb ('to commit'), where I think
"zatwierdzenie zmian" is a good translation, and "commit" might also be
used as a noun ('a commit'), where I think it should be probably translated
as "wersja" (eng. version) or "zmiana" (eng. change).

Nb. it is a good idea to take into account existing Mercurial translation
into Polish.
 
>> +# version control - zarządzanie wersjami
>> +# repository - repozytorium
>> +# branch - odgałęzienie
>
> 'gałąź'? I think that's the translation which is used in informal 
> conversations.

"Odgałęzienie" is what Subversion uses, but you are right that "gałąź"
might be better.  Though in this case the glossary cannot be marked
as coming from Subversion...
 
>> +# tag - tag
>
> 'metka', 'etykieta' according to the dictionary. I'm aware of 'metka'
> being used in CS anywhere, but it is short, and pretty cool, IMO.

I think that "etykieta" (eng. label) has already established different
meaning in Polish computer terminology for a "goto label".

"Metka" might be a good solution (it is mainly used in Polish to mean
textile labels), though I wonder if using English term "tag" (which
in Polish is used in computer science to mean metadata tag or markup
language tag) wouldn't be better as it is already computer term.
 
>> +# merge - łączenie zmian
>
> 'łączenie gałęzi'?

Well, in Subversion it is about merging changes, not branches ;-)))
 
>> +# conflict - konflikt
>> +# property - atrybut
>> +# revision - wersja
>> +# log message - opis zmian
>> +# entry/item - element
>> +# ancestry - pochodzenie
>> +# ancestor - przodek
>> +# working copy - kopia robocza
>> +# working dir - bieżący katalog
>> +# usage - wykorzystanie
>
> 'użycie', 'wywołanie'?
> E.g. 'standardowe wywołanie tego programu to: prog arg'

I'd have to check how other programs translate this.  I think
at least "usage: " in '-h' output is translated as "użycie: ",
though I am not sure if it is really a good translation to recommend.
 
>> +# source - źródłowy
>> +# destination - docelowy
>> +# hook - skrypt (skrypt repozytorium)
>> +# exclude - wykluczyć
>> +# crop - obciąć
>> +# cache - pamięć podręczna
>> +# child - obiekt podrzędny
>
> Standard CS term is 'ojciec' and 'syn' for 'parent/child'.

Right.
 
>> +# obliteration - obliteracja
>
> 'wymazanie'?

Well, anyway I don't think this is needed for git translation.
 
>> +# patch - łata
>> +# notes - adnotacja

-- 
Jakub Narebski
Poland

  reply	other threads:[~2011-10-07 22:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 19:34 Git's translations need to be updated for submission Ævar Arnfjörð Bjarmason
2011-07-07  6:10 ` [PATCH] po/hi.po: Eliminate fuzzy translations Ramkumar Ramachandra
2011-07-07 11:58   ` Ævar Arnfjörð Bjarmason
2011-07-07  9:53 ` [PATCH] po/pl.po: " Jakub Narebski
2011-10-03 18:30   ` Ævar Arnfjörð Bjarmason
2011-10-03 18:39     ` Ævar Arnfjörð Bjarmason
2011-10-03 21:37     ` Jakub Narebski
2011-10-04  8:23       ` Zbigniew Jędrzejewski-Szmek
2011-10-07 22:11         ` Jakub Narebski [this message]
2011-07-08 19:45 ` Git's translations need to be updated for submission Jan Engelhardt
2011-07-09 16:45   ` Ævar Arnfjörð Bjarmason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201110080011.14757.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=saper@saper.info \
    --cc=zbyszek@in.waw.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).