-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi.
I've just found some interesting things in Repligard. From the beginning: A friend of me is regularily working with Repligard and discovered, that current Repligard creates entities like &xFFFFFFC; which it uses to binary-encode (somehow...) special characters like german umlauts. For the export this works ok, though I'm not sure what sense it makes to do this binary-like. For Character Date something like UTF-8 should be the way. But anyway: The real problem comes from the import afterwards, repligard rejects the &x...; constructs with an "undefined entity" error. Now my question to the xml/expat cracks here: How does this have to work? For my personal use I will revert to a previous version for now, but we should get this cleaned up as fast as possible. Live long and prosper! Torben Nehmer - -- Torben Nehmer, Munich, Germany http://www.nathan-syntronics.de, mailto:[EMAIL PROTECTED] PGP Public Key ID on wwwkeys.(de.)pgp.net: 0x7E9DE456 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8zZEBJPh4Kn6d5FYRAvJ6AKD7N7FcRT/9REm7ZqRMGNQayL36xQCfXuNx x/NjSr4qTfC9CdF9yD6yka4= =jr5x -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
