I ran this test on macOS. Gary
On Thu, Jul 31, 2025, 19:22 Joseph Kesselman <[email protected]> wrote: > I wouldn't expect CR (ASCII 13) to be escaped unless (maybe) you were > producing CRLF line breaks (as for MS) but serializing them for an LF-only > platform such as Linux. > > Strong suggestion: compare with what main line xalan does in the same > configuration on the same platform, and make sure you are aligned with > that, or can cite a very explicit reason that you shouldn't be from the > xslt 3.0 documentation. Behavior should not change except where the new > recommendation requires it to change, for minimal surprise. > > -- > /_ Joe Kesselman (he/him/his) > -/ _) My Alexa skill for New Music/New Sounds fans: > / https://www.amazon.com/dp/B09WJ3H657/ > > Caveat: Opinionated old geezer with overcompensated writer's block. May > be redundant, verbose, prolix, sesquipedalian, didactic, officious, or > redundant. > ------------------------------ > *From:* Gary Gregory <[email protected]> > *Sent:* Thursday, July 31, 2025 7:01:17 PM > *To:* [email protected] <[email protected]> > *Subject:* Re: xalan-j releases discussion > > On Wed, Jul 30, 2025 at 12:17 PM Mukul Gandhi <[email protected]> > wrote: > > Hi Gary, > > On Wed, Jul 30, 2025 at 5:45 PM Gary Gregory <[email protected]> > wrote: > > > I would be grateful if you could provide these command lines to save > time. > > Your Maven build attempt has resulted in three test failures. > > I request you to please follow the below mentioned steps, to run one > of the tests that is failing for you. > > 1) Run command mvn clean install -DskipTests > This shall produce file xalan-java-3.0.1.jar within Maven's target folder > > 2) Create folder "xalan_3.0.1" for this testing somewhere within file > system (I've created this on my local, at location D:\xalan_3.0.1) > > Copy file xalan-java-3.0.1.jar to folder "xalan_3.0.1" > > Copy following files as well (from folder xalan-j_xslt3.0_mvn\libs) to > folder "xalan_3.0.1" > > > I pulled the latest: > > git log -1 > commit 1ef412d3a7492c0c2e615b6e3a3c7371fdb7f7ac (HEAD -> > xalan-j_xslt3.0_mvn, origin/xalan-j_xslt3.0_mvn) > > I'm not sure what the "xalan-j_xslt3.0_mvn" folder is, so I'll assume > that's your local folder name. I have: > > find . -name "*.jar" > > ./target/xalan-java-3.0.1.jar > ./libs/edu/princeton/cs/cup_runtime/1.0/cup_runtime-1.0.jar > ./libs/edu/princeton/cs/java_cup/1.0/java_cup-1.0.jar > ./libs/org/apache/commons/bsf/1.0/bsf-1.0.jar > ./libs/org/apache/xerces/xercesImpl/2.12.3/xercesImpl-2.12.3.jar > ./libs/org/apache/xerces/xml-apis/1.4.02/xml-apis-1.4.02.jar > ./libs/org/apache/xsl/xpath31_types/1.0/xpath31_types-1.0.jar > ./libs/JLex/JLex/1.0/jlex-1.0.jar > > So I'll copy the 3 files below from these various folders. > > > > xpath31_types-1.0.jar > xercesImpl-2.12.3.jar > xml-apis-1.4.02.jar > > Please navigate to folder > > D:\eclipseWorkspaces\xalanj\xalan-j_xslt3.0_mvn\src\test\resources\fn_transform > (wherever this folder is on your local) > > Please run following command, > > > D:\eclipseWorkspaces\xalanj\xalan-j_xslt3.0_mvn\src\test\resources\fn_transform>d:\jdk-1.8\bin\java > -Djava.endorsed.dirs=D:\xalan_3.0.1 org.apache.xalan.xslt.Process -in > test9.xsl -xsl test9.xsl > > This should produce following expected result > > <result><?xml version="1.0" encoding="UTF-8"?><details> > <a>1</a> > <b>2</b> > <c>3</c> > <d>4</d> > <e>5</e> > <f>6</f> > <g>7</g> > </details> > </result> > > > Then I get: > > java -Djava.endorsed.dirs=/Users/garygregory/tmp/xalan_3.0.1/ > org.apache.xalan.xslt.Process -in test9.xsl -xsl test9.xsl > <result><?xml version="1.0" encoding="UTF-8"?><details> > <a>1</a> > <b>2</b> > <c>3</c> > <d>4</d> > <e>5</e> > <f>6</f> > <g>7</g> > </details> > </result> > > That doesn't look like what you have above. > > Gary > > > > Please let us know whether you're getting these results, or any other > result. > > > -- > Regards, > Mukul Gandhi > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
