I don't think so, and I'm not sure whether you could use an APPLY operator with a list of mappings applied to a supplied string.

But I think a user-defined replace function is not too hard to code, unless the replace has to respect a particular order (which could also be done via sorting the entries accordningly).

A very simple starting point:

drop table if exists LT_Replace;
create local temporary table LT_Replace (strSource nvarchar(10) primary key, strTarget nvarchar(10) unique) not transactional;
-- Just the first 10 entries from the list above (just in swapped order)
insert LT_Replace values ('"', '":'),('&', '&:'),('''', '&apos:'), ('<', '<:'), ('>', '>:'), (' ', ' :'), ('¡', '¡:'), ('¢', '¢:'),('£', '£:'), ('¤', '¤:');
select * from LT_Replace order by 1;

create function fnReplace(varTest long nvarchar) returns long nvarchar
begin
   declare strReplaced long nvarchar = varTest;
   for forCrs as crs cursor for
      select strSource, strTarget from LT_Replace
   do
      set strReplaced = replace(strReplaced, strSource, strTarget);
   end for;
   return strReplaced;
end;

create variable varTest long nvarchar =
   'This is some random string with some <tags> & "quoted text", worth < £ 1,00 .';
select varTest, fnReplace(varTest);

Needless to say, I don't know why the HTML encodings in your code are shown as encodings whereas mine are not...

Thanks for the example.

I starterd working on it, but due to the fact of the current collation used in the database the string below

'°C Infineum P6072C - Do not reheat ªabove: 65 °C - ZINC PRODUCT ! ! !
'

Instead of parsing only the 'ª' in the string it parses all 'a' in the string.

I created a new database with UTF8BIN collation and with respect accents and then it is working.

However I have no idea what could be the effect of changing the collation of the database. Is there a way to do it runtime in the function?

Sorry, I had not thought of collation issues. Note, there's the BYTE_REPLACE() function which does work on binary characters (ignoring collations) and therefore should work as expected here.

You have to rebuild a database to change its collation, so that's quite a step. If you only need different collation behaviour now and then, you can use "collation-tailoring" for comparisons, see this FAQ with a sample using the COMPARE function in the question. That's how we do comparions when the required semantics w.r.t. to case/accents/sort order differ from our database collation...

Alternatively, if your function does return XML encoded in UTF8, you could already use NCHARs within your function to prepare your strings and use the default NCHAR collation - if that has different collation settings. (IIRC, the default NCHAR collation still ignores case and accents...)