Welcome, Guest Login

Support Center

Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Segementation not working

Mandar Nov 08, 2017 08:35AM CET

Hi

I created following segmentation rule, and selected it while importing translation file.

<?xml version="1.0" encoding="UTF-8"?>
<srx xmlns="http://www.lisa.org/srx20" xmlns:okpsrx="http://okapi.sf.net/srx-extensions" version="2.0">
<header cascade="yes" segmentsubflows="yes">
<formathandle include="no" type="start" />
<formathandle include="yes" type="end" />
<formathandle include="no" type="isolated" />
<okpsrx:options oneSegmentIncludesAll="no" trimLeadingWhitespaces="yes" trimTrailingWhitespaces="yes" />
<okpsrx:rangeRule />
</header>
<body>
<languagerules>
<languagerule languagerulename="spec">
<rule>
<beforebreak>[\t\n\u2029\u3002]</beforebreak>
</rule>
</languagerule>

</languagerules>
<maprules>
<languagemap languagerulename="spec" languagepattern=".*" />
</maprules>
</body>
</srx>

But on editor i can't see the source segmented after \u3002 (Japanese fullstop character).
Am unable to understand why my segmentation rule not working?

Up 0 rated Down
Zuzana Smirgova Nov 08, 2017 09:03AM CET Memsource Help Center Agent

Dear Mandar,

Thank you for contacting us.

Memsource should actually segment after Japanese full-stop character by default so no special segmentation rules should be needed.

Could you please send us further details, such as your username, URL of the project and possibly the file you wanted to import to support@memsource.com?

Up 0 rated Down
Mandar Nov 08, 2017 09:25AM CET
Hi Zuzana

Ok...will send details soon.

Post Your Public Answer

Your name (required)
Your email address (required)
Answer (required)
support@memsource.com
https://cdn.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete