-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(theme-translations): complete Polish translations #7214
Conversation
Hi @rev4324! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
✅ [V2]Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-7214--docusaurus-2.netlify.app/ |
LGMT, thank you for the translation updates @rev4324! 👍 I can also help with filling remaining gaps in i18n files, if you don't want to continue working on the translation. |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
No problem, I'll look into translating the remaining sentences in other files soon. Glad I could help. |
Thanks! There are a few missing in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally this look nice, I have suggested adding missing plural forms, Polish language uses three by default, and Docusausaurs supports it:
Additionally, I have suggested the alteration for the "image" translation, which suites the context a bit more, and it's more widely used on the web, ex. Google etc.
packages/docusaurus-theme-translations/locales/pl/plugin-ideal-image.json
Outdated
Show resolved
Hide resolved
packages/docusaurus-theme-translations/locales/pl/plugin-ideal-image.json
Outdated
Show resolved
Hide resolved
packages/docusaurus-theme-translations/locales/pl/plugin-ideal-image.json
Outdated
Show resolved
Hide resolved
packages/docusaurus-theme-translations/locales/pl/theme-common.json
Outdated
Show resolved
Hide resolved
packages/docusaurus-theme-translations/locales/pl/theme-search-algolia.json
Outdated
Show resolved
Hide resolved
@Simek Out of plain curiosity:
(Docusaurus interprets multiple pluralizations in the order I wonder which ones your translations correspond to? |
Oh, I see. I was wondering why there are two pipes in a row in some translations ( Polish forms are different for "one", "two-four", "five+" and I have used this order in the suggestions. I'm curious to what ranges |
According to my tests, "few" is 2-4, and "many" is 5+. "other" seems to be non-integers, so it's irrelevant here. If we are already ordering the plurals in that order (one|few|many) it should be good! |
@rev4324 Please take a look at the suggestions above ^^ I'll apply those changes and merge tomorrow if there are no further opinions. |
Just FYI, the range section is a bit overcomplicated in there, generally the range end form is used for the whole range pluralization, which also can be seen in the most right column. In other words the form of start of the range doesn't matter in i18n context. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
…-algolia.json Co-authored-by: Bartosz Kaszubowski <[email protected]>
….json Co-authored-by: Bartosz Kaszubowski <[email protected]>
…-image.json Co-authored-by: Bartosz Kaszubowski <[email protected]>
…-image.json Co-authored-by: Bartosz Kaszubowski <[email protected]>
…-image.json Co-authored-by: Bartosz Kaszubowski <[email protected]>
Thanks for the suggestions, you're right about the "image" translation, your way fits better. Also, I didn't know about the distinction between "few" and "many", since the source that I edited had only one of these two forms. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Motivation
Have you read the Contributing Guidelines on pull requests?
Test Plan
Related PRs