Make UI language, timestamps and live feedback consistent
This commit is contained in:
@@ -71,3 +71,39 @@ Use the shared `--text-*` scale, with 12 px as the minimum. Mobile inputs use
|
||||
in `npm run check`, rejects raw pixel font sizes. Use Inter with tabular figures
|
||||
for counts, scores, durations and charts; reserve mono for code, IDs, paths and
|
||||
logs. Static values use text or state colors; the accent marks links and controls.
|
||||
|
||||
### Product language
|
||||
|
||||
| Concept | Visible label |
|
||||
| --- | --- |
|
||||
| A managed game instance | Server; use the friendly map and lobby name |
|
||||
| Creating a server | Create server |
|
||||
| Removing a server | Remove server |
|
||||
| Favourite server | Pin |
|
||||
| Game does not answer | Not responding |
|
||||
| Games | Black Ops I / Black Ops II; BO1 / BO2 in compact labels |
|
||||
| Releasing file changes | Campaigns |
|
||||
| Player completion evidence | Present in final report / Not present in final report |
|
||||
|
||||
Keep internal values such as `t5`, `t6`, `destroy`, instance IDs, and filenames in
|
||||
API fields and technical details. User-facing actions use the labels above.
|
||||
Player presence in the final report does not establish a win or continuous
|
||||
survival. A missing timestamp is **Not recorded**, not **Never**.
|
||||
|
||||
Use `RelativeTime` for observed history: seconds, minutes or hours for the last
|
||||
24 hours, Yesterday for the preceding calendar day, then the shared absolute
|
||||
format. It includes the full timestamp in a tooltip and follows the account's
|
||||
timezone. Scheduled future actions use `timeFormat.dateTime` directly. Database
|
||||
timestamps without an offset are UTC; never parse them as browser-local time.
|
||||
Receipt freshness uses the browser clock and shows Paused or a retry reason
|
||||
when updates are unavailable. These clocks are not live regions.
|
||||
|
||||
Use `plural` or `countLabel` from `src/lib/ui/plural.ts` for count-dependent
|
||||
language, including verbs: `plural(count, 'needs', 'need')`. The helper uses
|
||||
`Intl.PluralRules`; supply irregular plural forms explicitly. Keep separators
|
||||
inside string expressions when a Svelte conditional would trim their leading
|
||||
space, for example `{offline ? ' · Offline' : ''}`.
|
||||
|
||||
Recommend an agent upgrade only when its reported version is known to lack a
|
||||
needed capability. Missing calibration samples can simply mean the host is
|
||||
still collecting measurements.
|
||||
|
||||
Reference in New Issue
Block a user