[Feature Request] Internationalization / Translation (simplified) #382
Description
I'd like to enable a simple translation/Internationalization UX for Kiln.
Currently using tools like Chrome's translate feature don't work well, as they also translate your data (the outputs of LLMs, the saved inputs). This makes it pretty unusable at its core use case -- your data shouldn't be translated in a data analysis tool.
Note: I don't want to support internationalizing the whole app with strings as part of the app at this point. There are too many strings, and things are moving too fast. The team won't be able to maintain key languages. We should make it easy to use with translation extensions for now.
Part 1: Ignore Raw Data [P1] - ✅
We should add translate="no" to our html elements with data (model outputs/inputs, synthetic data). We don't want translation software touching it.
After this we can encourage people to use Chrome's translate feature (or another extension), without breaking core purpose of Kiln
Part 2: Translate Key in App Strings [P2]
Add a translation framework and make a few key translations.
We want to strategically translate a few key items (sidebar labels, important buttons in UI that don't automatically translate well), without trying to translate everything. Leave 99% to the browser extension. At this point, contributors could fix bad translations with small tactical changes (add a data-i18n tag to problematic elements, and add translations for it).
Key concept: this is still optional for any string, and expected to be used with a browser extension. We don't want to slow down new development, but we do want to improve the main UX.