Hey guys, so whats the proper/recommended way to h...

# compose-web

[Moe]

Hey guys, so whats the proper/recommended way to handle localization ?

[Rok Oblak]

I ended up defining my own string-holder data classes which are provided via a composition local. I can define simple strings and also functions (to format arguments in a string).

I preferred this over string resources for different reasons; mostly just because they were cumbersome to work with.

it works for now, and I just let chatgpt translate when I need a new language. But not the best when there are lots of client-requested changes to random strings all over the place.

Improvements I'd want:
• have a simple visual editor in a table to see all translations per file
• have this be accessible and managable outside of the repo, to other non-dev people
Something like a google docs spreadsheet where my client can go in under a sheet, i.e. cta, and add a new row PayNow and fill out the english translation, and then chatgpt can automatically follow-up for the other columns.

Then my gradle script would fetch the sheet and generate the files and accessor code and I could just refer to it as GenStrings.cta.PayNow for example.
May do it a bit later this year of nobody else does first 🙂