Every label (44 passages, no note) of the generated site (note: Site) goes through a message catalogue per locale (3 passages, no note) in ICU MessageFormat, plurals (6 passages, no note), selections, numbers and dates (44 passages, no note) expressed in the message (22 passages, no note) itself, stored as JSON in the format (16 passages, no note) translation platforms (4 passages, no note) exchange. Message identifiers (note: Identifier) are typed (37 passages, no note) from the source (note: Source) catalogue (12 passages, no note), so that a missing key (46 passages, no note) or variable (5 passages, no note) fails the build (note: Build), and a test checks (note: Check) that every locale (note: Locale) carries every key. Messages are resolved (8 passages, no note) at build: the published HTML contains (3 passages, no note) final strings and no localisation library runs in the browser (31 passages, no note); dates and numbers use the platform formatters. A project overrides any message (3 passages, no note) through the labels of its theme.yaml.
ICU message catalogues
Decision · Acceptedspecs/decisions/publication/icu-message-catalogues
Properties
- Status
- Accepted
- Decided on
2 keys: the status and the date are authoritative.
See the neighbourhood map6 pages6Neighbourhood mapICU message catalogues
Neighbourhood map ICU message catalogues
Distance1 hop
13 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- Entity pageScreenaffects1
- HomeScreenaffects1
- Build pipelineProcessaffects1
- BuildBusiness objectaffects1
- SourceBusiness objectaffects1
- BuildTermaffects1
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.