[pl] Polish translation of the 'Contribution' chapter

[dkarczmarski]

I've recently translated the 'contribution' chapter into Polish language
and most of it I pushed into repository ( the remaining part I will push in 2 days ).

I faced some problems, and I'm not sure how to solve all of them.
I want to encourage you to discuss with me. I would like to present my solution
and alternative solution to make it easier to find right one.

Because there are about 30 files and there are different reviews assigned I would like
to agree on a common version of how corrections should be made.

At the beginning I want to present what are my principals what I follow
when I do translations:

1. The English version is the canonical source. It is the source of truth.
2. I translate everything exactly as it is - every sentence.
   I don't add anything, and I don't leave anything out.
   This translation is a mirror of the English version in Polish.
3. This is not a poem :) so it is more important to provide
   a good source of translated knowledge than to write in beautiful Polish.
   So I translate each English sentence into a Polish sentence:
   • I don’t merge sentences.
   • I don’t split sentences.
   • I don’t change the order of sentences.

My Polish language teacher at school told me that technical language might be
a little different from literary language because its main goal is precision.
Things that are considered mistakes in regular language are acceptable in technical language.
For example, the repetition of a technical term in a sentence.
Even if it is possible to replace it with a synonym, we often don’t do it,
and the same word is repeated in the same sentence.

Because the English the language is an IT language, so we people in Poland very often use
some English words as they were Polish. I'm not sure if it is completely correct,
but as my teacher said, language is dynamic, and changes over time, to follow
changes in world. For example 'pull request' or 'commit' - it is possible
to translate it to Polish, but nobody does it. And moreover,
probably if I said 'zatwierdzenie' lub 'żądanie ściągnięcia' nobody would understand it.
But when you say "zrób commit", then everybody knowns that it is about "git commit".

In contrast to English, in Polish words are declined through cases, with various prefixes and suffixes.
For example:

I did a commit - Zrobiłem commit
In this commit - W tym commicie
Add it to this commmit - Dodaj to tego commmita

We spoke this way in everyday conversation.

commit vs contribution

the word "contribution" can be translated into Polish as "kontrybucja",
but it works differently than the "commit" word , because in "commit"
we keep the original spelling of this word.
We don't write it as "komit".

Am I right?

shortcode

English language is very smart when it comes to creating new words.
When we say "shortcode" in a Polish sentence, everybody knows what it means.
It is possible to translate it into some form of "skrót" but IMO it is not good.
It's better to use it as it is.

In Polish, when you use an English word that ends with a vowel, you can use
an apostrophe to create a Polish form, for example:

Dodaj obok tego shortcode'a

BTW: Very often we can see this method is use for words that don't end with a vowel,
and even though it may not be entirely correct, IMO it is often very useful.

IMO it is very convenient to use it in the same way as the word "commit",
for example:

Dodaj obok tego shortcoda

How do you think about it ?

wrangler

There are two roles : issue wrangler and PR wrangler . It is easy to translate it
into Polish, for example: "Koordynator zgłoszeń".
But IMO the word "wragler" is so specific that it is reasonable to Polishify
this word into "wrangler zgłoszeń" i "wrangle PR / wrangler pull requestów"
because it is so precise that it's almost impossible to mistake for something else.

#49655 (comment)

untranslatable

There are sentences that lose their sense when you translate it,
or they make sense only in the English language.
For example:

{{< table caption = "Do and Don't - Używaj notacji PascalCase dla obiektów API" >}}
Zalecane | Niezalecane
:--| :-----
A PodList object is a list of pods. | A Pod List object is a list of pods.
{{< /table >}}

This kind of mistake we can do only in English language. I could skip it in translation
but because English language is an IT language, and we use English when we write posts, comments,
I kept it in English version because I still consider it valuable advice.

links

When we have a sentence with link and a name in capital letters, how should we translate it into Polish.
Should we keep capital letters too?
For example:

English:

The following examples focus on capitalization. For more information about formatting
API object names, review the related guidance on [Code Style](#code-style-inline-code).

Polish:

Poniższe przykłady koncentrują się na kapitalizacji. Aby uzyskać więcej informacji na temat formatowania
nazw obiektów API, zapoznaj się z powiązanymi wskazówkami dotyczącymi [Stylu Kodowania](#code-style-inline-code).

What the form should we choose:

• ...wskazówkami dotyczącymi [Stylu Kodowania]
• ...wskazówkami dotyczącymi [stylu kodowania]
  ?

How do you think?

key words / emphasized words

Is it always justified to translate into Polish ?
For example, the "namespace" word:

English:

Kubernetes uses the word _resource_ to refer to API resources. For example,
the URL path `/apis/apps/v1/namespaces/default/deployments/my-app` represents a
Deployment named "my-app" in the "default"
{{< glossary_tooltip text="namespace" term_id="namespace" >}}.

Polish:

Kubernetes używa słowa _zasób_ w odniesieniu do zasobów API. Na
przykład, ścieżka URL `/apis/apps/v1/namespaces/default/deployments/my-app`
reprezentuje Deployment o nazwie "my-app" w "default"
{{< glossary_tooltip text="namespace" term_id="namespace" >}}. 

nit:

According to:
https://kubernetes.io/docs/contribute/review/reviewing-prs/#other
there is:

As a reviewer, if you identify small issues with a PR that aren't essential to the meaning, 
such as typos or incorrect whitespace, prefix your comments with nit:. This lets the author 
know that this part of your feedback is non-critical.

My idea is to ask reviewers to mark their review comment as "nit:" when they meet this rule.
I would like to prepare one large PR with all minor non-critical fixes
for all files in the "contribution" chapter, to make it consistent.

[dkarczmarski]

I would like to notify about this post all people who are viewers or who left a comment. So far :
@kpucynski
@mfilocha
@nvtkaszpir
@sftim

[mfilocha]

Thanks @dkarczmarski for your contribution and the explanation of your approach!

I added my first set of comments to #49668 (review) - let's start with it to align on common standards to make localisation reasonable consistent.

[dkarczmarski]

Polish polite form "a Ty chcesz"

In Polish, we have a polite form of address, and we write "Ty" (you)
with a capital letter as a sign of respect. For example:

English:

Use this method to include sample YAML files when the sample is generic and
reusable, and you want the reader to try it out themselves.

Polish:

Użyj tej metody, aby dołączyć przykładowe pliki YAML, gdy są
one ogólne i wielokrotnego użytku, a Ty chcesz, aby czytelnik sam ją wypróbował.

Should we you that form in translations? Is it ok or is unnecessary?

[dkarczmarski]

[en] shortcode - [pl] kod / kody

According to :
#49668 (comment)
we translate "shortcode" into Polish "kod / kodu" .

This occurs on many pages and I will fix them all according to the guideline.

[dkarczmarski]

[en] Kubernetes - [pl] Kubernetesa / Kubernetesach

According to :
#49657 (comment)
and
https://kubernetes.io/pl/docs/contribute/localization-pl/#odmiana-terminu-kubernetes
we should decline the word "Kubernetes".

I will review all my translations and I will fix it soon.

IMO: it might be "nit:" :)

[mfilocha]

For localization/translation efforts, most of PR comments are "nits" - unless you have a really bad translation, which is not the case here :).

[dkarczmarski]

For localization/translation efforts, most of PR comments are "nits" - unless you have a really bad translation, which is not the case here :).

Actually, you are right :))

[dkarczmarski]

[en] Reference - [pl] Materiały źródłowe

this word ( Reference ) might appear in many places in the documentation. to maintain consistency, I added it here to have a common pattern.

I translated it the same way as it was already translated in another place.