Dariusz Koryto
80dadb3194
* feat(editor): add setting to turn off spellcheck underlines Add a device-local "Underline spelling mistakes" switch to the editing preferences. The rich-text editor and the mobile plain-text editor now set spellcheck from this preference and update live when it changes. Defaults to enabled, so existing behavior is unchanged. Refs #468 * feat(i18n): add Polish as an in-app locale Add Polish (pl) across clients, mirroring how Japanese was added: - Shared: full pl catalog, locale matching for pl/pl-*, Polish memo templates and factory AI prompts, mobile editor strings, and Polish as an AI translation target and selection-translate chip. - Web: "Polski" in the language picker; the catalog is lazy-loaded in its own i18n-pl chunk and kept out of the PWA precache like ja. - Android: pl locale option, mobile-only strings, web-clip labels. Messages that only had an English branch now use English for every non-Chinese locale, so Japanese no longer falls back to Chinese there. - iOS: .polish UI language (pl-PL), pl argument for every t() call, pl in CFBundleLocalizations and Localizable.xcstrings. - Companion: accepts locale "pl" and detects Polish requests. - Browser extension: _locales/pl messages. - Marketing site: /pl/ pages, hreflang, sitemap, language switcher. - Google Play listing copy for pl-PL (manual publish only). * fix(ios): show the note editor in Polish and Japanese The iOS editor received every interface language except English as Chinese, so with Polish or Japanese selected its toolbar and image gallery controls were labeled in Chinese. Pass Polish and Japanese through to the embedded editor, label its toolbar and the shared image gallery controls in both languages, and rebuild the checked-in EditorBundle. The Android editor uses the same gallery labels. Also translate the last iOS strings that had no Polish text: the follow-system language label, note created/updated times and the current-device marker. Refs #473 * fix(companion): recognize Polish typed without diacritics Requests in Latin letters without Polish diacritics were always treated as English, so with a Polish interface "Napisz plan na jutro" got an English reply. With a Polish interface, such text is now told apart by common English and Polish words; when it is still unclear, the recent conversation and then the interface language decide. Other interface languages keep treating Latin text as English. Refs #473 * chore(ios): regenerate the Xcode project for Polish Run xcodegen so the shipped Info.plist lists Polish in CFBundleLocalizations and the project knows the pl region. The hand-written AiDirectStream.swift entries are replaced by the IDs xcodegen generates. MARKETING_VERSION and CURRENT_PROJECT_VERSION stay in the project file because the release script and Xcode Cloud update them there. Refs #473 * i18n(pl): translate the sidebar shortcut, desktop menus and video scope Add Polish for features that reached main while this branch was open: the show/hide sidebar shortcut label, the desktop application and editing context menus, and the new "ai:generate" MCP scope. The desktop menus switch to Polish for pl and pl-* locales; other locales are unchanged. Refs #473
Mobile store assets
This directory contains the current EdgeEver store listing artwork, screenshots, and metadata.
Listing copy is pasted in App Store Connect and Play Console. It is not uploaded
by bun run publish:stores. That command only delivers store binaries; adding
an incomplete Japanese locale there would block App Review.
The root-level artwork is used by Google Play:
feature-graphic.png: 1024 × 500 feature graphic.phone-*.jpg: source mobile screenshots captured from the public demo workspace.phone-*-1080x1920.jpg: Play-ready portrait screenshots used for phone and tablet listing slots.
The app-store/ directory contains the App Store metadata source of truth and
Apple-ready iPhone screenshots. Keep English, Simplified Chinese, and Japanese
metadata files aligned when changing listing content.
The play/ directory contains Google Play listing copy for English, Simplified
Chinese, Japanese, and Polish.
Publish a Japanese listing
Japanese in-app UI is not required. Japanese users currently see English chrome. Reuse the existing screenshots.
App Store Connect
- Open the EdgeEver app → App Information.
- Add the Japanese (
ja) localization if it is missing. - Paste
app-store/metadata.ja.mdinto name, subtitle, promotional text, description, keywords, URLs, and the current version's What's New. - Save. Do not attach this locale to a binary review until those fields are complete.
Google Play Console
Play may already show Japanese from an earlier translation. Replace it with the copy in this repository.
- Open Grow → Store presence → Main store listing → Manage translations.
- Add Japanese (Japan) if it is missing.
- Paste
play/metadata.ja-JP.mdinto title, short description, and full description. - Publish the store listing. This does not upload a new AAB.
Publish a Polish Google Play listing
The Android app ships a Polish in-app UI. Reuse the existing screenshots.
- Open Grow → Store presence → Main store listing → Manage translations.
- Add Polish (Poland) if it is missing.
- Paste
play/metadata.pl-PL.mdinto title, short description, and full description. - Publish the store listing. This does not upload a new AAB.