Skeleton format

[Phil Ritchie]

Hi All

Long time!

I should know this but what format is the `<skl><internal-file/>` beginning "L+NZPP" in 1.2 XLIFF's?

I want to decode it. 

[yves.s...@gmail.com]

Hi Phil,

 

Long time indeed !

 

I’m not aware of any “L+NZPP” in XLIFF 1.2.

The <skl><internal-file> is to store the skeleton file internally vs externally.

Usually tools then use some type of base64 encoding to write out the skeleton data inside that element. That content is tool-specific.

 

I hope it helps.

-yves

--
You received this message because you are subscribed to the Google Groups "okapi-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-devel...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/okapi-devel/fdf18e18-fd7a-4ce7-8df7-92ea8ab75fcdn%40googlegroups.com.

[Phil Ritchie]

Was looking through the source code at GenericSkeletonWriter. Would it be raw (binary) data? The files in question come from XTM.

Have tried decoding it as Base64 but it doesn't produce anything readable or what would look like a compression signature. 

To view this discussion visit https://groups.google.com/d/msgid/okapi-devel/002c01dcd1aa%2495e9df50%24c1bd9df0%24%40gmail.com.

[Chase Tingley]

It's essentially implementation-dependent in whatever tool generated the XLIFF, so XTM in your case.

SDLXLIFF files often have <internal-file form="base64">, which contains a base64-encoded copy of the original source file.  The spec says the accepted values for the "form" attribute are "text", "base64", or a MIME type.  But that attribute is itself optional.

Okapi doesn't really do anything with that value, either when parsing or generating our own XLIFFs.

There is a unittest in okapi/filters/xliff/src/test/java/net/sf/okapi/filters/xliff/XLIFFFilterXtmPropTest.java called testXtmDetection() that implies that XTM does use Base64 data.  

To view this discussion visit https://groups.google.com/d/msgid/okapi-devel/CAEww_4P8%3DQEjdD2Bfq8xUR9xhiRL9v_LirmjqysoW-Vb8hNbfg%40mail.gmail.com.