Skip to content
This repository was archived by the owner on Feb 24, 2024. It is now read-only.

change(i18n): use JSON dictionary files for better compatibility with tooling - #289

Draft
eddieantonio wants to merge 7 commits into
locale/spanishfrom
refactor/locales
Draft

eddieantonio wants to merge 7 commits into
locale/spanishfrom
refactor/locales

Conversation

@eddieantonio

@eddieantonio eddieantonio commented Apr 3, 2021

Copy link
Copy Markdown
Owner

In a perfect world, I'd want the dictionary files to be in TypeScript, tooling like i18n-ally is way too cool to pass up! It only works with JSON and YAML however :/

So I converted the translations to JSON . I may tinker around with the commits here to get the attribution right/make it work right. I might even start again, but based off the production branch rather than the locales/spanish branch.

@vercel

vercel Bot commented Apr 3, 2021

Copy link
Copy Markdown

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/eddieantonio/predictive-text-studio/5xRAXPb4ZQ4xGTU4zH6bgqLdLJqL
✅ Preview: https://predictive-text-studio-git-refactor-locales-eddieantonio.vercel.app

@eddieantonio eddieantonio changed the title change(i18n change(i18n): use JSON dictionary files for better compatibility with tooling Apr 3, 2021
@eddieantonio
eddieantonio changed the base branch from production to locale/spanish April 3, 2021 19:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant