Reaching another market takes more than translated strings. A product that is ready for the world keeps its text in catalogues, formats numbers, dates and money for each reader, sorts the way the reader's language sorts, and never assembles a sentence from fragments. It mirrors for right-to-left languages and leaves room for text that grows in translation. Coroid follows Microsoft's international design checklist for all of this.
Globalisation in the main menu has two parts:
| Part | What it is for |
|---|---|
| Internationalisation | Code ready for any language and culture: the wizard, World readiness and Culture |
| Localisation | Every language, string by string: the workbench |
Globalisation opens on Localisation. Each project's workbench groups its sections the same way: World readiness and Culture under Internationalisation, and the translation sections under Localisation.
From one language to many
- Internationalise. The Internationalisation wizard sets up catalogues, languages, style and each market's money in one pull request.
- Clean up the code you have. World readiness lists what the code on your default branch still assumes about one language or one culture, and files small tasks to fix it.
- Follow each market. Culture shows what each market expects of dates, numbers, money, addresses, phone numbers and names, and which formatter the code uses for them.
- Translate. The Localisation workbench shows where every language stands and translates what is missing.
- Keep it that way. The Globalisation check reads every change: its strings, the code it adds, and, when you set it up, its pages rendered with a pseudo translation.
Design for every market explains what each market expects of the code, with the check's codes for each habit that gets it wrong.
Internationalisation
The Internationalisation part lists the projects you can read. A line at the top says how many are internationalised and how much the checks found in their existing code.
Each internationalised project's row shows what Coroid found on its default branch: text written into the code, assembled sentences, and everything else. It also shows the change since the last check. Coroid reads the code without running it. Opening a row opens the project's World readiness.
A project without translations says Not internationalised yet. Owners and admins start the wizard from that row, or from Internationalise a project at the top of the page.
Localisation
The Localisation part lists every internationalised project with its source language, its languages, its strings, and one bar for how much is translated. The small globe beside each project carries one bead per language: green when the language is complete, a teal ring when strings are missing or changed, and amber when some strings are broken.
Ready every project for every market: code that works in any language and culture, then its translations.
2 projects · 6 languages · 135 strings waiting
- StorefrontEnglish source · 5 languages · 1,240 strings97.2%135 strings waiting
- Help centreSwedish source · 2 languages · 318 strings100%Every language complete
1 more project is not internationalised yet.
Globalisation → Localisation: each internationalised project's languages as beads round a small globe, with how much is translated and what still needs work. Illustrative data.
Opening a project opens its workbench.
Who does what
Everyone who can read a project sees its Globalisation pages. Owners and admins run the wizard, create fix tasks, translate, edit strings and change settings. Which findings of the Globalisation check send a change back is set in Quality Control.