http://okapiframework.org/wiki/index.php?action=history&feed=atom&title=SRX_ExtensionsSRX Extensions - Revision history2026-04-17T17:29:40ZRevision history for this page on the wikiMediaWiki 1.38.2http://okapiframework.org/wiki/index.php?title=SRX_Extensions&diff=325&oldid=prevYsavourel: 1 revision imported2016-06-04T23:19:59Z<p>1 revision imported</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<tr class="diff-title" lang="en">
<td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 19:19, 4 June 2016</td>
</tr><tr><td colspan="2" class="diff-notice" lang="en"><div class="mw-diff-empty">(No difference)</div>
</td></tr></table>Ysavourelhttp://okapiframework.org/wiki/index.php?title=SRX_Extensions&diff=324&oldid=prevYsavourel at 05:43, 23 June 20112011-06-23T05:43:43Z<p></p>
<p><b>New page</b></p><div>__TOC__<br />
The Okapi framework implements a few extensions to [[SRX]].<br />
<br />
It is important to use those extensions carefully as they may make your SRX document incompatible with other SRX implementations. They may also make your SRX document compatible with some implementations, for example some systems trim white spaces from segments automatically even if there is no such option is SRX&nbsp;2.0.<br />
<br />
The namespace to declare them is <code><nowiki>http://okapi.sf.net/srx-extensions</nowiki></code><br />
<br />
Most of the extensions are placed at the end of the <code>&lt;header></code> element of the SRX file. For example:<br />
<br />
<nowiki><srx xmlns="http://www.lisa.org/srx20" version="2.0"</nowiki><br />
<span class='hi'><nowiki>xmlns:okpsrx="http://okapi.sf.net/srx-extensions"</nowiki></span>><br />
<header segmentsubflows="yes" cascade="no"><br />
<formathandle type="start" include="no"></formathandle><br />
<formathandle type="end" include="yes"></formathandle><br />
<formathandle type="isolated" include="no"></formathandle><br />
<span class='hi'><okpsrx:options oneSegmentIncludesAll="yes"</span><br />
<span class='hi'> trimLeadingWhitespaces="yes"</span><br />
<span class='hi'> trimTrailingWhitespaces="yes"</span><br />
<span class='hi'>/></span><br />
<span class='hi'><okpsrx:sample language="en" useMappedRules="yes">Mr. Holmes is from the U.K.</okpsrx:sample></span><br />
<span class='hi'><okpsrx:rangeRule>pattern</okpsrx:rangeRule></span><br />
</header><br />
<body><br />
...<br />
</srx><br />
<br />
==== trimLeadingWhitespaces ====<br />
<br />
This extension indicates that leading white spaces in the segments should be moved out of the segment.<br />
<br />
Possible values: <code>yes</code> or <code>no</code> Default: <code>no</code><br />
<br />
A value <code>yes</code> makes the SRX document not compatible with strict SRX implementations.<br />
<br />
Example:<br />
<br />
<okpsrx:options trimLeadingWhitespaces="yes" /><br />
<br />
==== trimTrailingWhitespaces ====<br />
<br />
This extension indicates that trailing white spaces in the segments should be moved out of the segment.<br />
<br />
Possible values: <code>yes</code> or <code>no</code> Default: <code>no</code><br />
<br />
A value <code>yes</code> makes the SRX document not compatible with strict SRX implementations.<br />
<br />
Example:<br />
<br />
<okpsrx:options trimTrailingWhitespaces="yes" /><br />
<br />
==== oneSegmentIncludesAll ====<br />
<br />
This extension indicates that when an entry (text unit) is composed of a single segment after the segmentation has been applied, that segment must include all the content of the entry, for example overriding the trimming extensions.<br />
<br />
Possible values: <code>yes</code> or <code>no</code> Default: <code>no</code><br />
<br />
A value <code>yes</code> makes the SRX document not compatible with strict SRX implementations.<br />
<br />
Example:<br />
<br />
<okpsrx:options oneSegmentIncludesAll="yes" /><br />
<br />
==== sample ====<br />
<br />
This extension allows you to store a sample text in the SRX document. That text can be used to what segmentation results from applying the rules of the document.<br />
<br />
The <code>language="yes|no"</code> attribute indicates the language code to use when applying the rules on the sample.<br />
<br />
The <code>useMappedRules="yes|no"</code> attributes indicates if all languages rules for the given language should be applied on the sample. If the value is <code>no</code> only the language rules currently displayed should be used.<br />
<br />
Defaults: Empty sample text, language: en, useMappedRules: yes<br />
<br />
This extension does not affect the compatibility of your rules.<br />
<br />
Example:<br />
<br />
<okpsrx:sample<br />
language="en"<br />
useMappedRules="no"<br />
>Mr. Holmes is from the U.K.</okpsrx:sample><br />
<br />
==== rangeRule ====<br />
<br />
This extension indicates that the specified regular expression patter should be searched on the text unit being segmented and if found, a segment corresponding to the matching content should be made a segment, overriding normal segmentation rules.<br />
<br />
This is useful for example in content where you may have a great number of inline codes mixed with no-translatable text and translatable text where using normal rules is too complicated.<br />
<br />
A non-empty content makes the SRX document not compatible with strict SRX implementations (if the specified pattern occurs in the text being segmented).<br />
<br />
Example:<br />
<br />
<okpsrx:rangeRule>thePattern</okpsrx:rangeRule><br />
<br />
[[Category:Segmentation]] [[Category:SRX]]</div>Ysavourel