Aipogeo Context Translate

Changelog

2.1.1

• Fixed the DeepSeek privacy policy link under External Services: the address it
  used had been retired and answered with a 404. Both DeepSeek links now point
  at the current documents.
• The subscription panel on Translation Settings loads its script from a proper
  enqueued file instead of markup printed into the page, so the script honours
  the usual dependency and caching rules.
• Option and transient names built at runtime now spell the plugin prefix out in
  full at the point of use, which makes it plain that nothing this plugin writes
  can collide with another plugin’s data.

2.1.0

• Translations bought through the Aipogeo subscription are now carried out by
  the service itself: the plugin sends the text, the service calls the AI
  provider with its own credentials and sends the translation back. No AI
  platform key is kept on your site for this route, and there is nothing to
  configure beyond the access key.
• Subscription usage is counted and shown in tokens, the same unit the service
  bills in, so what the settings screen reports matches your account.

2.0.1

• The two default translation prompts are now written in English instead of
  Chinese, so the plugin is usable out of the box whatever language your site is
  in. A prompt you have edited yourself is left alone; to pick the new default
  up, clear the prompt box and save, or press Reset to default.

2.0.0

• Renamed the plugin to Aipogeo Context Translate. The text domain, option names
  and database tables moved with it, so settings and translations saved by an
  earlier version are not carried over.
• The subscription screens are now in English like the rest of the plugin, so
  they can be translated on translate.wordpress.org along with everything else.
• The readme now documents every external service the plugin can contact, what
  is sent to each and when.

1.2.0

• New: translations can be requested through an Aipogeo subscription. Enter one
  access key and the site is ready to translate — no AI platform account, no
  top-ups, no model to pick. Activating, checking the subscription and
  unbinding the site are all on the settings screen, and there is a one-click
  connect that fetches the key for you. The two existing routes — your own API
  key, or the site-wide AI configuration of WordPress 7.0 — are untouched.
• The AI service section now shows only the settings that belong to the option
  you picked under “Where translations are requested”. The subscription key on
  its own for the subscription service; nothing to fill in for the site-wide
  configuration; the model, endpoint and API key only when you bring your own
  AI account. Fewer unrelated fields to read past on a first run.
• Fixed: the subscription option only appeared on WordPress 7.0 and later, so
  sites on 6.x could not choose it at all. It is always available now, and on
  6.x — where there is no site-wide AI configuration — the choice is between
  the subscription service and your own AI account.

1.1.3

• The language switcher no longer loses its layout to the theme around it. Its
  styles are now anchored to the switcher’s own id, so a theme rule such as
  .some-menu a { display: block } can no longer flatten the entries, and the
  flag and language name in every row start on the same line as the one on the
  button. Rows also set their own text alignment instead of inheriting the
  theme’s, which on a right-aligned menu left every row starting somewhere
  different. Custom styling still works — target the same id.

1.1.2

• The language switcher’s dropdown now lines up with the left edge of the
  button, so the language shown on the button and the entries below it sit in
  one column. It still flips to the right edge when the menu would not fit
  there, which is what happens in its default spot in the top right corner.
• When the switcher is placed inside a theme container, its menu is positioned
  against the switcher itself rather than whatever ancestor happened to be
  positioned, so it lands where it should and keeps its stacking order.

1.1.1

• The language switcher’s dropdown is now as wide as its longest entry instead
  of being squeezed to the width of the button, which left language names behind
  a horizontal scrollbar. It still never gets narrower than the button, stops
  growing at 280px, and trims anything longer with an ellipsis.
• The same goes for the language dropdown on the settings and language screens:
  it opens as wide as the longest language name, up to 480px, rather than being
  held to the width of the field. Its search box stays in place while the list
  scrolls.
• Both lists reserve room for their scrollbar, so a list long enough to scroll
  no longer has its content pushed sideways into a second scrollbar.

1.1.0

• WordPress 6.7 and later is enough again; 7.0 is no longer required. On 6.9 and
  later, page output is still handed to the output buffer WordPress opens for
  template enhancements; on earlier versions the plugin opens one of its own and
  closes it in the same request, so translated pages are served either way.
• The choice of where translation requests are sent only appears on WordPress
  7.0 and later, which is where a site-wide AI provider can be configured. On
  earlier versions that row explains the situation instead, and requests go to
  the plugin’s own AI service settings.
• A site saved with “this site’s AI settings only” and later moved to WordPress
  6.x falls back to the plugin’s own AI service settings rather than failing
  every translation.

1.0.0

• Renamed the plugin to Aipogeo Context Translate. The option names,
  database tables and text domain moved with it, so translations and settings
  saved by an earlier version are not carried over.
• Translations can now be requested through the AI provider configured for the
  whole site in WordPress 7.0, so you no longer have to enter a second API key
  here. The plugin’s own model, key, gateway and relay settings are still there
  for anything the site-wide configuration does not cover, and a new option on
  the settings screen decides which of the two is used.
• Page output is handed to the output buffer WordPress opens for template
  enhancements instead of one the plugin opened itself, and the robots.txt
  buffer is now closed in the same request step that opens it. Both changes keep
  the buffer stack aligned with other plugins.
• WordPress 7.0 is now the minimum, for the site-wide AI configuration and the
  template enhancement output buffer.
• Prompts, translations and replacement rules submitted from the admin screens
  are sanitized before they are stored, and every value inside a submitted JSON
  payload is checked individually rather than trusted after decoding.
• The admin menu icon style is enqueued rather than printed inline.
• Translation files are no longer shipped with the plugin; translations come
  from translate.wordpress.org once the plugin is published there.

0.6.1

• Elements marked as not to be translated now get a little breathing room: 4px of
  padding on the left and right. Languages such as Chinese and Japanese are
  written without spaces between words, so a brand name or model number wrapped
  in not-translate tends to sit flush against the text around it — and once the
  AI has reordered the sentence, it reads as one run-on word. The padding applies
  to class="not-translate", class="notranslate", translate="no" and
  translate=”0″, and only when the class attribute is exactly that marker, so
  elements of your own that merely carry the marker alongside other classes keep
  their layout untouched.

0.6.0

• Translate all now runs five pages at a time instead of one after another, which
  cuts the wall-clock time of a full run by roughly the same factor. A slot frees
  up the moment a page finishes, and the next language’s list is fetched while the
  last pages of the current one are still being translated, so the slots never sit
  idle between languages.
• The progress area lists every page currently being translated, each with its own
  language and elapsed time.
• Stop still lets the pages already sent finish, it just does not start new ones.
• Worth knowing: with several pages in flight at once, text they share — menus,
  footers, cookie notices — can be sent to the AI more than once during the first
  run, because none of them is stored yet when the batch starts. Later runs cost
  nothing extra for those, and each page still holds its own lock, so no page is
  ever translated twice at the same time.

0.5.1

• Fixed translated pages coming out with scrambled markup on sites whose theme
  or page builder keeps an HTML template inside a <script type="text/html">
  block — video lightboxes, carousels and similar components are usually built
  this way. PHP’s HTML parser treats the first closing tag inside such a block
  as the end of the script, so the rest of the template leaked into the page,
  elements closed in the wrong order and stray closing tags were dropped. The
  contents of script and style are now kept out of the parser’s way and put
  back untouched, byte for byte.
• As a side effect, text belonging to those templates is no longer picked up as
  translatable content.

0.5.0

• Translate all no longer stops at the language picked in the toolbar. It starts
  with that language and then works through the pending pages of every other
  target language on its own, so a site with several languages can be filled in
  one run instead of one round per language.
• The progress line now names the language currently being translated, and its
  counters cover all target languages together.
• Each language’s page list is fetched when its turn comes, so pages translated
  in the meantime by the background worker are not translated again.

0.4.1

• Fixed the language menu being hidden behind other page elements on some
  themes. The menu now carries its own stacking order, so it stays on top even
  when the switcher is docked into a theme container instead of floating.

0.4.0

• A page is now sent to the AI in one request whenever it fits. Batches used to
  be capped at 6,000 characters and 50 items, which split an ordinary page into
  seven or eight requests — most of them nowhere near the character limit,
  because menu items, buttons and alt texts are only a few words each. The item
  cap is now 1,000, and the character cap follows the model instead of a fixed
  number.
• Max output tokens now decides how much of a page goes into one request. It is
  converted to characters (about 1.6 per token for Chinese, Japanese and Korean,
  4 for languages written in the Latin alphabet) and never drops below 65,535
  characters. Left at 0 — the default — the plugin reckons with 65,536 tokens,
  which is where single-reply limits sit these days, so an ordinary page goes
  out in a single request. Note that this is about how much a model can write
  back in one reply, not about its context window: a million-token context says
  how much it can read.
• Fewer requests also means the instruction is sent once per page instead of
  once per batch, and the AI sees the whole page at once, which is what the
  context-aware translation is about in the first place.

0.3.1

• Fixed pages coming back as 404 on sites whose rewrite rules or security layer
  reject unknown query parameters. Pages used to be fetched with ?apgt_src=1
  appended; the address is now requested exactly as it is, and the marker that
  tells the front end not to substitute translations travels in the
  X-APGT-Source request header instead. apgt_src still works if you add it
  by hand to look at an untranslated page.
• Source pages are now fetched with Cache-Control: no-cache, so a caching
  plugin cannot hand back a stale copy of the page being translated.

0.3.0

• Translate Pages: when the source page cannot be fetched, the response now
  carries the details of the request that failed — the address that was actually
  requested, the IP it resolved to, any redirects, the response headers and the
  first few hundred characters of the body. It also states whether the response
  came from WordPress at all, which tells you straight away if a 404 was served
  by the web server or a security layer rather than by WordPress.
• The details are logged to the browser console on the Translate Pages screen,
  and a short summary is appended to the error shown in the status bar.
• New setting, Translation Settings → Fetching source pages → Fetch IP: enter an
  IP address and pages are fetched straight from it, for servers that cannot
  reach their own domain because it resolves to a CDN or a load balancer, or
  because their DNS does not know it. The Host header and the HTTPS certificate
  keep using your domain, so servers hosting several sites are unaffected. Empty
  by default, which uses normal DNS. The filter apgt_fetch_resolve_ip can
  override the stored value.

0.2.0

• Translation Settings and Languages: the language dropdowns are searchable now.
  Type a language name, an ISO code or the name in its own script to filter the
  list instead of scrolling through every language.
• Translate Pages: the current line is highlighted on both sides at once, so the
  line you are reading in the source is easy to find in the translation.
• Translate Pages: fixed the two panes losing sync near the end of long pages.
  When the translation wrapped to a different height than the source, the last
  lines of the taller pane could not be scrolled into view.

0.1.0

• Admin: translation settings, language management, page translation and
  translation data screens.
• Translation: by hand, background worker and on-the-fly, sharing per-page locks.
• Front end: language directory routing, internal link localization, hreflang,
  and a language switcher.
• SEO: localized sitemap URLs, and per-language Sitemap lines in robots.txt.
• Admin interface available in English, Simplified Chinese and Traditional
  Chinese. Language names in the admin follow the admin language too.