Skip to content
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

Use "Save" in Metadata Editor and remove "SaveChanges". #6212

Merged

Conversation

bluemoehre
Copy link
Contributor

Unified/merged Save & SaveChanges translations.

Changes

  • Merged both into SaveChanges
    • because this key was more recent in commit history
    • and is more accurate about the context
  • Use of shortest value to prevent unnecessary line-breaks in UI & save space
  • Double checked all translations with ChatGPT 4o
    • should be common for a software context
    • and for saving or applying user input

Issues

#6211

@bluemoehre bluemoehre requested a review from a team as a code owner October 16, 2024 18:10
@jellyfin-bot
Copy link
Collaborator

jellyfin-bot commented Oct 16, 2024

Cloudflare Pages deployment

Latest commit a98ae40
Status ✅ Deployed!
Preview URL https://b5bf90c9.jellyfin-web.pages.dev
Type 🔀 Preview

View build logs

@dmitrylyzo
Copy link
Contributor

Given the fact that we shouldn't directly change any language other than en-us, I would do the opposite: use Save because it is translated (for almost every language).

FYI, other languages should only be edited with Weblate to avoid conflicts.

@bluemoehre
Copy link
Contributor Author

Technically, I have no problems with changing it back to Save, but the reasoning (above) still makes sense to me, especially if I compare all the rest of the keys.

FYI, other languages should only be edited with Weblate to avoid conflicts.

It's a one-click in my IDE to convert everything. Will it cause problems that way?

@thornbill
Copy link
Member

Yes it does cause issues, and we do not accept llm generated translations.

@bluemoehre
Copy link
Contributor Author

we do not accept llm generated translations.

It's not LLM generated translations! It's just checked by LLM because I didn't know if the older or newer version was the one to take. So it's just for everyone's assurance to not only rely on me. (Obviously fixing a long time bug which affects all language files is nothing easy without automation)

Yes it does cause issues

How can I change this PR so we can get rid of the duplicates, without doing everything manually?

@dmitrylyzo
Copy link
Contributor

How can I change this PR so we can get rid of the duplicates, without doing everything manually?

Since we only need to narrow the text:

  1. Revert all.
  2. Change SaveChanges to Save in src/components/metadataEditor/metadataEditor.template.html.
  3. Remove SaveChanges from src/strings/en-us.json (since it's no longer in use). Weblate will remove it from other languages.

@bluemoehre
Copy link
Contributor Author

@dmitrylyzo done as you suggested. For DE it's fine. Native speakers of the respective languages (FR, PT, BU, etc.) must adapt their buttons themselves, then.

@thornbill
Copy link
Member

Sorry for misunderstanding your GPT comment before.

Our weblate system will remove the translations in other languages once it is removed from the primary language. If the "Save" translation is problematic that would be concerning since it is already used in similar edit dialogs/screens.

@thornbill thornbill added the cleanup Cleanup of legacy code or code smells label Oct 17, 2024
@dmitrylyzo dmitrylyzo changed the title Fix duplicate "Save" vs "SaveChanges" translation (all languages) Use "Save" in Metadata Editor and remove "SaveChanges". Oct 18, 2024
Copy link
Contributor

@dmitrylyzo dmitrylyzo left a comment

Choose a reason for hiding this comment

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

LGTM. Merge with squash.
I have changed the PR title, but it can be improved if necessary.

@bluemoehre bluemoehre force-pushed the remove-duplicate-save-button-labels branch from 07fbe54 to a98ae40 Compare October 18, 2024 13:58
Copy link

@thornbill thornbill added this to the v10.10.0 milestone Oct 20, 2024
@thornbill thornbill merged commit 5e5b3ab into jellyfin:master Oct 20, 2024
14 checks passed
@bluemoehre bluemoehre deleted the remove-duplicate-save-button-labels branch October 20, 2024 11:34
@bluemoehre
Copy link
Contributor Author

Thanks everyone! 🙂👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Cleanup of legacy code or code smells
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants