Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I18N Support #120

Open
garlandcrow opened this issue Apr 5, 2024 · 1 comment
Open

I18N Support #120

garlandcrow opened this issue Apr 5, 2024 · 1 comment

Comments

@garlandcrow
Copy link

Just curious if there is any ideas for how to support this now or in the future. Maybe we do something like how "live" is injected as a common prop to all components? We could inject a KV map that we populate from gettext, and then use that for the translations? Of course if a project 100% is svelte only then there are JS solutions for this but if we mix and match liveview and livesvelte, best way would be to reuse the same thing. Any other ideas one a first go at this?

@woutdp
Copy link
Owner

woutdp commented Apr 5, 2024

Hmm interesting I haven't thought about I18N support. Not sure if it's the correct thing to support too. If we go with this it should be a more generalizable solution that is not specific to I18N.

Something like a default prop that you don't have to pass explicitely, but define in one location, and is always available. A solution like that makes the most sense to me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants