<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello,<br>
<br>
The localization options are defined in the Schematron
specification. You can use the diagnostic element to specify the
message in multiple languages.<br>
<a class="moz-txt-link-freetext" href="http://www.schematron.com/iso/P8.html#GEN17">http://www.schematron.com/iso/P8.html#GEN17</a><br>
<br>
There is also an example of a multilingual schema in the Annex G
of the Schematron specification:<br>
<a class="moz-txt-link-freetext" href="http://www.schematron.com/iso/P27.html#GEN39">http://www.schematron.com/iso/P27.html#GEN39</a>
<pre style="margin-top: 0px; margin-bottom: 0px;"><span style="font-family: 'Courier New';">
<sch:schema xmlns:sch=<a class="moz-txt-link-rfc2396E" href="http://purl.oclc.org/dsdl/schematron">"http://purl.oclc.org/dsdl/schematron"</a>
xml:lang="en" >
<sch:title>Example of Multi-Lingual Schema</sch:title>
<sch:pattern>
<sch:rule context="dog">
<sch:assert test="bone" diagnostics="d1 d2">
A dog should have a bone.
</sch:assert>
</sch:rule>
</sch:pattern>
<sch:diagnostics>
<sch:diagnostic id="d1" xml:lang="en">
A dog should have a bone.
</sch:diagnostic>
<sch:diagnostic id="d2" xml:lang="de">
Das Hund muss ein Bein haben.
</sch:diagnostic>
</sch:diagnostics>
</sch:schema></span>
</pre>
<br>
<br>
Best Regards,<br>
Octavian<br>
<br>
On 11.01.2016 15:59, Tony Graham wrote:<br>
</div>
<blockquote cite="mid:5693B541.7030603@antenna.co.jp" type="cite">On
11/01/2016 13:24, Oxygen XML Editor Support (Octavian Nadolu)
wrote:
<br>
<blockquote type="cite">The Schematron multilingual messages
support will be available in
<br>
the next oXygen version. The presentations from the XML Prague
2016
<br>
oXygen User Meetup are containing both features that are
available
<br>
in oXygen 17.1 and features that will be available in the next
<br>
oXygen version. We will wait you at the presentation to discuss
the
<br>
features and give us feedback.
<br>
</blockquote>
<br>
I look forward to it.
<br>
<br>
Currently, for the Japanese version of 'focheck' [1], I'm using a
<br>
patched version [2] of the open source OmegaT translation memory
tool to
<br>
get whole Schematron files translated. I've implemented l10n
lookup
<br>
from XML property files using XSLT before, but implementing
extracting
<br>
messages to property files and generating translated Schematron
files
<br>
using translated property files seemed like too much effort for
just the
<br>
'focheck' project.
<br>
<br>
Hindsight is the only perfect science, but I've never understood
why
<br>
multilingual messages wasn't built into Schematron from the
beginning.
<br>
<br>
Regards,
<br>
<br>
<br>
Tony Graham.
<br>
</blockquote>
<br>
</body>
</html>