pl: Add mostly-machine-translated Polish translation

[pierd]

Partial Polish translation

https://github.com/google/comprehensive-rust/issues/399

[mgeisler]

Thanks a lot @pierd! I've reached out to people in Google to find someone who can skim through the translation here.

I know from translating into Danish that there are a lot of paragraphs where I wasn't sure about the best translation. If that was the case here too, then I hope you can work with the reviewer to find a good solution :smile:

To the reviewer: you can download the rendered course from the bottom of the test run.

[pierd]

No worries. Please note that this is a work in progress, as far as I remember I finished chapters 1-10 (assuming nothing changed in the original text since March).

I'm happy to iterate here to bring it to a state where full chapters/sections/days are done so it's easy for others to contribute too.

[mgeisler]

assuming nothing changed in the original text since March

I'm afraid there has been a bunch of typo fixes since then -- but you'll see that when you run msgmerge with an updated messages.pot file. A bunch of the translations will then be marked as fuzzy since the English original has changed. Fixing those should be fairly easy since the Polish translation presumably didn't copy the typos :smile:

[mgeisler]

@jkotur, here is the PR we talked about.

[pierd]

Thanks for the comments everyone! ❤️

@pawelpaa - I think something is broken on GitHub UI because a bunch of your comments are attached to a single line, I've applied some of them where I could find the problem from the context but for a few I'm not sure what they refer to

@jkotur - I've committed some of your suggestions through the web interface which means you are now listed as a co-author (congrats 😉), unfortunately this triggers GitHub action for CLA check. @mgeisler does it mean that @jkotur will have to sign the agreement?

[mgeisler]

unfortunately this triggers GitHub action for CLA check. @mgeisler does it mean that @jkotur will have to sign the agreement?

Hmm... yeah, I see... there is a mixup of email addresses here. @jkotur is a Googlers so it should be fine, but the personal email address confused the system. I can probably fix it somehow, I'll take a look :smile:

[jkotur]

Sorry for the delay, I'm back now and I'll continue the review.

@pierd - can you squash my personal email out of this PR? Unless it's easy to replace it with my corp address. I've changed my default email so from now on CLA check should be fine with my suggestions.

[pierd]

Squashed to clean co-authors (for the CLA check)

[mgeisler]

Thanks a lot, @pierd!