Apple

Hi Michael!

One of the other engineers and I did a bit of investigation.

While the XML file format is indeed UTF-8, URLs need additionally to be percent escaped, also known as RFC 2396 compliant (this is fairly common for XML files of various formats).

Here's how you can test this out.

Let's say you have a media file 'test.mov' (only use a unicode name of your choice).

1. Drag and drop that into the browser in FCP.

2. Select that clip (should be properly named 'test' )

3. Choose Menu File > Export > XML...

You'll see that re-importing that XML file will indeed work. you can compare the <pathurl> element with the ones that you've had that didn't work.

When I tried this I see that I get unreadable names (percents and then a hexcode) in the <pathurl> with something like:

"ו..."

So the workaround for your problem is to percent escape the pathurls such that they are RFC 2396 compliant. I believe the latest versions of FCP give a warning to that effect.

Regards,

Helena

On Nov 29, 2007, at 5:12 PM, Michael Miller wrote:

This is an issue for us since we're passing XML to FCP for clips to import, and the ones with Unicode names aren't being accepted, so I'm assuming these two things are related. Is there a specific reason FCP is working this way? If so, is there a workaround?

Thanks!
-Michael Miller
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (

This email sent to email@hidden

References:
	>Re: FCP file import doesn't accept Unicode? (From: Helena Ju <email@hidden>)