refactor(i18n): update dictionary with source-based keys and Spanish translations - #69
refactor(i18n): update dictionary with source-based keys and Spanish translations#69zeedif wants to merge 1 commit into
Conversation
…translations - Restructured `combinedMessages.prod.ts` to use natural English source strings as primary localization keys, removing the deprecated dot-notation identifier pattern. - Extracted hardcoded UI text from library components into the `$msg` localization system. - Added comprehensive Spanish (`es`) translations for all newly migrated and extracted entries, keeping only `def` and `es` for new items. Note: This update acts as the foundational dictionary support for the comprehensive UI i18n migration in the main `obsidian-livesync` repository.
|
It looks like |
|
Thank you very much for this contribution. While preparing v1.0.0, we changed the project boundary: application translations and dialogues now live in the main Self-hosted LiveSync repository, while Commonlib keeps its canonical English service messages and translation-injection boundary. This should make future contributions easier to locate, understand, and merge. I am sorry to ask for additional work after you prepared this PR. Would you be willing to open a new PR against Self-hosted LiveSync using the current structure? Thank you again for your contribution and patience. |
2 participants
combinedMessages.prod.tsto use natural English source strings as primary localization keys, removing the deprecated dot-notation identifier pattern.$msglocalization system.es) translations for all newly migrated and extracted entries, keeping onlydefandesfor new items.Note: This update acts as the foundational dictionary support for the comprehensive UI i18n migration in the main
obsidian-livesyncrepository.