When testing my app and its command-line helper in Mac OS 10.5 on a PowerPC machine, I see these annoying pairs of entries in the Console Log:
sdef error: Operation could not be completed. (NSXMLParserErrorDomain error 1549.) line number: 2 I'm not sure whether or not they're related to the problem I'm trying to fix. The helper does send AppleScript messages to my app. A web search shows that these messages are quite common, and that possibly they only occur in Mac OS 10.5 on PowerPC. I looked at lines 1 and 2 in my app's .sdef file (wonderfully created by Shadow Labs' "Sdef Editor" app), and find them to be exactly as specified in Apple's Cocoa Scripting Guide > Preparing a Scripting Definition File… <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE dictionary SYSTEM "file://localhost/System/Library/DTDs/sdef.dtd"> Then I looked into the packages of several Apple apps (Safari, Mail, etc.) on this old Mac, and found that, instead of .sdef files, these apps all still use the old .scriptTerminology and .scriptSuite files, which were depracated in Mac OS 10.4. Eeek. Well, these Console messages are not *that* annoying. Does anyone know how to stop these messages? Or can at least confirm that they are false alarms? _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
