hsr-optimizer
hsr-optimizer copied to clipboard
[Feature] Enable i18n/l10n Support
Current statically defined labels, strings, char/relic/LC, etc. are hard-coded en-US.
To enable international support, refactor app, DB, components, etc. to support locale-based display.
These changes may necessitate a UI/UX pass as non-latin languages will take less/more horizontal space in tables, cards, etc.
I voted for this. Hopefully I'll be able to contribute something, but I'm worried that I might be messing things up. Pure JavaScript is a little scary for me.