Changelog

• Sep 23, 2026

  🧠 Hypertranslate AI — a second engine

  A new AI translation telephone is live at /ai:

  • Every hop is a prompt to a large language model hosted by Pollinations.AI instead of a Google Translate lookup — the text is re-expressed phrase by phrase, so idioms and tone hold on a little longer before the drift takes over.
  • Four models are available above the form: GPT-5.6 Luna (default), GPT-5.4 Nano, Meta Llama 3.3 70B, and DeepSeek V4 Flash.
  • The whole run travels over one WebSocket connection, and each round streams back token by token — you watch the route land in real time instead of waiting for a final answer.
  • Switch & resume: if a hop fails or the socket drops mid-round, press Continue — finished rounds are kept and only the remaining hops re-run. You can switch models mid-run; your choice is remembered in your browser.
  • Auto-detect source language, live translation route with expand/collapse, per-hop copy, and local history are all on board, alongside share links with one-tap sharing to X, WhatsApp, and Telegram.
  • Full page copy, FAQ, and JSON-LD (WebApplication + FAQPage) ship in all seven locales: English, 简体中文, 繁體中文, العربية, Bahasa Indonesia, Bahasa Melayu, and Português (BR).

  🌐 Language settings

  A new settings page at /languages puts you in charge of the language pool:

  • Toggle any language on or off — disabled languages disappear from the target language picker and no longer appear as random stops in the relay.
  • Search, “only show enabled” filter, and enable/disable all make managing the list quick; at least one language must stay enabled.
  • Source language is unaffected — you can still translate from any language, including disabled ones.
  • Saved in your browser only (localStorage, no account), and the setting applies to both engines: the classic Google version on the homepage and Hypertranslate AI.
  • Available in all seven locales.
• Aug 29, 2026

  🌐 Localized Language Names

  The source and target language dropdowns no longer rely on a static English name table:

  • Option labels are resolved with Intl.DisplayNames in the visitor’s UI language — the same option reads “Japanese” on the English site and 「日语」 on the Chinese site.
  • Google-specific codes (zh-CN, zh-TW, tl) are mapped to their BCP-47 equivalents (zh-Hans, zh-Hant, fil) before lookup.
  • Intl.DisplayNames instances are cached per locale, and codes missing from CLDR fall back to the built-in English names.

  ⏱️ Request Timeouts & Clearer Failure Guidance

  A hung request no longer stalls a relay:

  • Every request now has a hard 10-second timeout (AbortSignal.timeout); timeouts are treated as retryable errors with their own localized message.
  • The Google dictionary endpoint’s retry budget was trimmed from 3 to 2 attempts, bounding the worst-case wait per round.
  • When a provider fails, the status bar now appends a hint: switch the engine and press Continue to resume from the failed round.

  🛡️ MyMemory Error Handling

  MyMemory reports business-level failures (exhausted quota, invalid language pairs) inside an HTTP 200 body via its responseStatus field:

  • Responses are now only accepted when responseStatus is 200.
  • Business failures surface as a localized “Translation service returned an error (HTTP {status})” message; responseDetails is logged for debugging.

  🧭 Route Expansion Fixes

  • The final round’s card expands exactly when the relay finishes — no longer while it is still running.
  • Rounds you manually collapsed stay collapsed.

  📱 Mobile Layout Polish

  • Long status messages wrap with break-words instead of overflowing.
  • Share actions reflow into a grid on small screens with consistent alignment.
  • Tighter padding and type scale across the form, history entries, and route stop cards.

  🗣️ Localization

  • Provider selection, resume, timeout and MyMemory error strings are translated across all seven locales: English, 简体中文, 繁體中文, العربية, Bahasa Indonesia, Bahasa Melayu, and Português (BR).
• Aug 28, 2026

  🔀 Multi-provider Architecture

  Translation is no longer coupled to a single endpoint. A TranslateProvider interface now abstracts each backend, making it easy to add or swap providers without touching the UI layer:

  • Providers are registered in a central map and exposed to the UI through TRANSLATE_PROVIDERS.
  • The user selects a provider from a dropdown in the form; the choice persists in localStorage.
  • If a provider fails mid-route, the user can switch to another provider and resume from the failed round without re-running successful steps.
  • Adding a new provider requires only implementing the TranslateProvider interface and registering it in PROVIDERS + TRANSLATE_PROVIDERS.

  🆕 MyMemory Provider

  A new MyMemory provider is now available alongside Google Translate:

  • Powered by the MyMemory free translation memory API — no API key required and CORS wide open (*).
  • Ideal as a fallback when Google’s free endpoints hit rate limits or region restrictions.
  • Handles the auto source-language case by passing autodetect to the API.
  • Shares the same retry and backoff logic as all providers.

  Note: MyMemory has a per-IP daily character quota (~5 000 chars) and translation quality depends on memory hits; less common language pairs may return untranslated or partially translated text. Microsoft/Bing endpoints (require credentials or lack CORS) and Baidu/DeepL (require keys) cannot be called from the browser and are not included.

  🛡️ Resilient Translation Pipeline

  The shared fetchWithRetry utility now underpins every provider:

  • Exponential backoff with jitter across up to 3 attempts per endpoint.
  • Retryable HTTP status codes: 0 (network), 403, 429, 500, 502, 503, 504.
  • Google’s three endpoint hosts rotate automatically before giving up.
  • Structured TranslateError with machine-readable codes (network_error, api_error, empty_result, unavailable) map to localized UI messages.

  ⏩ Resume-from-Failure

  When a translation round fails:

  • Completed rounds are preserved in the UI.
  • A “Resume” button appears, letting the user switch providers and continue from the exact round that failed.
  • History is only saved on full completion, so partial runs don’t clutter the list.

  🌍 UI and Localization

  • A provider selector dropdown has been added to the translation form.
  • New localized message keys: provider.google, provider.mymemory, status.providerFailed, status.providerSwitched.
  • All six supported locales have been updated with the new strings.
• Aug 23, 2026

  🚀 A New Focus

  Hypertranslate now has a focused product identity across navigation, legal pages, social metadata, and site configuration. Its purpose is simple: send text through a chain of languages and see how its meaning transforms along the way.

  🔁 Google Translate Fun

  The homepage now centers on the full Google Translate Fun workflow:

  • Build a custom route with multiple source, intermediate, and target languages.
  • Run every step in sequence and inspect the translated text at each stop.
  • Expand or collapse route steps for a clearer view of long chains.
  • Copy any intermediate result with one click.
  • Save completed runs to local browser history so you can revisit them later.

  🔗 Shareable Results

  Completed translations can be saved and shared through short links. Shared pages open in a read-only view that preserves the original route and all intermediate text, while still using localized page metadata.

  🛡️ More Reliable Translations

  Translation requests are now more resilient:

  • Multiple API endpoints rotate automatically.
  • Failed requests retry before surfacing an error.
  • Round limits keep long routes predictable.

  🌍 Interface and Content Updates

  • The translation interface uses a dedicated internationalized message system across all six supported locales.
  • Language-switcher path handling is more robust for translated pages.
  • Homepage titles, descriptions, tips, and FAQs have been refreshed.
  • The default font is now Nunito for improved readability.

  📈 Analytics and Metadata Improvements

  Added Google Analytics support where configured, consolidated site constants and metadata generation, and updated Open Graph and Twitter cards to match the new brand.