Search found 6 matches

by yamahito
Thu Jul 23, 2020 6:04 pm
Forum: DITA (Editing and Publishing DITA Content)
Topic: Searching the right approach: Specialization with RELAX NG v
Replies: 7
Views: 1909

Re: Searching the right approach: Specialization with RELAX NG v

Hi folks,

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

Thanks,
Tom
by yamahito
Fri Nov 15, 2019 4:29 pm
Forum: Other Issues
Topic: Element folding not entirely persistent
Replies: 4
Views: 1132

Re: Element folding not entirely persistent

What is the maximum number of folds, out of interest?
by yamahito
Fri Aug 14, 2015 6:46 pm
Forum: DITA (Editing and Publishing DITA Content)
Topic: DITAfor publishers (d4p) & Oxygen
Replies: 7
Views: 3662

Re: DITAfor publishers (d4p) & Oxygen

Thanks, Radu!

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

Tom
by yamahito
Thu Aug 13, 2015 10:39 pm
Forum: DITA (Editing and Publishing DITA Content)
Topic: DITAfor publishers (d4p) & Oxygen
Replies: 7
Views: 3662

Re: DITAfor publishers (d4p) & Oxygen

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...
by yamahito
Fri Nov 11, 2011 10:52 pm
Forum: XSLT and FOP
Topic: What are these ???
Replies: 8
Views: 4585

Re: What are these ???

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.
by yamahito
Fri Nov 11, 2011 3:43 pm
Forum: XSLT and FOP
Topic: What are these ???
Replies: 8
Views: 4585

Re: What are these ???

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...