Skip to content

Localize missing Appearance settings strings#5

Closed
digitalerdude wants to merge 2 commits into
mainfrom
claude/determined-pare-bf17fb
Closed

Localize missing Appearance settings strings#5
digitalerdude wants to merge 2 commits into
mainfrom
claude/determined-pare-bf17fb

Conversation

@digitalerdude

Copy link
Copy Markdown
Owner

What this PR does

Four strings under Settings → Appearance ("Sky behind cards" and its
caption, "Card transparency" and its caption) were added to
SettingsView.swift's appearanceCard but never made it into
Strand/Resources/Localizable.xcstrings, so every non-English locale fell
back to the raw English source text instead of showing a translation.

Adds de, es, fr, it, pt-PT, zh-Hans, and zh-Hant entries for
all four strings, reusing existing catalog terminology (e.g. "Frecuencia
cardíaca"/"心率" for Heart Rate, "Fondo según el ciclo del día" for the
day-cycle background) so they read consistently with neighboring rows.

Note: pt-PT entries in this catalog are marked needs_review throughout
(existing entries mix in Spanish words), and the four new ones follow that
same convention — worth a native pt-PT pass over the whole file at some
point.

Type of change

  • Bug fix
  • New feature
  • Refactor / cleanup
  • Documentation
  • CI / tooling

(Closest fit is "Documentation" — this is a string-catalog-only content
change, no code paths touched.)

How it was tested

Data-only change to Localizable.xcstrings. Verified the file is valid
JSON and that all four keys now carry complete localization sets via a
Python script; no Swift/Kotlin code was touched so no build or test suite
applies.

Checklist

  • Swift package tests pass for any package I touched (swift test in Packages/<name>) — N/A, no package touched
  • Android unit tests pass if I touched android/ — N/A, not touched
  • No new build warnings introduced
  • UI changes use only StrandDesign tokens — no hardcoded colors, fonts, or spacing — N/A, no UI code changed
  • No hardcoded hex frame bytes; protocol facts live in the schema / decoders — N/A
  • Follows the conventions in docs/CONTRIBUTING.md
  • I did not commit generated output (Strand.xcodeproj/) or any secrets/keystores

Related issues

None

digitalerdude and others added 2 commits July 9, 2026 12:35
…ency)

These four strings were added to SettingsView.swift's appearanceCard but
never made it into the string catalog, so every locale fell back to the
English source text. Adds de/es/fr/it/pt-PT/zh-Hans/zh-Hant translations.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
fitnessReadyLead() returns an already-localized String (via
String(localized:)), but ReadinessChecklistCard.lead was typed
LocalizedStringKey?, which SwiftUI treats as a lookup key rather than
literal text. Retype to String? — Text(_:) accepts both, and this is
the correct type for pre-resolved copy.

Pre-existing break from commit 75a096a (PR ryanbr#81), unrelated to this
branch's localization change; fixing here so PR #5's CI build passes.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@digitalerdude

Copy link
Copy Markdown
Owner Author

Superseded by ryanbr#152 against upstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant