From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: Jakub Narebski <jnareb@gmail.com>
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: Tue, 04 Oct 2011 10:23:48 +0200 [thread overview]
Message-ID: <4E8AC294.2060608@in.waw.pl> (raw)
In-Reply-To: <201110032337.09975.jnareb@gmail.com>
On 10/03/2011 11:37 PM, Jakub Narebski wrote:
+# Terminologia dla kluczowych terminów z Subversion:
+# 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'
+# version control - zarządzanie wersjami
+# repository - repozytorium
+# branch - odgałęzienie
'gałąź'? I think that's the translation which is used in informal
conversations.
+# 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.
+# merge - łączenie zmian
'łączenie gałęzi'?
+# 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'
+# 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'.
+# obliteration - obliteracja
'wymazanie'?
+# patch - łata
+# notes - adnotacja
Zbyszek
next prev parent reply other threads:[~2011-10-04 8:23 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 [this message]
2011-10-07 22:11 ` Jakub Narebski
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=4E8AC294.2060608@in.waw.pl \
--to=zbyszek@in.waw.pl \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=saper@saper.info \
/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).