Polish translation update.

[arekm]

PL diacritics and some unification. Lengths have changed in few cases.

druk - jako proces
wydruk - jako produkt
wyładuj (zamiast rozładuj)
kanał (nie slot)
katalog (nie folder)
podręcznik (nie instrukcja)
firmware (krótsze; nie oprogramowanie układowe)
bazowanie (nie zerowanie bo zerowanie może wiele rzeczy oznaczać)
nieudane (zamiast nie powiódł się bo krótsze)

[arekm]

Ok, so these "cols=20" comments are hard limits, right?

[github-actions]

Target	ΔFlash (bytes)	ΔSRAM (bytes)
MK3S_MULTILANG	0	0
MK3_MULTILANG	0	0

[3d-gussner]

Ok, so these "cols=20" comments are hard limits, right?

Yes the c=xx r=y are hard limits. You can use lang-check.py --information to show all messages and pages.
I used that for German as there it is allowed to split words with a - (German can have very very long words) to fit it better on one page.
Try to get everything on one page (20x4) and not to have only one word on next page. Sometimes \n is useful to force a new line but use this only if necessary.

[3d-gussner]

Here the output for the Polish translation.

polish_messages.txt

I will ask the internal Polish translator to review these changes.

Thanks a lot.

Sidenote: Vscode Polish spellchecker shows still lot of issues BUT a native speaking person should beat any spell checker.

[3d-gussner]

@arekm If you have translations with c=20 r>=5 and you get an error/warning it is not an big issue we can expand it, ONLY if really needed.

As each char costs at least two bytes of the resources. I limited the rows to the max used of all translations.
See it more as a warning that you exceed the limit other languages have been able to squeeze in the translations.

Real hard limits

• c<20 are used in menus and selections and very limited. We need to get a toggle menu within a row
• c=20
• c=20 r=2 Messages with two row selections
• c=20 r=3 Messages with last row selections
• c=20 r=4 Some of these message are limited to one page only

[leptun]

@3d-gussner Please ping me when this PR is merged since I want to rebase the diacritics PR after this is merged

[leptun]

@3d-gussner Now that I think about it, I think it would be better if the diacritics PR was merged first, then we rebase this PR on top of the latest MK3 branch, test this PR again, then merge it. Does this sound good?

[leptun]

Rebased and fixed the conflict

[3d-gussner]

Reviewed internally and approved

@arekm Bardzo dziękuję za ten pull request

[3d-gussner]

@arekm See video #3383

[arekm]

Bed / hotend strings not marked as translatable at 3:28 ?

"Najpierw" twice at beginning of two sentences, one after another. Hmm, could change one occurrence to something else to not repeat it that often (3:13 and 3:17).