Skip to content

Localization improvements and Indonesian Support#1806

Open
adlifarizi wants to merge 3 commits intotheovilardo:masterfrom
adlifarizi:feat/i18n-improvements
Open

Localization improvements and Indonesian Support#1806
adlifarizi wants to merge 3 commits intotheovilardo:masterfrom
adlifarizi:feat/i18n-improvements

Conversation

@adlifarizi
Copy link
Copy Markdown
Contributor

Summary

  • Move more hardcoded strings into resources xml.
  • Add Simplified Chinese to language selector.
  • Add Indonesian language support (values-in).

Note

There still some hardcoded strings which I can't cover for now. Current state is good enough for localization, but surely future improvements is recommended.
Current full translation is English, Spain, Chinese (Simplified), and Indonesian. France and Russia is not fully translated by community.

…ardcoded strings

- **Internationalization**:
    - Added Simplified Chinese (`zh-CN`) to supported languages in `AppLanguage`.
    - Implemented full Simplified Chinese translations for settings, batch actions, and library states.
    - Updated Spanish translations for new settings and empty state strings.
- **UI/UX**:
    - Refactored `LibraryEmptyState` and `PlaylistContainer` to use localized string resources instead of hardcoded English text.
    - Added comprehensive "Empty State" messaging for Songs, Albums, Artists, Folders, and Playlists, with specific variants for local and cloud filters.
    - Added localized labels for "Minimum Tracks per Album" and "Album Art Cache Limit" in the settings screen.
- **Settings**:
    - Added a toggle for Simplified Chinese in the language selection settings.
    - Localized the "Minimum Tracks per Album" slider label.
@rebornloki-dev
Copy link
Copy Markdown
Contributor

Hey! This PR is really helpful, especially the move away from hardcoded strings.

I tested it locally and it improves localization consistency a lot. As the French localization contributor, I’m still refining some translations (French can be tricky with context 😅), and having everything properly in resources will make that much easier and more accurate.

This looks like a great step forward 👍

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.

2 participants