Saxon

Legacy ID: #3625155 Legacy Poster: Michael Kay (mhkay)

Interesting one. The language argument (the third argument of format-date()) defaults to the language of the default Java locale. Presumably in your case this is not English. If there is no localization of format-date installed for that language, format-date falls back to English, adding the string [Language: en] as required by the spec, to indicate that the language used is not the one requested. You can fix this by changing your call to format-date(current-date(),'[Y01]-[M01]-[D01]', 'en', (), ()) I'll have a think, though, about changing the design to avoid this problem occurring. Michael Kay Saxonica

Legacy ID: #3625333 Legacy Poster: Yannick (efolia)

Hi and thank you very much. It worked. I was convinced I had tried that solution before asking for advice, but I guess I must have applied it wrong: the 3-way logic (input/system/output) behind language switching is quite interesting but a little twisted conceptually. I don't see a solution to this problem except for implementing a mechanism that disables all the output that is not explicit -- for this problem is akind to including system error messages in the xsl output. For those of use who keep to XML and who design to purposely limit further processing by a programming language to a minimum, it would make lots of sense. My goal is to keep the solutions I design as close to pure XML as possible, thus avoiding all the traps and pitfalls that the programming solutions eventually lead to. Actually, this has only been possible since the release of XSLT 2.0 and its Saxon 8.7 implementation. Thanks again. :) Yannick