I’m evaluating the Translation manager package for a potential project. I am trying it on an Umbraco 15.2.2 instance, with Jumoo.TranslationManager 15.0.3. Sending/recieving translations all seems to work great (testing with Google & Microsoft translation APIs), but i have queries about the approval process:
if a translated response for a node is not quite right, is it possible to edit individual content nodes before moving to the approval process? Or is the idea you choose Save and mark as ‘reviewing’, and then edit in the CMS after importing it?
is it possible to only accept specific/individual nodes, but not others? Is there a way to select which nodes to import? Or is it all or nothing?
Is some functionaly hidden because I am not using a licence, or perhaps I am looking in the wrong place? It sounds from the docs it might be possible (Approve Translations | Jumoo docs)? Does anyone with experience of the package have any insights?
Yes, when you get a translation set back (whether from one of the automatic connectors, or if you’ve received an XLIFF file) you can go through every node and compare the translations. You can also edit them right there, before you mark them as approved (can’t remember the exact wording). When you’re done reviewing and ready to do the final “Approve”, you can also select individual nodes - you’re not forced to just import “everything”.
Thanks Chriztian. This sounds good, but I can’t see any option for this. Do you know version you have seen this in? Or perhaps the options are unlocked when a licence is applied?
This is what i see for the review panel where you can compare text, but there is no option to edit the translation:
At the moment the v15 version doesn’t have the ability to edit the returned translation here.
we are looking at it, with loads of feedback from translation providers, this feature can actually causes them some grief - because editing the translation here doesn’t then update anything on the translation system so if you send something for translation again, the same mis-translation is passed through.
Appreciate for machine translation this isn’t quite the same. so thats one of the reasons we are looking at it.
but for Microsoft translations we have added the ability to use the custom translations features of the Microsoft API so in theory you can put things like this into a custom translator so they are the same each time.
Thanks Kevin. Does this also mean an editor cannot accept translated nodes individually, and instead translations have to be accepted/rejected at the page level?
only when a job has been received (but this is when you would want to do it).
and we haven’t yet got it using a RTE (or TipTap) for HTML values, but you can edit them, which is the start.
(all the other stuff about doing it in the source system stands )
)