Update pt-PT.json5#2706
Conversation
Addition of new translation keys (following DSpace 7.6.1 release) & revision/improvement of some of the already existing.
Addition of new translation keys (following DSpace 7.6.1 release) & revision/improvement of some of the already existing.
tdonohue
added
i18n / l10n
paulo-graca
left a comment
paulo-graca
left a comment
There was a problem hiding this comment.
Thank you @rsaraivac for this contribution! I've just some comments, could you can check if they make sense to you?
| "admin.registries.schema.title": "Registo de esquemas de metadados", | ||
|
|
||
| // "admin.access-control.bulk-access.breadcrumbs": "Bulk Access Management", | ||
| "admin.access-control.bulk-access.breadcrumbs": "Gestão do acesso em lote", |
There was a problem hiding this comment.
Could you consider to change to:
"Gestão de permissões" or "Gestão de permissões em lote"
| "admin.registries.bitstream-formats.title": "Registo de formatos de ficheiro", | ||
|
|
||
| // "admin.registries.bitstream-formats.select": "Select bitstream format", | ||
| "admin.registries.bitstream-formats.select": "Selecionar formato de 'bitstream'", |
There was a problem hiding this comment.
Can you consider to use "ficheiro" to be coeherent?
| // "search.filters.namedresourcetype.Workspace": "Workspace", | ||
| "search.filters.namedresourcetype.Workspace": "Por terminar", | ||
| // "access-control-limit-to-specific": "Limit the changes to specific bitstreams", | ||
| "access-control-limit-to-specific": "Limitar as alterações a 'bitstreams' específicos", |
There was a problem hiding this comment.
Can you use "ficheiro" instead of "bitstream"?
| "access-control-limit-to-specific": "Limitar as alterações a 'bitstreams' específicos", | ||
|
|
||
| // "access-control-process-all-bitstreams": "Update all the bitstreams in the item", | ||
| "access-control-process-all-bitstreams": "Atualizar todos os 'bitstreams' no item", |
There was a problem hiding this comment.
Can you use "ficheiro" instead of "bitstream"?
| "access-control-process-all-bitstreams": "Atualizar todos os 'bitstreams' no item", | ||
|
|
||
| // "access-control-bitstreams-selected": "bitstreams selected", | ||
| "access-control-bitstreams-selected": "bitstreams selecionados", |
There was a problem hiding this comment.
Can you use "ficheiro" instead of "bitstream"?
| "access-control-bitstreams-selected": "bitstreams selecionados", | ||
|
|
||
| // "access-control-bitstreams-select": "Select bitstreams", | ||
| "access-control-bitstreams-select": "Selecionar 'bitstreams'", |
There was a problem hiding this comment.
Can you use "ficheiro" instead of "bitstream"?
| "access-control-remove": "Remover condição de acesso", | ||
|
|
||
| // "access-control-select-bitstreams-modal.title": "Select bitstreams", | ||
| "access-control-select-bitstreams-modal.title": "Selecionar 'bitstreams'", |
There was a problem hiding this comment.
Can you use "ficheiro" instead of "bitstream"?
| // "mydspace.status.mydspaceWaitingController": "Waiting for Controller", | ||
| "mydspace.status.mydspaceWaitingController": "Aguarda validador", | ||
| // "access-control-bitstream-toggle.enable": "Enable option to perform changes on the bitstreams", | ||
| "access-control-bitstream-toggle.enable": "Ativar a opção para efetuar alterações nos 'bitstreams'", |
There was a problem hiding this comment.
Can you use "ficheiro" instead of "bitstream"?
| // "mydspace.status.mydspaceWorkflow": "Workflow", | ||
| "mydspace.status.mydspaceWorkflow": "Em fluxo de trabalho", | ||
| // "access-control-bitstream-toggle.disable": "Disable option to perform changes on the bitstreams", | ||
| "access-control-bitstream-toggle.disable": "Desativar a opção para efetuar alterações nos 'bitstreams'", |
There was a problem hiding this comment.
Can you use "ficheiro" instead of "bitstream"?
|
@rsaraivac : If you'd like this to be considered for 8.0 (and backported to 7.x), please address the feedback above. Otherwise, we'll need to reschedule for 9.0 |
Revision and improvement of some of the already existing translation keys upon reviewers’ suggestions.
|
@paulo-graca : Could you give this a re-review? It looks like your feedback has been addressed. |
@tdonohue Hi, thanks for this reminder and support. I've just reviewed the translations accordingly to the suggestions and introduced some other minor improvements. |
paulo-graca
left a comment
paulo-graca
left a comment
There was a problem hiding this comment.
Thank you @rsaraivac!
|
Successfully created backport PR for |
tdonohue
removed
the
port to dspace-7_x
4 participants
Addition of new translation keys (following DSpace 7.6.1 release) & revision/improvement of some of the already existing.
References
Add references/links to any related issues or PRs. These may include:
issue-number(if this fixes an issue ticket)pr-number(if a REST API PR is required to test this)Description
Short summary of changes (1-2 sentences).
Instructions for Reviewers
Please add a more detailed description of the changes made by your PR. At a minimum, providing a bulleted list of changes in your PR is helpful to reviewers.
List of changes in this PR:
Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!
yarn lintyarn check-circ-deps)package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.