I hope to automate it all (cf the Scripts directory I just added to P5-Pure) ... and then spend ages picking up the pieces, as per usual. So far today I have identified two show stoppers a) the content model of macro.anyXML b) in impure ODDs DTD generation required massive numbers of redundant rng:group elements. I am hoping that these are no longer required in pure odd, since turning them all blindly into <sequence> causes various things to break. If someone else would like to ponder what to do about (a) while I attack (b) I'd be grateful! L On 08/08/15 14:27, Syd Bauman wrote:
I think moving on to phase 2 now (in the P5-Pure branch, of course) is a reasonable plan. I would tag the existing P5-Pure branch before delving in to such a huge task, though.
How much of phase 2 do you plan to automate, and how much to do by hand? I'd be happy to chip in on either approach.
This means, of course, that this branch cannot be merged with the trunk until there has been a new stylesheet release and we have moved over to using it on our jinxes. Which is a pain, but not too great a one. In the circs, I think I might proceed to phase 2 of operation purity: namely, switching the content models in P5 to use pure ODD. It ought to All Just Work, but...