site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com I assume this person on FCP 6.x ? -eryk Hi List, The .dtd file would have also found the problem for me. Greg _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... There were some cases where illegal characters could get into the XML output causing it to not reimport. So far as I am aware these issues were fixed in FCP 7. In some cases the offending characters are control characters. If you are familiar with the command line, the easiest way to find this is with an old-fashioned editor like 'vi'. (Most GUI editors tend to be entirely too helpful and do not display such characters at all.) An alternative is to use another command line tool 'xmllint' and see if it complains about anything. I've got a customer with a strange situation. He exports an XML file of his sequence, but the XML won't reimport back into FCP: you get the critical error and general error dialogs. Could this be caused by a corrupt sequence or a problematic clip in the sequence? Greg. Eryk, you are exactly right. The problem was FCP was exporting some bad characters in the lognote field that weren't escaped. Text Edit didn't show the characters, but TextMate did. For fellow XMLers, here's a tip I learned last week. If you open an XML file in Firefox or Camino, it will tell you if it's valid and show you exactly where the problem is. It's like having your own validator. This email sent to site_archiver@lists.apple.com