fix(l10n): repair corrupted duration abbreviations in ar/bn/hi/ja/ru/zh ARB files
Build & Deploy PluriWave / Análisis de código (push) Successful in 25s
Build & Deploy PluriWave / Build APK + AAB release (push) Successful in 2m24s

Sleep-timer duration strings (durationHoursMinutesSeconds, durationMinutesSeconds,
durationMinutesOnly, durationSecondsOnly) contained literal "?" characters instead
of the native hour/minute/second abbreviation in 6 locales. Replaced with correct
native short-form units per locale, verified byte-exact against a pinned spec table
and against the already-correct neighboring hoursLabel/minutesLabel/secondsLabel
values in each file.
This commit is contained in:
Javier Bautista Fernández
2026-07-21 09:56:18 +02:00
parent 12967e9894
commit fb7fe8774b
15 changed files with 517 additions and 24 deletions
@@ -0,0 +1,19 @@
# Apply Progress: i18n-locale-audit
Status: complete (all 13 tasks done, 1 batch)
## Phase 1: Content Repair — done
All 24 exact-string line replacements applied across the 6 locale files (`app_ar.arb`, `app_bn.arb`, `app_hi.arb`, `app_ja.arb`, `app_ru.arb`, `app_zh.arb`), lines 19/27/34/40 each, matching the pinned spec table byte-exactly. No JSON re-serialization; surgical single-line `Edit` calls only.
## Phase 2: Static Validation — done
- 2.1 JSON parse: all 6 files parse successfully.
- 2.2 UTF-8 strict decode: no `` replacement characters.
- 2.3 Diff scope: `git diff --stat` shows exactly 24 insertions / 24 deletions across the 6 files (8 changed lines each); per-file hunk headers confirm only lines 19/27/34/40 touched.
- 2.4 Zero literal `?` in the 24 target values.
- 2.5 Placeholder integrity: extracted `{...}` tokens match expected `{hours}`/`{minutes}`/`{seconds}` set/order per key; `@durationXxx.placeholders` metadata blocks unchanged (implicit — not part of the diff).
- 2.6 Byte-exact match: all 24 values equal their pinned spec-table cell.
- 2.7 `git diff --check`: exit 0, no whitespace/EOL damage.
## Notes
- Did not run `flutter build`, `flutter gen-l10n`, `dart analyze`, or `flutter analyze` per instructions (they hang in this environment).
- Validation performed with `python` (not `python3`, which is unavailable on this Windows/git-bash environment; `python` resolves to `/c/Python/Python312/python`).
- No files other than the 6 target ARB files were touched.