Landing page: EN/JA toggle + full Japanese translation#16
Merged
Conversation
The TUI is bilingual (EN/JA); the landing page now is too. - Fixed top-right EN/JA toggle button. The markup stays the EN source of truth; each translatable element carries data-i18n, and the script snapshots EN innerHTML on load and swaps to JA on toggle. Choice persists in localStorage; first visit defaults from navigator.language. - Full JA translations across hero / about / install / features / preview / keybindings / daily-notice / credits / footer (70 keys; EN-JA parity verified). The notice-board preview shows the JA banner + bodies in JA mode. - Brings the keybindings panel up to 0.4.x: adds D Duplicate, u Undo, r Resume (it was still missing them). - JA strings use only punctuation inside the bundled DotGothic16 subset so the text renders in the pixel font rather than a fallback. docs-only (no app/version change). Validated: 70/70 i18n key parity, HTML well-formed, JS passes `node --check`. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…able amber The footer (〜 終 〜 + the no-telemetry line) was ~0.72em and the second line used --amber-faint (#2a1500), nearly invisible. Bumped the footer to 1em / .dim to 0.95em and recolored .dim to --amber-dimmer so it is legible. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bilingual landing page — EN/JA toggle + full Japanese translation
The TUI ships EN/JA, so the landing page should too. This adds a language toggle and a complete Japanese version of every visible string.
How it works
data-i18nkey, and a small script snapshots the ENinnerHTMLon load and swaps to JA on toggle (so toggling back is lossless).localStorage; first-time visitors default fromnavigator.language(JA browsers land on JA).<html lang>updates with the choice.What's translated
Every section — hero tagline/meta, about, install steps, all 14 feature bullets, the keybindings panel, the daily-notice blurb, credits, and footer. 70 keys, EN↔JA parity verified. The notice-board preview also flips to the JA banner (
【週間】更新予定スレ) and JA post bodies in JA mode, matching the real app.Bonus fixes
DDuplicate,uUndo,rResume.Notes
data-i18n↔JA key parity, HTML well-formed (tag balance), and the toggle script passesnode --check. (Couldn't run a real browser here — worth a quick visual click-through of the toggle when it's live.)🤖 Generated with Claude Code