[droplister]

Keep transaction amounts intact while localizing the site. Invalid drafts such as -5, 1e5, or 0,5 remain visible and block quotes or compose instead of becoming a different valid amount. Amount, fee, and slippage controls validate their complete draft; generated Max values and compose quantities use canonical digits, a decimal point where supported, and the asset’s verified precision.

Language, number format, and fiat currency are separate saved preferences. Number formatting follows the interface language by default and supports an independent override. Currency Auto uses browser regional preferences; an explicit choice, including USD, survives language changes. Presentation changes do not reinterpret transaction values. Current fiat estimates use the selected currency with dated rate context; historical values retain their USD basis.

Use the local Rewards label without XCP in non-English navigation and page titles; currencies remain identified beside amounts. Finish the localized navigation, canonical/hreflang metadata, translation coverage, and source-context review. Correct transaction, expiry, refund, LP-token, and funding explanations against the actual components and Counterparty semantics, with primary crypto terminology references. AI-reviewed translations retain machine provenance; this does not claim native-speaker approval. Language switching navigates to another URL and currently clears unsaved form drafts.

Validation:

• 682 tests pass, including sequential input/compose boundaries, preference independence, routes, and translation interpolation.
• Web/API TypeScript, lint, numeric discipline, all ten 1,237-key catalogs, GitHub CI, and the production OpenNext build pass.
• 66 actual Chromium settings cases cover all 11 interface languages at 360px and 1280px; draft errors fit within two lines. Page checks cover home, minting/trading, Activity, Stats, Rewards, Docs, FAQ, Create, Dispense, Swap and Limit; the observed mobile Docs overflow was corrected and rechecked: actual source-context and responsive checks supplement catalog completeness checks; they are not a native-language certification.

The immutable SDK pin 79f190308d4b60cc3ec9023beada21e0ee776213 already passes its CI and builds; a new SDK release is unnecessary. The API tree matches merged PR24, so this localization release needs only the web deployment.