Helping Translate WoowTech
WoowTech's user-facing text is localized with Lokalise, a web-based platform for collaborative translation. Rather than one giant glossary, the work is split into four independent translation projects:
- Frontend — the strings you see in the web interface.
- Backend — text contributed by individual integrations and platforms.
- iOS app — the WoowTech Companion build for Apple devices.
- Android app — the WoowTech Companion build for Android devices.
Where to Sign Up
Anyone can jump in via the public team links below — no invitation required:
Even a language that already shows as 100% done still gains from a second pair of eyes — reviewing and proofreading existing entries is genuinely useful work.
How New Translations Reach Users
Each time WoowTech is built, the current translations are pulled in automatically, so every release ships with the most recent strings the community has produced.
Reading the Placeholders
Two bracket styles inside a string carry special meaning, and getting them wrong breaks the UI:
[ ... ](square brackets) — a key reference in Lokalise. Instead of re-typing an identical phrase in many places, one key points at another. Don't translate the contents; the reference resolves to whatever the target key holds.{ ... }(curly braces) — a runtime argument. WoowTech swaps in a live value (a device name, a count, a date) where the placeholder sits. Copy it across verbatim — name, casing, and any embedded plural or select logic — and never localize what's inside.
Ground Rules
- Translate only into a language you speak natively.
- Keep the tone aligned with the Material Design writing guidance.
- Leave brand and product names alone — WoowTech, Supervisor, Hue, and similar proper nouns stay in their original form.
- To seed a regional variant whose wording matches the parent language, duplicate the source string with Ctrl+Insert rather than retyping it.
- Anything that renders inside a
state_badgehas to stay short, or it will spill out of the badge. - When the same wording appears under several keys, wire them together with a Lokalise key reference instead of copy-pasting.
Requesting a Language That Isn't There Yet
If your language is missing, open a request on GitHub and include both its English name and its endonym (the name in the language itself).
A maintainer will then:
- Confirm the language tag conforms to BCP 47.
- Register the tag and native name in
src/translations/translationMetadata.json. - Create the language inside Lokalise, tweaking the ISO code there if it differs from the tag.
Per-Language Conventions
German
- Address the user informally with du, not the polite Sie.
- Take care with imperative (command) verb forms.
French
- Don't translate Blueprint. Keep it as a proper noun, capitalized, so it isn't confused with unrelated terms and stays searchable.
Helping Translate WoowTech
WoowTech's user-facing text is localized with Lokalise, a web-based platform for collaborative translation. Rather than one giant glossary, the work is split into four independent translation projects:
- Frontend — the strings you see in the web interface.
- Backend — text contributed by individual integrations and platforms.
- iOS app — the WoowTech Companion build for Apple devices.
- Android app — the WoowTech Companion build for Android devices.
Where to Sign Up
Anyone can jump in via the public team links below — no invitation required:
Even a language that already shows as 100% done still gains from a second pair of eyes — reviewing and proofreading existing entries is genuinely useful work.
How New Translations Reach Users
Each time WoowTech is built, the current translations are pulled in automatically, so every release ships with the most recent strings the community has produced.
Reading the Placeholders
Two bracket styles inside a string carry special meaning, and getting them wrong breaks the UI:
[ ... ](square brackets) — a key reference in Lokalise. Instead of re-typing an identical phrase in many places, one key points at another. Don't translate the contents; the reference resolves to whatever the target key holds.{ ... }(curly braces) — a runtime argument. WoowTech swaps in a live value (a device name, a count, a date) where the placeholder sits. Copy it across verbatim — name, casing, and any embedded plural or select logic — and never localize what's inside.
Ground Rules
- Translate only into a language you speak natively.
- Keep the tone aligned with the Material Design writing guidance.
- Leave brand and product names alone — WoowTech, Supervisor, Hue, and similar proper nouns stay in their original form.
- To seed a regional variant whose wording matches the parent language, duplicate the source string with Ctrl+Insert rather than retyping it.
- Anything that renders inside a
state_badgehas to stay short, or it will spill out of the badge. - When the same wording appears under several keys, wire them together with a Lokalise key reference instead of copy-pasting.
Requesting a Language That Isn't There Yet
If your language is missing, open a request on GitHub and include both its English name and its endonym (the name in the language itself).
A maintainer will then:
- Confirm the language tag conforms to BCP 47.
- Register the tag and native name in
src/translations/translationMetadata.json. - Create the language inside Lokalise, tweaking the ISO code there if it differs from the tag.
Per-Language Conventions
German
- Address the user informally with du, not the polite Sie.
- Take care with imperative (command) verb forms.
French
- Don't translate Blueprint. Keep it as a proper noun, capitalized, so it isn't confused with unrelated terms and stays searchable.
Start writing here...