"William F Hammond" <hammond@c...> wrote in message 
news:i7r65a9irw.fsf@h......
> Martin Honnen <mahotrash@y...> writes:
>
>> LionelAndJen@g... wrote:
> . . .
>>> ...  UNFORTUNATELY, XSLT
>>> translates  doesn&apos;t into doesn't in the output, which then
>>> destroys my sql statement.  How do I tell my XSLT to leave well-enough
>>> alone ?  ...
> . . .
>> references in the output the XSLT processor creates then you need to
>> look at processor specific extensions to do that. Or you can look into
>> XSLT 2.0 and character maps
>> http://www.w3.org/TR/xslt20/#character-maps. Note that both ways will
>> not simply allow you to preserve entity references in the input,
>> instead you will create entity references in the output.
>
> I suppose sql language is not usually envisioned as a translation
> target in the xml world.
>
I think it quite a common requirement though.
I just do the usual sanitisation on the SQL though, replacing a single quote 
with two single quotes before running it.
If the OP is is using XSLT 2.0 it's trivial with the replace function, if 
not there are plenty of example templates online that do string replacement.

-- 

Joe Fawcett
http://joe.fawcett.name