Getting <CR> on xml export from windows Server

[Devin]

When I'm exporting an xml from a script thats running on a Windows server it's adding <CR><CR> after each line.

It's not doing that when I export it local on OS X. I'm using the same XSL.

Any clue?

Thanks

 

 

[webko]

I don't believe whitespace should have any effect on an XML file, so....

Is this actually causing an issue further down the line?

[Devin]

I don't think it's going to cause an issue. But I'm more concerned with the change in behavior?

I would aspect to see the same thing regardless of platform.

[comment]

Could we see your XSLT stylesheet (preferably reduced to the minimum necessary to produce the problem)?

[Devin]

Attached is the Stylesheet.

ShippingACK.xsl

[comment]

Is it possible that the result has CRLF as the newline character (as you would expect on Windows), and you are viewing it in an application that presents this as double line spacing?

 

[Devin]

I'm sure that very possible. I've used Text Wrangler,  TextMate and Sublime and all show the same issue.

[comment]

Well, you need to view the actual code. Does TextWranger have the option to hex dump a file, like BBEdit does?

[Devin]

It does have the hex dump.. But that not telling me much.

 

Here are the two files.. One from Mac the other from windows

 

 

MacVersion.xml

Windows.xml

[comment]

The Win file you posted does have two CR and a LF characters between the lines. To be 100% sure of the source of the problem, could you perform the transformation and zip the result before doing anything else (not even opening the file)?

Edited August 26, 2016 by comment

[comment]

(after examining the original file)

The file definitely has an extra carriage return. The actual sequence is 0D 0D 0A - that is, two carriage returns followed by a line feed.

I have seen a similar problem reported a few times before. Very few times - no more than 3 or 4 such reports over the last 10 years. I suspect this happens only on some Windows systems - though it's hard to be sure because so few people use XML/XSLT export. It would be interesting to see if the problem can be reproduced on other Windows systems.

Anyway, this is clearly a bug and I suggest you report it. I am not going to suggest a workaround, since the flaw is harmless in your case.

[Devin]

Thanks Comment

I will submit for review.

 

 

[beverly]

I made an addition/update to my article about an XML with XSLT export issue with Windows:

https://filemakerhacks.com/2012/09/23/export-field-contents-as-utf-8/

Quote

Several have found that Windows FileMaker has a problem with this method (XML/XSLT) and is exporting an extra carriage return between “lines”. This is an alternative method of using One Field Several Records and Export (as tab delimited). Using the single field or variable, loop to push the ‘lines’ (returns in field) to a temporary table and Export.

then I added a demo file.

It is a *known* issue in Windows only (per TS in FM Community forum). my demo only addresses the "Export Field Contents" and not XML with other XSLT (on Windows).

beverly

[comment]

Link to Filemaker Knowledge Base:
https://support.filemaker.com/s/article/Exporting-data-as-XML-using-FileMaker-Pro-for-Windows-can-cause-an-extra-carriage-return-to-be-inserted-at-the-end-of-a-line-1503693093066?language=en_US