Lots of XDF files have lost line breaks.

Turbosport · Post by **Turbosport** » Sat Mar 26, 2016 12:29 pm

Looks like a lot of our xdf files have been uploaded without a text/ascii mode enabled on the ftp client and so have lost their line breaks, for instance:

This one is fine:
http://www.tunerpro.net/download/bindef ... oft529.xdf

this one has lost its line breaks

http://www.tunerpro.net/download/bindef ... D1_ABA.xdf

about 30% of all files are the same by the looks of it.

Post by **Mangus** » Mon Mar 28, 2016 11:31 am

I'm seeing line breaks (/r/l) in those files just fine.

Turbosport · Post by **Turbosport** » Mon Mar 28, 2016 11:53 am

Not in chrome on both Windows 10 or MAC ??

Here is what I get in page source, so the files are in a different format:

Post by **Mangus** » Mon Mar 28, 2016 11:56 am

Those screenshots look fine to me, clearly showing that lines are broken. Also, view them in your favorite hex editor and note that they clearly have line breaks.

Turbosport · Post by **Turbosport** » Mon Mar 28, 2016 11:57 am

Mangus wrote:Those screenshots look fine to me, clearly showing that lines are broken. Also, view them in your favorite hex editor and note that they clearly have line breaks.

Sorry they are not screen shots they are page source screen shots hold on.

Turbosport · Post by **Turbosport** » Mon Mar 28, 2016 11:58 am

This is a screen shot of the link clicked directly -

By the way a guy I was helping with an xdf spotted this, I just thought I woudl follow it up so its not just me

Post by **Mangus** » Mon Mar 28, 2016 11:59 am

Open them in a hex editor. Search for 0x0d 0x0a (newline and carriage return characters). Note that they exist.

Do the files fail to open in TunerPro?

Turbosport · Post by **Turbosport** » Mon Mar 28, 2016 11:59 am

and why are my image tags not working ?

Post by **Mangus** » Mon Mar 28, 2016 12:00 pm

Turbosport wrote:This is a screen shot of the link clicked directly -

By the way a guy I was helping with an xdf spotted this, I just thought I woudl follow it up so its not just me

You're trying to view XML in a web browser. HTML is XML.

Don't do that. Open them in notepad or a plain text editor if you want to see/edit the plaintext.

Turbosport · Post by **Turbosport** » Mon Mar 28, 2016 12:03 pm

I have always just clicked the link and copied the text into a text file with an xdf extension.

Works on some now not others, so some are formatted differently.

Doesn't everyone just click the link and copy ?

Post by **Mangus** » Mon Mar 28, 2016 12:05 pm

That's a bad practice on your part. The files are fine, as you can prove yourself by opening them in a plain text editor.

Right-click, save link as.

Turbosport · Post by **Turbosport** » Mon Mar 28, 2016 12:09 pm

Mangus wrote:That's a bad practice on your part. The files are fine, as you can prove yourself by opening them in a plain text editor.

Right-click, save link as.

ok I'll update my help files, would be nice if they all behaved the same though.

Post by **Mangus** » Mon Mar 28, 2016 12:20 pm

There are two different XDF formats - old and new. New is XML. Don't expect to view raw XML in your browser without the browser trying to render it like HTML (like you see in your third screenshot). Old format will probably work just fine in your browser (like your first screenshot). That's probably the difference you're seeing.

Thanks, though.