Usage of storage size with xml-its filter

[Marc Mittag]

Dear all,

there is a second question today:

I tried to use the extraction of the storage size with the
xml-its-filter as described here:

https://www.w3.org/TR/its20/#storagesize

Works like a charm.

The only issue, that astonishes me is, that the extracted xliff fragment
looks like this

<source xml:lang="en-US" its:storageSize="30">Interesse geweckt?</source>

instead like this

<source xml:lang="en-US" maxwidth="30" size-unit="char">Interesse
geweckt?</source>

Since Okapi always tries to work with the standards as far as possible,
I would have expected, that no additional name space is added to the
xliff, if something exists in the standard, that does the job.

Is there a way to make Okapi do so? If I uncheck the option "Include ITS
mark-up, when available" in the "Generic xliff settings" of the
translation kit step, nothing is added to the xliff that shows the
length restriction. I would have expected a fallback to what the
standard offers in that case.

best

Marc

[Chase Tingley]

Without looking at the code, I think this is an oversight that needs to be fixed in the filter. IIRC the ITS annotations are all serialized to XLIFF as a special case because this is a desirable thing to do for annotations like LQI, Provenance, etc. In this case, the filter needs to map the storage-size annotation to the standard maxwidth property that will serialize correctly.

--
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 on the web visit https://groups.google.com/d/msgid/okapi-users/c6b81f8c-b760-4ccb-a684-d656cf5ce115%40marcmittag.de.

[Marc Mittag]

this means, I understand it correctly, that if the option "Include ITS  mark-up, when available" in the "Generic xliff settings" is checked, it should look like

<source xml:lang="en-US" its:storageSize="30">Interesse geweckt?</source>

and it is a bug, that if it is unchecked it does not look like this?

<source xml:lang="en-US" maxwidth="30" size-unit="char">Interesse
geweckt?</source>

best

Marc

[Chase Tingley]

I think it’s a bug that there’s no way to write this out as maxwidth. I’m wondering if we should *always* write out maxwidth, and then also redundantly wrote out its:storageSize if the ITS option is set. Doing one or the other seems like maybe it’s being clever at the expense of making it harder to use.

[Marc Mittag]

Would make sense for me.

How can we go forward with a fix?

Should I ask Denis to implement it?

best

Marc

[Jim Hargrave]

>> we should *always* write out maxwidth, and then also redundantly wrote out its:storageSize if the ITS option is set

+1

Looking at XmlWriter this is exactly what we do. The issue is the XML ITS filter not populating a Property for maxsize (Property.MAX_WIDTH) etc..

Jim

To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-users/CAGRYq4ja5u5pr9opuhbf14h71TEH%2Bb4B67vTi5LyyHN%3DyJimyQ%40mail.gmail.com.

This e-mail and any attachments are confidential and intended solely for the intended addressee. If you are not the intended addressee or have received this e-mail in error, please notify Straker immediately, delete it from your system and do not copy, disclose, distribute or otherwise act in reliance upon any part of this e-mail or its attachments. Straker will not be held liable for any damage caused by the message.
Is it necessary to print this email? If you care about the environment like we do, please refrain from printing emails. It helps to keep the environment forested and litter-free.

[Chase Tingley]

Sure, if you could reach out to Denis, that would be great.  Hopefully this should not be too hard.

[Marc Mittag]

ok, will do :-)

best

Marc