localize

name	localize
description	Add or change a localized string in Fonde UI. l10n is managed manually (no intl, no flutter gen-l10n) — edit the .arb files plus the abstract class and the en/ja implementations by hand. Use when adding, renaming, or editing user-facing strings.

Add / change a localized string

l10n is manual. Do NOT run flutter gen-l10n and do NOT set generate: true in pubspec.yaml. The intl package is not used. See doc/localization.md.

Steps

For each string you add or change, edit these four files in sync:

1. ARB files — lib/l10n/fonde_ui_en.arb and lib/l10n/fonde_ui_ja.arb. Add the key (and its @key metadata where the file uses it) to both.

2. Abstract class — lib/src/core/l10n/fonde_ui_localizations.dart. Add a getter declaration with a doc comment:

   /// <what the string is for>
   String get <key>;
   

3. English impl — lib/src/core/l10n/fonde_ui_localizations_en.dart. Implement the getter returning the English text.

4. Japanese impl — lib/src/core/l10n/fonde_ui_localizations_ja.dart. Implement the getter returning the Japanese text.

Note: the paths above follow doc/localization.md. If lib/l10n/ does not exist, check lib/src/core/l10n/ for the actual .arb location and adjust — keep all four layers (arb × 2, abstract, en, ja) in sync regardless of exact path.

Verify

fvm dart format .
fvm flutter build <target>   # a real build, not just analyze (CLAUDE.md)

Confirm every key exists in both en and ja implementations and in both .arb files — a missing override will fail to compile because the abstract getter is unimplemented.