> It looks like this might be a feature, handling how the > replace function deals with a non-match. Ah, because it's a pathological case; yes, that's unavoidable. Xerces is broken and returns the input string when it fails to find a match, and the only way to detect that case was to guard it. -- Scott