Is there already some kind of consensus about tran...

# multiplatform

[Tolriq]

Is there already some kind of consensus about translations sharing in multiplaform apps?

[Vidmantas Kerbelis]

Not really sure about a consensus, but I’ll add a comment from my work experience with an external translation service.

They mentioned that the way most, let’s say noteworthy, translation companies work using out-of-the-box solutions like for example Crowdin (https://crowdin.com/). Now, as we do not have a wide-spread solution for translations, such tools do not support anything specific for KMM. They support native Android, JS, iOS solutions though (And CSV, so technically any solution could work, but you’d have to customize an import/export mechanism). So, ... XML is an option. So, … Moko Resources is an option technically (although there is no consensus on this one)

Now what this means is that for the time being, if there is an intention for an external translation company, you’re somewhat forced to either keep the strings in the platform code, or use XML.

[Tolriq]

Hum ok thanks, currently using Weblate so can relatively easily convert the exports to support both and keep native things for now.

[Arun Joseph]

I have got Moko resources working with kmmbridge and looks sufficient for existing iOS/Android use cases.

[Ashu Tyagi]

Hey @Arun Joseph,

How did you get moko-resources to work with kmmbridge? I'm stuck with the same issue. Thanks in advance.

[Arun Joseph]

It would help if you describe what exact issue is being faced.

build.gradle.kts

[Arun Joseph]

Hi I have the above build.gradle.kts file

[Ashu Tyagi]

Thanks a lot. It helped. It's working now. isStatic flag was missing.