I'm relatively new to XML export from FMP, but I'm not able to control well the 0D or 0A characters I insert in the [text] output. When I request 0D;, I'll get the one 0D output as expected. When I request 0A, I'll get 3 characters output (0D-0D-0A). This is causing problems (too many blank lines) when I import the resulting [tagged] text into InDesign CS. [The 0A is important for one section to hold separate lines of a paragraph together as a unit in InDesign.]

I'm using WinXP, FMP 6.0v4.

With MacX everything works as expected (6.0v4 FMP).

[note: when I say 0D or 0A I mean an entity as #x0D or #x0A]

Any suggestions?

When do you insert the characters? Before or after the XML export?

If it's after, you should check your editor settings, e.g. if it stores the edited file in Unix, Mac, or DOS format.

The character insertion is during the transformation from FMP to a text file via my XSL. I then read the text file as hex in TextEdit. The workflow is to transform the FMP to text output for InDesign. InDesign plunks in a paragraph break when it encounters a Od and a forced line break when it encounters a 0a. So I see extra paragraph breaks after import when I use a Windows-only platform workflow.

On the Mac platform the text file that results from FMP transformed has single 0d and single 0a characters where I expect them (per my XSL file) as observed via a hex dump using BBedit. No extra 0d's exist as they do with Windows.

I've attached a sample of my XSL code, really excerpts of the overall file I'm using to export as InDesign tagged text.

Excerpt_XSL.txt

Hmmm. What data is in fmp:COL[16] ?

How do you control the number of recursions, what's the exit criterion?

You could export once the XML tree with the XSLT stylesheet and check the contents of your field fmp:COL[16]. I guess that you may have some carriage returns in it.

Could you also check the <xsl:output ... line in your XSLT?