Follow-up Comment #5, bug #17112 (project gnustep):
As I understand it, the problem is essentially that MacOS-X generates illegal
XML, and the libxml2 parser used by GNUstep-base does not accept illegal XML.
I've (so far) been unable to find any way of getting libxml2 to accept the
bad characters... which leaves two fixes I can see ...
1. do an inefficient scan for illegal characters first, replacing them with
some unusual sequence. parse the XML, and scan the parsed output for the
sequence we put in, and change it back to the illegal character. Euch!
2. use another parser to handle MacOS-X plists ... one that tolerates illegal
characters.
I've put some work into that, but it's not ready yet.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=17112>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
