Differences in tikal output between recent versions

10 views

Skip to first unread message

Pablo Gómez

unread,

Mar 4, 2026, 5:16:59 AMMar 4

to okapi-users

Hi all,

I have recently moved from 1.1.45 to 1.1.48 and I get different results with identical input file and commands when extracting XLIFF from a DITA file:

This is the output of 1.1.45 (Tikal Version: 2.1.41.0):

<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:okp="okapi-framework:xliff-extensions" xmlns:its="http://www.w3.org/2005/11/its" xmlns:itsxlf="http://www.w3.org/ns/its-xliff/" its:version="2.0">
<file original="products/LM35/REFERENCE_KEYS/EN/button_names_ref.dita" source-language="en" target-language="de" datatype="xml" okp:inputEncoding="UTF-8">
<body>
<trans-unit id="tu1" resname="power_lm35-id">
<source xml:lang="en"><g id="1"><g id="2">Power</g> button on the <g id="3">optical block</g></g></source>
<seg-source><mrk mid="0" mtype="seg"><g id="1"><g id="2">Power</g> button on the <g id="3">optical block</g></g></mrk></seg-source>
<target xml:lang="de"><mrk mid="0" mtype="seg"><g id="1"><g id="2">Power</g> button on the <g id="3">optical block</g></g></mrk></target>
</trans-unit>

and this is the output of the 1.1.48 (Tikal Version: 2.1.48.0-SNAPSHOT)

<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:okp="okapi-framework:xliff-extensions" xmlns:its="http://www.w3.org/2005/11/its"
xmlns:itsxlf="http://www.w3.org/ns/its-xliff/" its:version="2.0">
<file original="/C:/MySandbox/manuals/LET/products/LM35/REFERENCE_KEYS/EN/button_names_ref.dita"
source-language="en" target-language="de" datatype="xml" okp:inputEncoding="UTF-8">
<body>
<trans-unit id="tu1" resname="power_lm35-id">
<source xml:lang="en"><bpt id="1">[#$dp4]</bpt><bpt id="2"><uicontrol></bpt>Power<ept id="2"></uicontrol></ept> button on the <bpt id="3"><ph conkeyref="cref/optical_block"></bpt>optical block<ept id="3"></ph></ept><ept id="1"></ph></ept></source>
<seg-source><mrk mid="0" mtype="seg"><bpt id="1">[#$dp4]</bpt><bpt id="2"><uicontrol></bpt>Power<ept id="2"></uicontrol></ept> button on the <bpt id="3"><ph conkeyref="cref/optical_block"></bpt>optical block<ept id="3"></ph></ept><ept id="1"></ph></ept></mrk></seg-source>
<target xml:lang="de"><mrk mid="0" mtype="seg"><bpt id="1">[#$dp4]</bpt><bpt id="2"><uicontrol></bpt>Power<ept id="2"></uicontrol></ept> button on the <bpt id="3"><ph conkeyref="cref/optical_block"></bpt>optical block<ept id="3"></ph></ept><ept id="1"></ph></ept></mrk></target>
</trans-unit>

The command is identical in both cases:

tikal.bat -sl EN -tl DE -ie UTF8 -oe UTF8 -fc okf_xmlstream-dita -x <files_in> -seg <srx file>

Should I apply any filter or option anywhere?. XLIFF versions appear to be identical. Do you need an example source file for testing?

yves.s...@gmail.com

unread,

Mar 4, 2026, 5:27:07 AMMar 4

to Pablo Gómez, okapi-users

Looks like the default inline code mode for the XLIFF extraction has changed.

I don’t think there is an option for it in Tikal (unlike from Rainbow).

Both should work without difference.

-ys

--
You received this message because you are subscribed to the Google Groups "okapi-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/okapi-users/608afc43-5396-44e0-bdb8-3035ef4a4762n%40googlegroups.com.

Reply all

Reply to author

Forward

0 new messages