Skip to content

i18n: Translate new keys for pt-BR #4962

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.

Sign up for GitHub

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

Jump to bottom
Open
JohnnyMendesC wants to merge 1 commit into
base: main
Choose a base branch
from
Open

i18n: Translate new keys for pt-BR #4962

JohnnyMendesC wants to merge 1 commit into from

Conversation

@JohnnyMendesC
Copy link

@JohnnyMendesC JohnnyMendesC commented Dec 30, 2025

References

  • No specific issue ticket. Addresses pending translation keys in the codebase.

Description

This PR updates the Portuguese (Brazil) translation file (src/assets/i18n/pt-BR.json5). It addresses approximately 290 keys previously marked as // TODO New key - Add a translation and // TODO Source message changed - Revise the translation, covering generic messages, admin curation tasks, bitstream formats, external login, and LDN/COAR Notify services.

Instructions for Reviewers

List of changes in this PR:

  • Translated ~290 keys marked as TODO.
  • Removed the // TODO New key - Add a translation and // TODO Source message changed - Revise the translation.

Guidance for testing:

  1. Switch the UI language to Português (Brasil).
  2. Verify that the newly translated keys (e.g., in Admin > Curation Tasks or LDN Services) appear correctly and are not falling back to English.

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.

@tdonohue tdonohue added i18n / l10n Internationalisation and localisation, related to message catalogs 1 APPROVAL pull request only requires a single approval to merge labels Jan 5, 2026
@tdonohue tdonohue moved this to 🙋 Needs Reviewers Assigned in DSpace 10.0 Release Jan 5, 2026
@t-rodrigues t-rodrigues mentioned this pull request Jan 14, 2026
Closed
12 tasks
t-rodrigues
t-rodrigues suggested changes Jan 14, 2026
View reviewed changes
Copy link
Contributor

@t-rodrigues t-rodrigues left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’ve reviewed the pull request and left a few minor suggestions, mostly related to wording and consistency.
Overall, looks good.

Revisei o pull request e deixei algumas sugestões, principalmente relacionadas à escrita e à consistência.

src/assets/i18n/pt-BR.json5
@@ -460,20 +459,16 @@
"admin.access-control.epeople.table.edit.buttons.remove": "Excluir \"{{name}}\"",

// "admin.access-control.epeople.table.edit.buttons.remove.modal.header": "Delete Group \"{{ dsoName }}\"",
// TODO New key - Add a translation
"admin.access-control.epeople.table.edit.buttons.remove.modal.header": "Delete Group \"{{ dsoName }}\"",
"admin.access-control.epeople.table.edit.buttons.remove.modal.header": "Deletar grupo \"{{ dsoName }}\"",
Copy link
Contributor

@t-rodrigues t-rodrigues Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"admin.access-control.epeople.table.edit.buttons.remove.modal.header": "Deletar grupo \"{{ dsoName }}\"",
"admin.access-control.epeople.table.edit.buttons.remove.modal.header": "Excluir Grupo \"{{ dsoName }}\"",

Anteriormente foi utilizado "Excluir" no lugar de "Deletar".

src/assets/i18n/pt-BR.json5

// "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": "Você tem certeza de que quer deletar o grupo \"{{ dsoName }}\" e todas as políticas associadas a ele?",
Copy link
Contributor

@t-rodrigues t-rodrigues Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"admin.access-control.epeople.table.edit.buttons.remove.modal.info": "Você tem certeza de que quer deletar o grupo \"{{ dsoName }}\" e todas as políticas associadas a ele?",
"admin.access-control.epeople.table.edit.buttons.remove.modal.info": "Você tem certeza de que quer excluir o Grupo \"{{ dsoName }}\" e todas as políticas associadas a ele?",

src/assets/i18n/pt-BR.json5

// "admin.access-control.epeople.table.edit.buttons.remove.modal.confirm": "Delete",
// TODO New key - Add a translation
"admin.access-control.epeople.table.edit.buttons.remove.modal.confirm": "Delete",
"admin.access-control.epeople.table.edit.buttons.remove.modal.confirm": "Deletar",
Copy link
Contributor

@t-rodrigues t-rodrigues Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"admin.access-control.epeople.table.edit.buttons.remove.modal.confirm": "Deletar",
"admin.access-control.epeople.table.edit.buttons.remove.modal.confirm": "Excluir",

src/assets/i18n/pt-BR.json5
@@ -669,8 +663,7 @@
"admin.access-control.groups.form.delete-group.modal.header": "Excluir grupo \"{{ dsoName }}\"",

// "admin.access-control.groups.form.delete-group.modal.info": "Are you sure you want to delete Group \"{{ dsoName }}\" and all its associated policies?",
// TODO Source message changed - Revise the translation
"admin.access-control.groups.form.delete-group.modal.info": "Você tem certeza que quer excluir o grupo \"{{ dsoName }}\"",
"admin.access-control.groups.form.delete-group.modal.info": "Você tem certeza que quer deletar o grupo \"{{ dsoName }}\" e todas as políticas associadas a ele?",
Copy link
Contributor

@t-rodrigues t-rodrigues Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"admin.access-control.groups.form.delete-group.modal.info": "Você tem certeza que quer deletar o grupo \"{{ dsoName }}\" e todas as políticas associadas a ele?",
"admin.access-control.groups.form.delete-group.modal.info": "Você tem certeza que quer excluir o Grupo \"{{ dsoName }}\" e todas as políticas associadas a ele?",

src/assets/i18n/pt-BR.json5
@@ -2317,20 +2298,16 @@
"comcol-role.edit.delete.error.title": "Falha ao excluir a função '{{ role }}' do cargo",

// "comcol-role.edit.delete.modal.header": "Delete Group \"{{ dsoName }}\"",
// TODO New key - Add a translation
"comcol-role.edit.delete.modal.header": "Delete Group \"{{ dsoName }}\"",
"comcol-role.edit.delete.modal.header": "Deletar grupo \"{{ dsoName }}\"",
Copy link
Contributor

@t-rodrigues t-rodrigues Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"comcol-role.edit.delete.modal.header": "Deletar grupo \"{{ dsoName }}\"",
"comcol-role.edit.delete.modal.header": "Excluir Grupo \"{{ dsoName }}\"",

src/assets/i18n/pt-BR.json5

// "submission.sections.describe.relationship-lookup.selection-tab.title.openalexInstitution": "Search Results",
// TODO New key - Add a translation
"submission.sections.describe.relationship-lookup.selection-tab.title.openalexInstitution": "Search Results",
"submission.sections.describe.relationship-lookup.selection-tab.title.openalexInstitution": "Resultados da pesquisa",
Copy link
Contributor

@t-rodrigues t-rodrigues Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"submission.sections.describe.relationship-lookup.selection-tab.title.openalexInstitution": "Resultados da pesquisa",
"submission.sections.describe.relationship-lookup.selection-tab.title.openalexInstitution": "Resultados da Pesquisa",

src/assets/i18n/pt-BR.json5

// "submission.sections.describe.relationship-lookup.selection-tab.title.openalexPublisher": "Search Results",
// TODO New key - Add a translation
"submission.sections.describe.relationship-lookup.selection-tab.title.openalexPublisher": "Search Results",
"submission.sections.describe.relationship-lookup.selection-tab.title.openalexPublisher": "Resultados da pesquisa",
Copy link
Contributor

@t-rodrigues t-rodrigues Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"submission.sections.describe.relationship-lookup.selection-tab.title.openalexPublisher": "Resultados da pesquisa",
"submission.sections.describe.relationship-lookup.selection-tab.title.openalexPublisher": "Resultados da Pesquisa",

src/assets/i18n/pt-BR.json5

// "submission.sections.describe.relationship-lookup.selection-tab.title.openalexFunder": "Search Results",
// TODO New key - Add a translation
"submission.sections.describe.relationship-lookup.selection-tab.title.openalexFunder": "Search Results",
"submission.sections.describe.relationship-lookup.selection-tab.title.openalexFunder": "Resultados da pesquisa",
Copy link
Contributor

@t-rodrigues t-rodrigues Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"submission.sections.describe.relationship-lookup.selection-tab.title.openalexFunder": "Resultados da pesquisa",
"submission.sections.describe.relationship-lookup.selection-tab.title.openalexFunder": "Resultados da Pesquisa",

src/assets/i18n/pt-BR.json5

// "submission.sections.describe.relationship-lookup.selection-tab.title.dataciteProject": "Search Results",
// TODO New key - Add a translation
"submission.sections.describe.relationship-lookup.selection-tab.title.dataciteProject": "Search Results",
"submission.sections.describe.relationship-lookup.selection-tab.title.dataciteProject": "Resultados da pesquisa",
Copy link
Contributor

@t-rodrigues t-rodrigues Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"submission.sections.describe.relationship-lookup.selection-tab.title.dataciteProject": "Resultados da pesquisa",
"submission.sections.describe.relationship-lookup.selection-tab.title.dataciteProject": "Resultados da Pesquisa",

src/assets/i18n/pt-BR.json5

// "external-login-page.orcid-confirmation.netid": "Account Identifier",
// TODO New key - Add a translation
"external-login-page.orcid-confirmation.netid": "Account Identifier",
"external-login-page.orcid-confirmation.netid": "Identificador da conta",
Copy link
Contributor

@t-rodrigues t-rodrigues Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"external-login-page.orcid-confirmation.netid": "Identificador da conta",
"external-login-page.orcid-confirmation.netid": "Identificador da Conta",

@github-project-automation github-project-automation bot moved this from 🙋 Needs Reviewers Assigned to 👀 Under Review in DSpace 10.0 Release Jan 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@t-rodrigues t-rodrigues t-rodrigues requested changes

Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees

@JohnnyMendesC JohnnyMendesC

Labels

1 APPROVAL pull request only requires a single approval to merge i18n / l10n Internationalisation and localisation, related to message catalogs

Projects

DSpace 10.0 Release
Status: 👀 Under Review

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@JohnnyMendesC @t-rodrigues @tdonohue