> Get a real editor 8)
>
> It's the old story of ANSI / DOS Format. Some editors don't understand a single
> 0xa etc., others do.
> I prefer TextPad (and notepad for smaller stuff) and both work fine with the
> current linefeed/newline commands.
>
I would expect Clrmame Pro to output both the string format and the seperator format the same. But if you specify &#10 in the string format, it adds an extra &#13 character before the &#10 character in the generated file.

Place the following tests into setformat01.xml:

<SetFormat>
<Format name="Test 1 &#13&#10" pre="" post="" separator="&#13;&#10;" string="Test 1&#13;&#10;"/>
<Format name="Test 2 &#10" pre="" post="" separator="&#13;&#10;" string="Test 2&#10;"/>
</SetFormat>

Scan a collection in Clrmame Pro, and use the export set list to output both formats. Then use a hex editor to open both files.

The Test 1 generated file looks like:

54 65 73 74 20 31 0d 0d 0a 0d 0a

when it should have been generated as:

54 65 73 74 20 31 0d 0a 0d 0a

The Test 2 generated file looks like:

54 65 73 74 20 32 0d 0a 0d 0a

when it should have been generated as:

54 65 73 74 20 32 0a 0d 0a

It's just strange that the 'separator' gets output correctly, while the 'string' contains an extra &#13 in these two tests.