jthompson4004

6 ms·

1.
by jthompson4004 2y ago
Which translations feel unnatural at the moment so we can check into it? Right now we're still figuring out pricing, so everything is free at the moment in our pilot stage.
2.
by jthompson4004 2y ago
We do have it translated into 13 languages right now, which language is your browser set to so we can add it?
3.
by jthompson4004 2y ago
It should switch to the appropriate language based on your browser settings. If you're in Chrome, make sure that in Settings > Languages, your language is at the top of the list.
4.
by jthompson4004 2y ago
Ahh okay, that makes sense. There are two possible approaches we could take, one would be creating some kind of E2E testing that would detect overflows/things like that, or integrating into existing tests, but that would probably requi
5.
by jthompson4004 2y ago
Yup, we use a very similar library on the backend, we just layer a few things on top of it, like our VSCode extension that scans through the app and auto-wraps user-facing strings for translation, build-time translation, automatic context,
6.
by jthompson4004 2y ago
Yeah, we detect off the browser what locale we should switch into. As for UI tests, we're doing that ad-hoc right now for everybody, but what was your favorite approach to that? I'd love to look into what the best ways people han
7.
by jthompson4004 2y ago
Right now we actually do have React Native support, it is now in our docs! As for adding manual context, we're planning on adding that, but we don't want people to go overboard with adding additional context where it's not ne
8.
Launch HN: Quetzal (YC S24) – Stripe for Internationalization
48 points by jthompson4004 2y ago|37 comments