AumLang – AI Multilingual Translation & SEO

Registre de canvis

1.7.2

• A translation written in the wrong alphabet is no longer accepted. Nothing checked that what
  came back was in the language that was asked for. A provider that answers an Italian request with
  Chinese returns the right number of items, in valid JSON, with no error anywhere — so it was stored
  as the Italian translation, and retrying produced the same thing because the stored value already
  looked finished. Replies are now checked against the writing systems the target language actually
  uses, and one in the wrong script is treated as a failed attempt: the retry runs, and if that fails
  too the original text is kept. English left in place is a problem you can see; Chinese presented as
  Italian is one you cannot.
• The check only judges what can be judged with certainty — a script the language never uses. It does
  not try to tell Spanish from Portuguese, and it never rejects a reply for a language it does not
  know: not knowing is not evidence of an error.

1.7.1

• Bulk translation offered to translate posts that were themselves translations. The posts list
  shows translations alongside their originals, so a site with three languages has four times the
  rows — and “select all” selects what is on the screen. There is no way for the owner to tell which
  rows are copies, so the Japanese copies of three posts were counted as “will be translated into
  Japanese”: money spent to produce a Japanese translation of a Japanese page, overwriting what was
  there. Those are now left alone, and the confirmation screen says why.

1.7.0

• Translate many posts at once. Select rows in the Posts or Pages list, pick a language from the
  bulk actions menu, and AumLang works through them in the background. Until now the only way to
  translate was the button in the editor: one post, one language, one click. A site with twenty pages
  and five languages is a hundred clicks across twenty page loads, each waiting for the rounds to
  finish — not a slow workflow but an impossible one, and sites were sitting at a handful of
  combinations done while their owners reported the result as a fault in the translation.
• Because this spends money, Apply does not start anything. It opens a screen saying how many posts
  will actually be sent, how many already have a translation and will be left alone, and into which
  language. That screen has the button. The counts are worked out as the screen is drawn, never
  reused from a moment ago.
• A post that already has a translation is skipped rather than translated again, including one whose
  translation is out of date. Re-translating a single post stays where it was, on the button in the
  editor that says what it will do before it does it.
• The run survives the page being closed: it continues in the background and the progress screen
  picks it up again. Stop finishes the post it is on and then stops; posts already done stay done.

1.6.0

• A header or footer built as a page is now translated. Builder-driven themes keep the header,
  the footer and other global blocks in an ordinary page and render it inside every request with
  get_post(), which runs no query — so nothing this plugin had hooked could see it. The entry was
  in the translation list, translating it changed nothing on the front end, and there was no error
  anywhere. The content is now matched by an exact hash of itself, so it works regardless of how the
  theme fetched the page, and a theme that uses no such block pays one string comparison.
• Widget text is now translated whatever wrote the widget. The previous pass used the
  widget_title filter, which only fires if the widget itself calls it. Core widgets do; many others
  simply print the stored value, and for those the title stayed in the source language and never even
  appeared in the strings list, so there was nothing to notice. Every widget’s stored fields are now
  read before it renders. URLs, icons, CSS classes, ids, email addresses and phone numbers are left
  alone — translating those breaks the widget rather than the wording.
• 23 more languages show their flag. A flag was drawn from the region in the locale, and
  WordPress writes a number of locales with no region at all — Japanese is ja, not ja_JP. Those
  languages sat in the switcher with no flag beside the ones that had one. Languages genuinely spoken
  across several countries (English, Arabic, Swahili, Catalan, Basque) still show no flag, because
  there is no right answer for them and a wrong flag is worse than none.

1.5.1

• The plugins list now carries a Guide link beside Deactivate, pointing at this plugin’s
  manual in the language that administrator reads the admin in. The manual is the product’s
  full documentation; it is a separate thing from the plugin’s own help text.

Older entries are in changelog.txt, which ships with the plugin.