Android: 79 localized paragraphs are completed by hardcoded English (whitespace is the symptom) #922

Filed as a whitespace defect. Re-reviewing it found the whitespace is the symptom of something larger, so this is rewritten in place rather than left mis-scoped.

What is actually wrong

94 strings in values/strings.xml end with a trailing space. I assumed they were fragments joined to other localized fragments. They are not. Of the 94:

// AddDeviceWizard.kt:830
Text(
    uiString(R.string.l10n_add_device_wizard_a_whoop_strap_bonds_to_a_d39bdf4a) +
        "to the official WHOOP app, and the other way round. It's reversible: pair it in the " +
        "other app whenever you want it back.",

A French user reads:

Un bracelet WHOOP se lie à un seul appareil. Alors qu'il est connecté à NOOP il ne va pas diffuser to the official WHOOP app, and the other way round. It's reversible: pair it in the other app whenever you want it back.

Half the paragraph is translated and half is English, in 79 places, in every non-English locale. The missing trailing space is a cosmetic detail on top of that.

Why nothing catches it

The trailing literals are real hardcoded UI copy, and i18n_audit.py does find them — they are part of the 229 it reports and sit in Tools/i18n_audit_baseline.json, so the gate is green. The baseline was the right call for a backlog, but it means these particular 79 read as "known, tolerated" when their user-visible effect is a half-English paragraph, not an untranslated label.

Revised fix

The whitespace patch alone would only add a space before the English — polishing the seam. The real fix, per paragraph:

1. extract the trailing literal(s) into values/strings.xml with the existing key convention;
2. compose from localized parts (or better, use a single string with placeholders so translators see whole sentences);
3. drop the now-pointless trailing space from the leading fragment;
4. remove those entries from the audit baseline, ratcheting it down as Tools/doc_comment_lint_baseline.txt requires of its own.

That is 79 paragraphs across ~20 screens plus translations into five locales, so it wants splitting by screen rather than one sweep.

Still true from the original report

pt-rPT carries the trailing space on all 94 and the machine-translated locales dropped every one (de/es/zh: 94 missing, fr: 77 after #921). If the composition survives in any form, a trailing-whitespace parity test against the default catalogue is worth having — but it is now the smaller half of this issue.