Detecting language please wait for.......
I have a file from a customer, where a certain tag shall break segments.
This is the file:
<?xml version="1.0" encoding="UTF-8"?><xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:ns0="">scroll-translations.addons.k15t.com/xliff" ns0:exportTimestamp="1592826402925" ns0:original-language="de_DE" ns0:spaceKey="IM" ns0:target-language="en_GB" ns0:variantId="all" ns0:versionId="current" ns0:versionName="Currently Published" version="1.2"><file datatype="xml" ns0:exportTimestamp="1592826402925" ns0:original-language="de_DE" ns0:spaceKey="IM" ns0:target-language="en_GB" ns0:variantId="all" ns0:versionId="current" ns0:versionName="Currently Published" original="Dashboards speichern" source-language="de-DE" target-language="en-GB"><header><ns0:scrollHeader pageId="3868430" revision="9" scrollPageId="0AEFE06B01690F48C6A3469C04080387" spaceKey="IM" versionId="current"/></header><body><trans-unit id="ScrollPageTitle" restype="heading"><source>Dashboards speichern</source></trans-unit><group xmlns:ac="">http://atlassian.com/content" xmlns:ri="">atlassian.com/.../identifier" restype="x-storageFormat"><group id="group1" restype="x-p"><trans-unit id="tu1"><source><g ac:thumbnail="true" ac:width="30" ctype="x-image" id="g3" ns0:vsn-prefix="ac"><g ctype="x-attachment" id="g2" ns0:vsn-prefix="ri" ri:filename="icon_save_dashboard_DE.png"><g ctype="x-page" id="g1" ns0:vsn-prefix="ri" ri:content-title="Downloads"/></g></g> Haben Sie auf <g ctype="x-strong" id="g4">privaten Dashboards</g> Änderungen an Widgets vorgenommen, dann speichern Sie diese über das Icon "Dashboard speichern" in der Dashboardleiste.<g ctype="x-br" id="g5"/>Gespeicherte Dashboards werden beim nächsten Öffnen im zuletzt gespeicherten Stand geöffnet.</source></trans-unit></group></group></body></file></xliff>
This tag <g ctype="x-br" id="g5"/> is a soft-line break. But I can't see any way to adapt the segmentation in xliff file type. Is there any other method of forcing the segmentation to break here?
Hmmm, it looks like an XLIFF constructed by someone who doesn't fully understand the XLIFF principles...
(by that "someone" I mean K15t, the authors of the plugin, not your customer)
Okapi's UI is something to get used to, but it's a very useful translator's toolbox. You would want to create a translation kit, so that you can create the original file format again. You…
That should have been done when the XLIFF was generated and before the soft line breaks were converted to tags...
Thank you for your comment.
According to my customer it is not possible... My solution would be to treat the XLIFF as XML with embedded content, but they have only the source element, so before starting it would be necessary to duplicate source to target. Too much hassle for them.
Is what you posted one whole file? I can't even preview it in Studio.
Yes, it is a complete file.
I attach it as zip.3868430_Dashboards speichern_de_DE_en_GB.zip
Thanks a lot! I had copied the text of your initial post and somehow it did not get the links, so the second namespace was empty ("") and I puzzled over that a lot!
With your uploaded file it's all fine.
I can't get Studio to segment it, but Okapi does, and you can get Okapi's output. Okapi has a round-trip function, so you could have it segment all your files, then revert them. I would definitely do a pseudo-translation first to check that the round-trip works all the way...
Many thanks. So there is no way to force Studio to segment here. Which Okapi app do you mean here? I use only Olifant...
Hi Jerzy Czopik
As I understand it is part of the XLIFF idea that segmentation is done at creation of the file.
I am using the Okapi Rainbow Toolkit for this: https://okapiframework.org/wiki/index.php/Main_Page
Okapi's UI is something to get used to, but it's a very useful translator's toolbox. You would want to create a translation kit, so that you can create the original file format again. You have to use some srx file for the segmentation step, but I am sure you have that.