I was a bit disapointed to find out that this functionality isn't built-in in oxygen 23; the plug-in is now for a quite out-of-date version of saxon

Any chance of a Saxon-JS compiling plug-in?

Cheers,
Tom

Hi folks,

Now that google code has been shut down, is there an equivalent github repo for dita-ng?

Thanks,
Tom

What is the maximum number of folds, out of interest?

Thanks, Radu!

It doesn't quite answer my question, but I'll follow up with a comment on the blog post

Tom

IS this still the recommended way of implementing this (as of version 17)? I ask since it seems incompatible with the idea of creating an extension to the DITA framework and distributing it as an Add On; is there no way of doing this other than replicating (and therefore having to maintain) the whol...

Yes, removing the 'hex' option bypasses the bug.

In my case that's fine for debugging (or I just live with the invalid result), but the 'hex' option needs to be there when actually run.

So it's not a show-stopper or anything, just a minor annoyance.

Hi Adrian, What was the result of this query? I am experiencing the same symptoms (inclusion of the same illegal characters when running through debugger, expected output when using transformation scenario). I believe that in my case it is tied to the use of saxon:character-representation='hex' on x...