Leveraging Step: Fuzzy Matches Not Appearing as alt-trans in XLIFF Output (Discrepancy with documentation)

[Chinese translator and desktop publisher.]

Dear Okapi Framework Developers and Community,

I am writing to seek assistance regarding an unexpected behavior I'm observing with the Leveraging Step in Okapi Rainbow, specifically concerning the handling of fuzzy matches and their output to XLIFF.

According to the Okapi Wiki documentation - https://okapiframework.org/wiki/index.php/Leveraging_Step - for the "Leveraging Step" (specifically, the line "The matches that have a score equal or above a given threshold are placed into annotations that are attached to the target container or the target segments of the text unit"), I understand that fuzzy matches found by a translation memory should be recorded internally as annotations, and subsequently appear as <alt-trans> elements in the output XLIFF file.

However, in my testing, I am consistently observing that no fuzzy matches are recorded as <alt-trans> elements in the processed XLIFF output file, even when:

• I am using a single Pensieve TM source.
• The fuzzy matches are successfully identified by the Leveraging Step and are correctly written to the TMX document generated by the Leveraging Step (when that option is enabled). This confirms that Pensieve is finding the matches and the Leveraging Step is recognizing them.
• I have configured the Leveraging Step's parameters:
• "Accept matches that are equal or above this score" is set to a sufficiently low value (e.g., 70%) to capture fuzzy matches.
• "Fill the target with the best translation candidate" is set to 101% to prevent any fuzzy match from automatically filling the main <target> (and thus, hopefully, forcing them into <alt-trans>).

I have also carefully checked all available parameters within both the Leveraging Step itself and the subsequent XLIFF Output Filter step for any explicit options related to "proposals," "alternatives," or "annotations" that might enable the writing of <alt-trans> elements. I have not found any such explicit setting that seems to control this particular output behavior for fuzzy matches.

Could this be a configuration detail I'm missing, a change in behavior in recent versions not fully reflected in the wiki, or an issue with how these annotations are serialized to the XLIFF output? Any guidance or insight into how to properly configure the Leveraging Step and subsequent XLIFF output to include fuzzy matches as <alt-trans> elements would be greatly appreciated.

Thank you for your time and support.

Best regards,

Wei