Hello Tony, Unfortunately we do not support multiple languages for the Schematron messages. We have an issue on our issue tracker regarding this problem and I will increase it's priority. The Schematron messages are generated at validation and we need to collect only the diagnostics with the xml:lang equal with the one form the application. Now all the messages are collected, the xml:lang attribute is ignored. If you make multiple single language Schematron files, maybe you can create for each one a validation scenario and depending on the language use the specific validation scenario. But you will need to associate the scenario manually. Or you can create different projects and save the validation scenario and the association in the project, and when you will change the project you will have the specific validation. Other workaround is to use the "phase" mechanism. You can create a Schematron with multiple phases, a phase for each language. At validation oXygen will present a dialog with the phases and you can select the one you want depending on the language. I added an issue also for the annotations, to support multiple languages. Here is the same problem we collect all the annotations without looking at the lang attribute. Best Regards, Octavian -- Octavian Nadolu <oXygen/> XML Editor http://www.oxygenxml.com On 20.08.2015 01:47, Tony Graham wrote:
I'm looking at localising the Schematron messages in 'focheck' (https://github.com/AntennaHouse/focheck).
The non-normative advice in Annex G, "Use of Schematron for Multi-Lingual Schemas", in the Schematron spec is to use multiple <diagnostic>, one for each translation of the text from an <assert> or <report>.
oXygen, unsurprisingly, shows every applicable <diagnostic>. This gets a bit cluttered and, for some user, puts the readable version of the message right at the very end.
Is there a way to put multiple, localised versions of a message in a Schematron file and have only the preferred one show? Is there an alternative to making multiple single-language versions of the Schematron?
And, while I'm at it, what can be done about l10n of the annotations in Relax NG schema that become tool-tips in oXygen?
Regards,
Tony Graham.