Skip to content

Conversation

@efb4f5ff-1298-471a-8973-3d47447115dc
Copy link
Member

@efb4f5ff-1298-471a-8973-3d47447115dc efb4f5ff-1298-471a-8973-3d47447115dc commented Nov 12, 2025

Pull Request Type

  • Chore

Related issue

#5000

Description

This PR is drafted because i'd like to reach a consensus on the changes first before i change all the related files

Notable changes:
https://github.com/efb4f5ff-1298-471a-8973-3d47447115dc/FreeTube/blob/5c7be48e038b60e32366ca591bcf8c1f65e351b9/static/locales/en-US.yaml#L4-L26 is made the same as browser and other Electron application menu bars

General rules of thumb im adhering to in all my PR's:

  • Apply proper punctuation when using multiple sentences to both the key and value
  • Remove punctuation when using one sentence (95% already does this so i just make it consistent)
  • Apply proper casing to abbreviations if its being used already to both the key and value
  • Apply proper casing when a specific setting or button is being named in a message (e.g. If you want to import your subscriptions you can go to **Data settings** and select **Import subscriptions** or you can search for a channel and subscribe to them.)

Testing

Look around in the UI to check that sentence casing has been applied properly

Desktop

  • OS: Windows 11
  • OS Version: 24H2

Comment on lines 32 to 36
Version {versionNumber} is now available! Click for more details.: Version {versionNumber} is now available! Click
for more details.
Download from site: Download from site
A new blog is now available, {blogTitle}. Click to view more.: A new blog is now available, {blogTitle}.
Click to view more.
Copy link
Member

Choose a reason for hiding this comment

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

I would prefer to keep periods out keys if possible, as it makes using the translation strings more annoying t('parent.key without a period') vs t('parent["key with . a period"]'), I don't mind adding them to the values/the actual strings.

Off-topic: I would prefer to use shorter keys in general, even if that means that the key doesn't match the text.

@github-actions
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions
Copy link
Contributor

Conflicts have been resolved. A maintainer will review the pull request shortly.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants