-
Notifications
You must be signed in to change notification settings - Fork 504
Update Czech translations to DSpace9 #4933
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
Update Czech translations to DSpace9 #4933
Conversation
* Merge pull request DSpace#4641 from dataquest-dev/update-czech-translations [WIP] Added czech translations to `cs.json5` * WIP translations of untranslated czech messages * Translated all czech messages * Revised changed translations * check grammer, fix errors * Translated back from context * Review of translations --------- Co-authored-by: Tim Donohue <tim.donohue@lyrasis.org> Co-authored-by: Matus Kasak <matus.kasak@dataquest.sk> Co-authored-by: milanmajchrak <90026355+milanmajchrak@users.noreply.github.com> Co-authored-by: Paurikova2 <michaela.paurikova@dataquest.sk>
| @@ -821,439 +795,334 @@ | |||
| "admin.access-control.groups.form.subgroups-list.notification.failure.subgroupToAddIsActiveGroup": "Toto je aktuální skupina, nelze přidat.", | |||
|
|
|||
| // "admin.access-control.groups.form.subgroups-list.no-items": "No groups found with this in their name or this as UUID", | |||
| "admin.access-control.groups.form.subgroups-list.no-items": "Nebyla nalezena žádná skupina s tímto v návzvu nebo UUID", | |||
| "admin.access-control.groups.form.subgroups-list.no-items": "Nebyla nalezena žádná skupina s tímto názvem nebo UUID", | |||
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.
This should be the same as one above:
Nebyla nalezena žádná skupina s tímto textem v názvu nebo s tímto UUID
src/assets/i18n/cs.json5
Outdated
|
|
||
| // "admin.access-control.epeople.table.edit.buttons.remove.modal.info": "Are you sure you want to delete Group \"{{ dsoName }}\" and all its associated policies?", | ||
| // TODO New key - Add a translation | ||
| "admin.access-control.epeople.table.edit.buttons.remove.modal.info": "Are you sure you want to delete Group \"{{ dsoName }}\" and all its associated policies?", | ||
| "admin.access-control.epeople.table.edit.buttons.remove.modal.info": "Opravdu chcete odstranit skupinu \"{{ dsoName }}\" a všechny s ní související zásady?", |
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.
Somewhere, for policies, we use "politiky" somewhere "zasady".
Should be consistent, though both seem to me strange.
May be "pravidla" would be better in this case.
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.
Should we use "pravidla" for policies everywhere?
Like "resource policies", "item's policies", etc
tdonohue
left a comment
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.
👍 Thanks @Paurikova2 ! I tested this out today and verified the new translations are all loading properly. In order to get these updates in the next 9.x release, I'm going to merge this immediately.
|
Successfully created backport PR for |
Description
Updated Czech translations.
Instructions for Reviewers
Check the grammar.
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!
mainbranch of code (unless it is a backport or is fixing an issue specific to an older branch).npm run lintnpm run check-circ-deps)package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.