On Mar 8, 2004, at 3:12 PM, [EMAIL PROTECTED] wrote:

Yes, I was confused by the fact you said and XML to XML tranformation
worked correctly, but XML to HTML did not.  Clearly, they must have
beeen
with different data sets, so the comparison was not relevant.

Well, *we* didn't think they were different data sets, but the output xml went through an unintended change between transformations.

I'm not disputing that, but when you make a claim in a posting, you should
be very careful that claim is true. Otherwise, you're misleading people,
and it's difficult for them to respond reasonably.

Not to continue this thread for any longer than necessary (but I will, apparently), but Keith's response was right on the mark, and he instantly knew what I was (or could be) doing, so I certainly don't think everyone was 'misled' (I feel that 'misleading people' is a poor choice of phrasing which seems to indicate some kind of premeditation which certainly wasn't the case). While I realize that we weren't doing what we thought we were, you can't reasonably expect everyone to know what they're doing wrong, otherwise they wouldn't be asking the question. If I knew copy-paste screwed things up on windows, I wouldn't have even needed to ask the question in the first place, since I would have avoided the very problem. The other platform I'd been working on (MacOS X) had a copy-paste which worked quite well with unicode text, and I didn't know that windows 2000 didn't work with the same accuracy, and it's not like there's an annoying paper clip that pops up to tell me that 'Hey, I notice you're trying to copy UTF-8 text!'.


Can you send me a private emai, with a copy of that document attached? I'd
like to see why the parser accepts it if it has invalid UTF-8 byte
sequences. That's a very big problem.

I'm not sure if we still have the bad XML file, but we can probably recreate it. We're currently in the process of dumping our existing toolset on windows and finding new tools (since the old one's clearly didn't support unicode all that well), so it might be a day or so until we get back to recreate the problem.


--
Nick




Reply via email to