Skip to content

Adjust unnecessary capitalization in English i18n strings #4192

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

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

Conversation

alanorth
Copy link
Contributor

@alanorth alanorth commented Apr 15, 2025

Description

We don't need to be capitalizing "Community" and "Collection" in the user interface unless they are at the beginning of a sentence or in a title/header. They are not proper nouns and look out of place.

Screenshot 2025-04-15 at 18-49-09 Test collection

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:

  • Update several occurrences of "Community" and "Collection" and one "Item" in English i18n strings

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.

Build the user interface and make sure you can see the new strings. One place these strings occur is in the success message after creating a community or collection, for example.

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.

We don't need to be capitalizing "Community" and "Collection" in
the user interface unless they are at the beginning of a sentence
or in a title, header, or bread crumb. They are not proper nouns
and they look out of place when capitalized.
@alanorth alanorth added improvement i18n / l10n Internationalisation and localisation, related to message catalogs quick win Pull request is small in size & should be easy to review and/or merge ux User Experience related works affects: main Issue impacts "main" (latest release). labels Apr 15, 2025
@tdonohue tdonohue moved this to 🙋 Needs Reviewers Assigned in DSpace 9.0 Release Apr 15, 2025
Copy link
Member

@kshepherd kshepherd left a comment

Choose a reason for hiding this comment

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

+1, thanks @alanorth , I agree this makes the English more consistent. Almost all references to "item" and "bitstream" use lowercase when not beginning a sentence, and they are even more fundamental "DSpace terms" that appear in messages

@github-project-automation github-project-automation bot moved this from 🙋 Needs Reviewers Assigned to 👍 Reviewer Approved in DSpace 9.0 Release Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects: main Issue impacts "main" (latest release). i18n / l10n Internationalisation and localisation, related to message catalogs improvement quick win Pull request is small in size & should be easy to review and/or merge ux User Experience related works
Projects
Status: 👍 Reviewer Approved
Development

Successfully merging this pull request may close these issues.

2 participants