On Nov 23, 2008, at 7:41 PM, Keith Blount wrote:
Thanks for trying... It's a shame... I have an OPML importer (no
export) working based on old code I had found based on CFXMLTreeRef,
but I was hoping to write an importer/exporter based on
NSXMLDocument, and this is the one sticking point - everything else
has been trivial with the NSXMLDocument class. Is this just an
oddity with the OPML specs, that they allow such whitespace in an
attributes when XML in general doesn't? Or is it just a limitation
of NSXMLNode attributes? And does this mean that there is just no
way of doing it using NSXMLDocument and that I'll have to look for a
different solution altogether?
Anyway, thanks for your help - much appreciated.
All the best,
Keith
The OPML specs do not specifically allow or disallow such whitespace.
http://www.opml.org/spec
The specs are pretty short and vague. However, it is clear that <opml>
is an XML element. Thus, anything that applies to XML applies to OPML.
If people have taken the whitespace in the attribute values to be
significant, it's most likely because they're ignorant of the
specifications. Of course, ignorance of the specifications is an
extremely common situation on the internet, as anyone who writes a
parser comes to realize. :-)
-Jeff
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
