Changeset 3807199
- Timestamp:
- 11/17/2026 11:06:58 AM (less than one hour ago)
- File:
-
- 1 edited
-
autolingo-polylang-translate/trunk/readme.txt (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
autolingo-polylang-translate/trunk/readme.txt
r3806093 r3807199 5 5 Tested up to: 7.1 6 6 Requires PHP: 8.0 7 Stable tag: 1.13. 17 Stable tag: 1.13.2 8 8 License: GPLv2 or later 9 9 License URI: https://www.gnu.org/licenses/gpl-2.0.html … … 277 277 == Changelog == 278 278 279 = 1.13.2 = 280 * DiviFlash: FAQ questions and the other texts of DiviFlash modules are translated (Pro) 281 * Divi: a module's tablet, phone and hover texts are translated, the Text module's included (Pro) 282 * Structured data written by hand in the content (a <script type="application/ld+json"> in a Divi Code module or an HTML block): its texts (name, headline, description, answers…) are translated, inLanguage takes the language of the translation, and the site's addresses point to the translated pages 283 * Scripts and styles in the content are no longer sent to the translation provider: an AI provider could otherwise rewrite code, and they cost characters 284 * Internal links keep their anchor (#section) when they are pointed to the translated page 285 279 286 = 1.13.1 = 280 287 * Divi (module settings, Theme Builder, menu modules) and Contact Form 7 are now part of AutoLingo Pro, like the other page builders. The free version still translates the text between Divi shortcodes and keeps the shortcodes as they are
Note:
See TracChangeset
for help on using the changeset viewer.