----- Original Message ----- From: "Conor MacNeill" <[EMAIL PROTECTED]>
> Ummm. I wasn't really hoping for a "great deal of modification" in the > beta > :-) Oh well, we will now require a second beta, I guess. "Great deal" in this case is mostly considered as "bugfixconsolidation" to me... It would have been next to impossible to let it work correctly w/ Xalan 2.0-Xalan2.2 and I feel it was easier to redo everything from scratch and enforcing the syntax by passing File object rather than "maybe" systemids and I could not pass file object to the transformer because JAXP transform the file into file:// + path on Unix and file:/// + path on Windows and Xalan was testing for file:/// in some places..and not in other. It is currently under cleaning in the xalan code. If you feel it is dangerous I'm fine with doing this in the main branch instead but this is also why I did the testcases for all xsltlaison...it plays with xml entities, xsl include and xalan redirect and I added a small one for basic encoding consideration. (btw, if you have a Unix box it would be cool to check for the testcases) > Another thing, it is easier to manage the branches if you don't make the > same changes on both the 1.4 branch and the main branch. CVS can > sometimes > see the concurrent modifications as conflicts. If you need to have code > in > the next beta, add it to the 1.4 branch and when I cut the next beta I > will > merge it into the main branch. I did not do the changes in the main branch on purpose (unless I did something wrong, in this case I have no excuses), it had more sense to me to do the merge once the 1.4 branch is terminated otherwise it is difficult to figure out the changes. Stephane
