Skip to content

Releases: Jumoo/Jumoo.TranslationManager.Issues

v13.1 / v10.6 / v12.6 - BlockList and other formatting

23 May 08:09
d0e9456
Compare
Choose a tag to compare

This is a minor release of Translation Manager for Umbraco v10, 12, and v13. it contains some fixes to how block list translations are handled.

due to the nature of these changes we recommend that this update is only appled when you have no outstanding translations. (see below)

What's Changed

New

  • ⭐ Preserve versions of content (prevent cleanup) that are used in translations
  • ⭐ Don't include include styles and script tags in Xliff 1.2 serialization when splitting inline html
  • ⭐ New options to clean up non-breakable spaces in xliff
  • ⭐ New options to perform replacements in encoded xliff 1.2 values

Fixes

  • 🐛 View button on an item shouldn't show when content item isn't published
  • 🐛 Fix copy from source if value is blank in Xliff 1.2 serializer
  • 🐛 Fix block list/grid translations find items by position within grid when key lookup doesn't work.
  • 🐛 Fix - hitting return in a content items name box causes the set dialog to open (for admins).

Blocklist/BlockGrid update

This release changes the way that block list items are indexed inside a translation job, previously jobs where indexed by the blockId, but between translated versions of a content item these values can become out of sync.

From this version content blocks are indexes based on postion and type of content item, this means we can always find the content blocks even when their internal keys have changed.

If you use block list or block grids then any existing translation jobs will be using the old key based index. and when this update is appled Translation manger will attempt first to look for the posistion based index. it should fall back to the key based index and find your content blocks but as with any update there is a small chance that this lookup will not work.

The likelyhood of this lookup not working is low, but whenver we change anything of this nature we change the minor version of the release and we recommend that you do not update with inprogress translation jobs.

v13.0.5 / v12.5.5 / v10.5.5 - XLIFF 1.2 tweaks and fixes.

22 Feb 15:42
d0e9456
Compare
Choose a tag to compare

This is a patch release of Translation Manager for Umbraco 13/12 and 10. It contains some fixes to how XLIFF 1.2 can be serialized (non-breaking). and a fix for the clone button, so it reloads the content node after clone (#57)

What's New

  • XLIFF 1.2
    • consistent casing of "html" in restype attribute
    • ensure sub/sup are inline when using generic 'g' tags
    • ensure id values for anchors and other html elements don't clash with XLIFF tag id values.
    • html namespaces for html based attributes
  • 🐛 Fix #57 - clone button should reload the content node once the clone operation is complete.

v13.0.4 / 12.5.4 / 10.5.4 - Patch release

07 Feb 11:45
d0e9456
Compare
Choose a tag to compare

This is a minor patch release rollup for Translation manager for Umbraco v10,v12 & v13 it contains the following fixes

13.0.4 / 12.5.4 / 10.5.4

  • 🐜 Fix: Link updater causes extra save of source element when processing loopback link checks.
  • 🐜 Fix: Translate Icon disappears from the context menu when you click it twice
  • ✅ Update: Allow providers to show status in the job list in the translate section and status list in the content app
  • ✅ Update: Streamline how many items are shown on Content App status page when you have multiple sets
  • ✅ Update: Improved the layout of the content app on smaller screens.

13.0.3 / 12.5.3 / 10.5.3

  • 🐜 Fix: 'undefined' in send to translate dialog title
  • 🐜 Fix: Block Element Id mapping between variant blocks (block ids are unique but deterministic, so they can be translated into)

13.0.2 / 12.5.2 / 10.5.2

  • 🐜 Fix: for using "include targets" in XLIFF 2.1 direct serializer

13.0.1 / 12.5.1 / 10.5.1

  • 🐜 Fix: for Block elements inside RTEs when using XLIFF 1.2 serializer

v13.0.0 - Translation Manager - Major Release 🫡

14 Dec 16:44
d0e9456
Compare
Choose a tag to compare

This is the major, long term support (LTS) release of Translation Manager for Umbraco v13. it contains updates to support new features in Umbraco v13.

Translation Manager v13 is a long term support (LTS) release, and is a licence update release, meaning you will need an updated licence key to use this version - checkout our recent prices blog post for more details

Whats New

  • Support for Umbraco 13
    • RTE Blocks translations
  • Support for .NET 8

12.4.2 / 10.4.2 release

10 Oct 08:10
d0e9456
Compare
Choose a tag to compare

This is a patch releaze to address a clash between the uSync and Translation manager licensing controls.

Fixes

#54 Error - The HttpClient factory already has a registered client with the name

We have delisted in nuget v12.4/10.4 in favour of this release.

12.4 / 10.4 - release

24 Sep 19:04
d0e9456
Compare
Choose a tag to compare

This is a minor update of Translation Manager, it contains fixes and updates to features.

This update is for Umbaco 10 & 12 versions of translation manager

please note Umbraco 11, in now in a security update's only phase and as such no Translation Manager updates will be released for version 11.

What new

  • Xliff 1.2 improvements
    • option to use the '' tag for html elements
  • Added ability to disable core connectors in settings]
  • New set options
    • Always create job (removes the create job button from editors)
    • Hide children (only ever sends on page, removes 'include children' from editors

Fixes

  • using RegEx expressions to exclude the only item on a double nested (or above) block list item can result in orphaned target elements
  • Saving items in a loopback "non-master" culture still puts the items in pending.
  • selecting items across multiple pages in the pending list doesn't remember selection from previous page.

12.3.3 (plus 11..3.3 & 10.3.3) Patch release

11 Sep 06:37
d0e9456
Compare
Choose a tag to compare

This is a patch release for Translation Manager for Umbraco 10/11/12 - it contains minor patches to reported issues.

Please note this is the LAST non-security update for v11 - as Umbraco v11 has now entered a security only phase

Fixes:

  • Fix for grouped Translation connectors using pending queue (connectors that send multiple jobs to a single project/job on the provider's system)
  • DeepL connector Library upgrade (fixes use of free/paid service tiers)

v10/11/12.3.0 Mega release

28 Jun 12:55
d0e9456
Compare
Choose a tag to compare

This is the next super shared release of Translation Manager for Umbraco 10, 11 and 12 .

We release 3 nuget versions (on for each version) but they all come from a shared codebase so include the same features.

Fixes

  • Notification Email templates not found in RCL package
  • improve error messaging around missing target nodes, limit error so less false positives for missing nodes
  • Fix 'Add all configured domains' so it actually adds all configured domains
  • Linux container file case issues #48

Features

  • Setting to allow on published items to go into the Pending queue
  • Ensure all blocklist elements have unique id's in translated content
  • allow for splitting of xliff responses into multiple files, and upload of multiple xliff files for a single job
  • add ability to show word count for content item and all decendents

Getting Translation Manager

Install the version for your version of Umbraco . eg.

Umbraco 10

dotnet add package Jumoo.TranslationManager --version 10.3.0 

Umbraco 11

dotnet add package Jumoo.TranslationManager --version 11.3.0

Umbraco 12

dotnet add package Jumoo.TranslationManager --version 12.3.0

Detailed Notes

This version is multi-targeted but does not produce a multi-targeted package, rather it produces two versions of the package from the same code on for version 10.x of Umbraco and one for v11.x.

This means you still install the version that is relevant for your release as it has been targeted for your Umbraco release rather than the .net runtime that release is actually running on.

Development wise this means

  • We only have one code base to support for v10, v11 & v12
  • All updates can go back to the Long Term Support release (v10.x)
  • Changes between versions can be controlled at build time so we don't have complicated code checking what version of Umbraco you are running.

v11.2 / v10.2 - Together release

11 Apr 09:24
2bc0c49
Compare
Choose a tag to compare

This is a minor version release of Translation manager for Umbraco 10 and Umbraco 11.

This release re-unifies the v10 and v11 code branches - we now build two versions of the shared code (v10/.net 6 and v11/.net 7). so we have one release for all v10 and v11 releases of the Product.

Fixes

  • #50 Cannot send to pending when auto create is set to false.
  • Error displaying username on history if name appears more than once
  • Fix : Uploading a file second time on XLIFF provider page requires reload.
  • Improve error reporting dialog.

Getting Translation Manager

Install the version for your version of Umbraco . eg.

Umbraco 10

dotnet add package Jumoo.TranslationManager --version 10.2.0 

Umbraco 11

dotnet add package Jumoo.TranslationManager --version 11.2.0

Detailed Notes

This version is multi-targeted but does not produce a multi-targeted package, rather it produces two versions of the package from the same code on for version 10.x of Umbraco and one for v11.x.

This means you still install the version that is relevant for your release as it has been targeted for your Umbraco release rather than the .net runtime that release is actually running on.

Development wise this means

  • We only have one code base to support for v10, v11 & v12
  • All updates can go back to the Long Term Support release (v10.x)
  • Changes between versions can be controlled at build time so we don't have complicated code checking what version of Umbraco you are running.

v8.7.11 - Multiple sets sharing languages

01 Mar 12:38
1ebc54d
Compare
Choose a tag to compare

This is a minor patch release for Translation manager v8 for Umbraco 8 . It contains a backported fix for a issue that occurs when you have two or more sets that have the same source and target nodes.

You do not need to update to this release unless you are experiencing this specific issue .

(please note - the main supported release for Umbraco 8 is now Translation Manager v9)

Fix

  • If you have two or more sets that have the same source and target nodes in them using variants . then when you attempt to send the a language to translation you might see the 'Nodes can only be from one translation set' message.
  • this fix - removes that by property passing the set and site id to the backend when creating nodes.

This fix was included in v9.16 / v10.1.3 and v11.0.2