Hi,
simple and quick question.
Is it somehow possible to download the translation files for translating e.g. in PO or POT format (can actually be any formated format), would be very helpful instead of checking each page and each component etc.
Or to see all possible translations for each.
I think you just choose a wrong approach to build your app to begin with. This can simply be done via an intermediary formula that parses a JSON with all of your various translations 
But yes, it would be great if we could do this natively in the Editor without workarounds.
i do it at the moment half-half-“half”
Like in WeWeb, DB & WeWeb Formula (if)
Makes you kinda confused if you have ~6 languages.
But to have everything in one place is better, so you can just send the files to native speaker and they translate it.
Or give access to the translator, something like that.
@Broberto Could you maybe share a quick outline of the “ideal” approach of building a multli-language frontend in WeWeb? I’d be very curious to read about it.
So far I’ve been using multi-language text properties on my components in combination with the translate() formula inside the component.
However, I’ve already been thinking ahead of time and now worry about: “what if I introduce a new language? wouldn’t I have to go through my entire frontend and add the language + translations to each of these properties?” 
How would you strucutre and store a central translation file?
Thanks in advance!
You could probably bind it to the variable, instead of having a static value there. I see you have a lot of questions going on, maybe you could benefit from a consultation? I do 1:1 consulting, if you might wanna get unstuck on a little more deeper problems. Check out Consult with Broberto – Broberto