Refactor Internationalization #2906
Conversation
…gs w TranslateSheet.create
| import ko from "./ko" | ||
|
|
||
| const resources: Resource = { | ||
| en: { language: "isPrimary" }, |
There was a problem hiding this comment.
primary language is read directly from TranslateSheet.create objects. Need to have "en" listed in resources or else i18n doesnt pick up the primaryLanguage as a language option
| demoIcon: { | ||
| description: | ||
| "Un componente para dibujar un ícono pre-definido. Si se proporciona el atributo `onPress`, se rodea por un componente <TouchableOpacity />. De lo contrario, se rodea por un componente <View />.", | ||
| useCase: { | ||
| icons: { |
There was a problem hiding this comment.
all of the content from the demo files live in its respective main language file
|
Whew, @branaust, this is a tremendous amount of work -- thanks so much! I like a lot of what I see. One thing though -- we (generally) can't merge new patterns into Ignite until we've shipped at least an app or two using this methodology and can solidly stand behind it. But this work isn't wasted, at all. It gives us a great reference point to do so, when the time is right. Would you be interested in taking this and turning it into an Ignite Cookbook recipe? By the way, the conflicts look tiny, at least as of now. |
|
@jamonholmgren firstly thanks for giving this a glance. Opening a massive pr on such a critically acclaimed repository is incredibly intimidating (which is mostly why it's remained in draft), but it was such a great opportunity to see what TranslateSheet could look like in a large codebase. During my integration into Ingite, I did actually run into a couple of limitations which led me to make some updates to the library itself and I can now say that TranslateSheet is 100% compatible with the boilerplate! I did not intend for this to get merged in right away, but more-so to use this as an opportunity to share what this library can offer and get some eyes from some of the best in the business to share their opinion. I will absolutely add this as a recipe to the ignite cookbook. Thank you to the infinite red team for all of your contributions to react-native and its community and God bless! |
|
this is free ? I see a "billing" section on translationsheet dashboard |
@ahmedrowaih the TranslateSheet API is and always will be free! The translation service/dashboard/hosting is free while in beta 😁 for the next few weeks you can use the translation API to translate your app in over 200+ languages |
|
well, it looks aowesome ABC, I added a PR x'D
|
|
@jamonholmgren I've moved this PR to the TranslateSheet org, opened up a PR to add this as a community recipe in the ignite cookbook recipes repo and have referenced the ignite + TranslateSheet repo in that recipe |
Description
This PR reshapes the way we think about internationalization in ignite by introducing a new tool called TranslateSheet
What is TranslateSheet?
Built on top of the trusted i18next library, TranslateSheet combines developer-first workflows with powerful features, making localization easy for both new and existing apps
Inline Translation Definitions
Define your app's translations directly in your components with a simple API. No more juggling massive external files during development – keep your translations organized and scoped by component or feature.
Hot reloading support
One major issue with i18next is that it takes away the ability to quickly make a text change or add a new piece of text without completely restarting your app. TranslateSheet serves as a proxy on top of i18next, and for the first time gives you the optimal desired DX with the combination of both localization and hot-reloading support.
Full TypeScript Support
Another pain point that comes with using i18next is type safety. The ignite boilerplate has done a great job filling the gaps by providing its own in-house type safety on all of its custom components with props such as
txandtxOptions. With TranslateSheet, type safety comes baked in. There is no need for separate props on the components to define a translated string and the translated string options.AI Translation
For teams that want to serve their apps to users in other countries as fast as possible, quickly translate your app in over 200+ languages with a single command
translate-sheet generate.Translation CRM
For teams that already have translation files (i.e. ignite boilerplate) and want to adopt the TranslateSheet CRM, push up all of your translation files with a single command
translate-sheet push. Within seconds, your app's translations are accessible in a user-friendly interface making it incredibly easy to manage your app's text and hire professional translators to validate your text strings or add additional languages. You can provide context to your text strings via image or recording. Once approved, auto-open a PR (or merge to main) with your latest changes or manually pull them locally with the commandtranslate-sheet pullIgnite demo w/ TranslateSheet
Check out the demo for my 2025 App.js Conference Application
TranslateSheet Documentation