Apple

Hey Bruce!

I'm not exactly sure I understand the question but I think the goal to get a string back from the pathurl node without any of the %-escaped entities.

Here's a snippet of code that may help (NS first, then CF-equivalents)

//if you get the node (firstPathurlXmlNode):

//you can get the string value of that node, and make a NSURL with it:

NSString* firstPathString = [firstPathurlXmlNode stringValue];

NSURL * mediaurl = [NSURL URLWithString: firstPathString];

//you can remove the %-escaping:

NSString* non_escapedPath = [firstPathString stringByReplacingPercentEscapesUsingEncoding:NSUTF8StringEncoding];

//=============

//you can get the string value of that node, and make a NSURL with it:

CFStringRef cfFirstPathString = CFXMLNodeGetString(firstPathurlXmlNode);

CFURLRef cfMediaurl = CFURLCreateWithString(kCFAllocatorDefault, cfFirstPathString, NULL);

//you can remove the %-escaping:

CFStringRef cfNon_escapedPath = CFURLCreateStringByReplacingPercentEscapes(kCFAllocatorDefault, cfFirstPathString, CFSTR(""));

Please let me know if the question was something else, and I'll see if I can help.

Cheers!

Helena

On Aug 18, 2008, at 12:16 PM, Bruce Sharpe wrote:

I am running into a conflict between URL encoding and XML node values.

I retrieve my project as XML. It has nodes like this:
<pathurl>file://localhost/Broken Fists/clip1</pathurl>
where the space in "Broken Fists" is URL encoded as .

If I try to represent that node as a string via stringValue or XMLString it comes out as
<pathurl>file://localhost/Broken 0.000000ists/clip1</pathurl>
apparently because it interpreted F as a C string format code.

This is messing me up because NSLog and other functions report errors like
[NSMethodSignature appendCharacters:length:]: unrecognized selector sent to instance 0x16b416b0

Am I doing something wrong, or is there a workaround?

Bruce
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

References:
	>URL encoding in XML node values causes trouble (From: "Bruce Sharpe" <email@hidden>)
	>Re: URL encoding in XML node values causes trouble (From: Helena Ju <email@hidden>)