feat: add i18n translations (es-ES, pt-PT)#67
Open
Cubel89 wants to merge 2 commits intoBowserinator:masterfrom
Open
feat: add i18n translations (es-ES, pt-PT)#67Cubel89 wants to merge 2 commits intoBowserinator:masterfrom
Cubel89 wants to merge 2 commits intoBowserinator:masterfrom
Conversation
Add internationalization support with separate JSON files per language. Initial translations: Spanish (Spain) and Portuguese (Portugal). Each file includes names, categories, phases, summaries and appearances for all 119 elements.
Add three new i18n translation files: - en-US.json: American English (Aluminum, Cesium, color) - en-GB.json: British English (Aluminium, Caesium, colour) - es-AR.json: Spanish (Argentina) with rioplatense voice
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR adds
Internationalization (i18n) support for the periodic table data through separate translation files, without modifying any existing files.
Structure
A new
i18n/directory with:README.md— Documentation and contribution guideen-US.json— English (United States)en-GB.json— English (United Kingdom)es-ES.json— Spanish (Spain)es-AR.json— Spanish (Argentina)pt-PT.json— Portuguese (Portugal)Each translation file includes:
All translations are indexed by atomic number and use the original English values as keys for categories, phases, and appearances.
Why separate files?
Language-specific highlights
How to use