Bosca / Localization

Export

The format each platform expects

Translations don't have to live in Bosca. Export them in the exact shape your apps read — mobile, web, or a translation tool — with placeholders rewritten to each platform's syntax and only the strings you've marked ready.

Eight formats

One project, every target

The same strings export to whatever your stack needs — no hand-conversion, no glue scripts to maintain.

Androidstrings.xmlwith <plurals>
iOS.stringskey–value
iOS.stringsdictplural forms
Flutter.arbICU preserved
Webi18n JSONNuxt nested
Webflat JSONkey: value
Webnested JSONdot keys expanded
Any toolXLIFF 1.2CAT interop

Placeholders travel

The same variable, each platform's way

You write a placeholder once, in the standard ICU form. On the way out, the exporter rewrites it to the syntax the target expects — so an Android build and an iOS build both get a variable they understand, from the one source.

  • Author once in ICU MessageFormat; export converts it per platform.
  • Plural forms are emitted in each platform's native shape.
  • No per-platform string files to keep in sync by hand.
{count} items
Android%1$s items
iOS%@ items
Flutter{count} items

Only what's ready

Ship the finished, hold the rest

An export isn't all-or-nothing. Choose which workflow states to include — published by default — and half-translated or in-review strings simply stay behind, so a release never ships a draft by accident.

  • Filter an export to the states you want; published is the default.
  • In-progress translations are left out until they're ready.
  • One request returns the file, its type, and a sensible name.
export
formatandroid-xml
includepublished
strings.xml · 214 strings

Keep exploring

More on Localization