[oXygen-user] Multilingual Schematron messages?

Octavian Nadolu
Tue Jan 12 06:24:21 CST 2016


Hello,

The localization options are defined in the Schematron specification. 
You can use the diagnostic element to specify the message in multiple 
languages.
http://www.schematron.com/iso/P8.html#GEN17

There is also an example of a multilingual schema in the Annex G of the 
Schematron specification:
http://www.schematron.com/iso/P27.html#GEN39

<sch:schema xmlns:sch="http://purl.oclc.org/dsdl/schematron" 
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>



Best Regards,
Octavian

On 11.01.2016 15:59, Tony Graham wrote:
> On 11/01/2016 13:24, Oxygen XML Editor Support (Octavian Nadolu) wrote:
>> The Schematron multilingual messages support will be available in
>> the next oXygen version. The presentations from the XML Prague 2016
>> oXygen User Meetup are containing both features that are available
>> in oXygen 17.1 and features that will be available in the next
>> oXygen version. We will wait you at the presentation to discuss the
>> features and give us feedback.
>
> I look forward to it.
>
> Currently, for the Japanese version of 'focheck' [1], I'm using a
> patched version [2] of the open source OmegaT translation memory tool to
> get whole Schematron files translated.  I've implemented l10n lookup
> from XML property files using XSLT before, but implementing extracting
> messages to property files and generating translated Schematron files
> using translated property files seemed like too much effort for just the
> 'focheck' project.
>
> Hindsight is the only perfect science, but I've never understood why
> multilingual messages wasn't built into Schematron from the beginning.
>
> Regards,
>
>
> Tony Graham.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20160112/b4821155/attachment.html>


More information about the oXygen-user mailing list