I'm developing a FileMaker app that generates an XML file, and I've been
using TextWrangler 4.0.1 to inspect the generated file.

Something changed during the past several days, and TextWrangler is now
reporting an error when I open the generated file:

*Incorrectly formed UTF-8*

The UTF-8 file "filename.xml" is damaged for incorrectly formed; please
proceed with caution.

If dismiss the error, save the file under a new name, and open the cloned
file, there's no error.  Comparing the cloned file to the generated file
reports there's no difference.

TextWrangler's footer status bar shows the two files have the same size.
 But Get Info on the two files shows that the cloned file is two bytes
larger than the original generated file.

How can I determine why TextWrangler is unhappy with my generated XML file?

-- Ward

Hi Ward,

usually TextWrangler will mark errors in UTF-8 with a character of " ", you can actually search for it as \x{fffd}.
If you don't find anything there try to open your different files as ISO Latin 1 and compare them, there you should be able to see the difference.

Best
Thomas

Am 08.10.2012 um 19:24 schrieb Ward Clark:

Thanks, Thomas, for the key to solving my UTF-8 problem:

Search didn't locate the single accented French character in my 6120-line
XML file.  But eventually I isolated it by reducing the input data
processed by my FileMaker app (a classic binary search).

-- Ward