On 19-Feb-09, at 6:08 PM, Fabian Rueger wrote:
Wow, this is amazing. Searching the RB NUG reveals 11 emails not
from this thread that uncovered the same issue, ... first seven (!)
years ago and then at least three times since, last before me today
just this January. Nobody bothered to fix, further investigate, or
seems to have filed a bug report, since the issue seems uninterfering.
RB since at least version 5.x (!) on OS X seems to not properly
store its Filetypes in UTF8 format but ASCII, which throws a couple
of OS 10 XML parser errors into the Console log everytime you run RB
using filetypes. This, from what I gather, is the cause. I guess end
users never notice, but internally it's ugly, filling user consoles
up with our apps' error entries, portraying us as if we don't know
how to parse properly into UTF8. Do we have no pride?
First discovered in 2002, and still needs fixing 7 years later...
Wow. Now I'll stick to this RB NUG tradition myself. Not a word from
me! This one shall go unreported until such time as the gods of
Austin grace it with their almighty attention. Does no one else ever
notice this stuff in the Console?
CFPropertyListCreateFromXMLData(): plist parse failed; the data is
not proper UTF-8. The file name for this data could be:
(UNKNOWN)
If no one reports it or gives the steps required to reproduce this
error then the likelihood it will get looked at or fixed is very
nearly zero
I run RB all day long, often with the console open and I will confess
to never seeing this particular message
I'd love to know what you're doing that I'm not that makes this show
up for you
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|