It seems like the Xliff Connector is broken. I am unable to create a job for/export more than one node at a time.
If I try to send my root node with children to translation, I get the following error. Seem the be the same as this.
I can then go to the Translation tab, and see that all the nodes are pending. If I then try and create a job for one or more of the nodes, I get this error:
I seem to be able to send a single node to translation and create a job for it at the same time. I can then export the Xliff file. But when I translate the content in the file, and try to import it again, I get this error:
The segment is missing , is reporting that the resulting xliff you have doesn't have one or more <target> elements which contain the translations.
XLIFF documents have a <source> tag which contains the text to be translated and then translation services/software usually put the translated text into a matching <target> element,
This error is there to tell you that some of the translation is missing - so you know you don't have a complete translation in the file.
(it can be overridden in the xliff connector settings you can tell it to take the source value if the target is missing, but then you are not getting translated text for those values just the source values copied over to the targerts
Oh. So this might just be me who does not understand how stuff works. I have never worked with an Xliff file, so I just opened it up in Notepad, changed a piece of random text and tried importing it. So I assume that is not something that can be done. And that it will probably work when we get the file back from the translation service?
you can edit them by hand, (creating the <target> values next to the <source> ones). and then that will import but it's not fun (we do occasionally do it for testing!).
the passthrough or one of the machine translation connectors, will do some of that for you if you just want to see things move from a -> b.
Xliff Connector is broken
It seems like the Xliff Connector is broken. I am unable to create a job for/export more than one node at a time.
If I try to send my root node with children to translation, I get the following error. Seem the be the same as this.
I can then go to the Translation tab, and see that all the nodes are pending. If I then try and create a job for one or more of the nodes, I get this error:
I seem to be able to send a single node to translation and create a job for it at the same time. I can then export the Xliff file. But when I translate the content in the file, and try to import it again, I get this error:
Versions: Umbraco CMS: 13.5.2 Translation Manager: 13.1.3
yes,
assuming this is the same as this other post, we have fixed that now:
This fixes exporting, but I am still getting the samme error (Segment is missing...) when I try to import a translated .xlf file.
Hi,
The segment is missing , is reporting that the resulting xliff you have doesn't have one or more
<target>elements which contain the translations.XLIFF documents have a
<source>tag which contains the text to be translated and then translation services/software usually put the translated text into a matching<target>element,This error is there to tell you that some of the translation is missing - so you know you don't have a complete translation in the file.
(it can be overridden in the xliff connector settings you can tell it to take the source value if the target is missing, but then you are not getting translated text for those values just the source values copied over to the targerts
Oh. So this might just be me who does not understand how stuff works. I have never worked with an Xliff file, so I just opened it up in Notepad, changed a piece of random text and tried importing it. So I assume that is not something that can be done. And that it will probably work when we get the file back from the translation service?
yeah,
you can edit them by hand, (creating the
<target>values next to the<source>ones). and then that will import but it's not fun (we do occasionally do it for testing!).the passthrough or one of the machine translation connectors, will do some of that for you if you just want to see things move from a -> b.
All right. Thanks for clearing that up.
is working on a reply...