I believe the Segments to Text Units Converter step does this.
But I’m not sure how you would merge back such flow of events if you need it.
One would probably have to create another step to put things back together.
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/CABm46bY2oUQ8joCKXfyRGh7sjs5aZxiXHJr0BG%2B4aQb0DLz2QA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-users/000201d75c6d%24bbfa6960%2433ef3c20%24%40gmail.com.
Yes, I think there is currently no step that puts back the several TUs into a single one. (or maybe it exist, but it’s not documented, but I doubt it).
The “exploding” step was likely made for other purpose than merging back.
So, currently, I’m afraid there is no out-of-the-box solution for this type of processing.
setThrowCodeException(false); // compare tu inline codes setThrowSegmentIdException(true); // compare tu id's setThrowSegmentSourceException(false); // compare tu source
To view this discussion on the web visit https://groups.google.com/d/msgid/okapi-users/CABm46bb3j13i5ER9jrR6LfZqjudhTBWE1ygg-dA72KEyhJwZPA%40mail.gmail.com.