Does the tool need a UTF definition file?
UTF-8 / UTF-16. e.g. South America exposure with special char - sometime UTF-16 is not enough to handle e.g. Chinese/Mandarin char.
Standard behaviour should be to pass data through with now change, if not recognised.
Does the tool need a UTF definition file?
UTF-8 / UTF-16. e.g. South America exposure with special char - sometime UTF-16 is not enough to handle e.g. Chinese/Mandarin char.
Standard behaviour should be to pass data through with now change, if not recognised.