Skip to content

Conversation

@Paurikova2
Copy link
Contributor

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!

  • My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
  • My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
  • My PR passes ESLint validation using npm run lint
  • My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
  • My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
  • My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
  • My PR aligns with Accessibility guidelines if it makes changes to the user interface.
  • My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
  • My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
  • If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
  • If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
  • If my PR fixes an issue ticket, I've linked them together.

* 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",

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


// "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?",
Copy link

@kuchtiak-ufal kuchtiak-ufal Dec 11, 2025

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.

Copy link
Contributor

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 tdonohue added i18n / l10n Internationalisation and localisation, related to message catalogs 1 APPROVAL pull request only requires a single approval to merge labels Dec 15, 2025
@tdonohue tdonohue moved this to 🙋 Needs Reviewers Assigned in DSpace 10.0 Release Dec 15, 2025
@tdonohue tdonohue added the port to main This PR needs to be ported to `main` branch for the next major release label Dec 16, 2025
Copy link
Member

@tdonohue tdonohue left a 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.

@github-project-automation github-project-automation bot moved this from 🙋 Needs Reviewers Assigned to 👍 Reviewer Approved in DSpace 10.0 Release Dec 16, 2025
@tdonohue tdonohue added this to the 9.2 milestone Dec 16, 2025
@tdonohue tdonohue merged commit a7ddef1 into DSpace:dspace-9_x Dec 16, 2025
15 checks passed
@github-project-automation github-project-automation bot moved this from 👍 Reviewer Approved to ✅ Done in DSpace Maintenance (9.x, 8.x, 7.6.x) Dec 16, 2025
@dspace-bot
Copy link
Contributor

Successfully created backport PR for main:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1 APPROVAL pull request only requires a single approval to merge i18n / l10n Internationalisation and localisation, related to message catalogs port to main This PR needs to be ported to `main` branch for the next major release

Projects

Development

Successfully merging this pull request may close these issues.

5 participants