Someone reported this issue a little while back as well. We have it logged to look into, but I don't currently have a fix. It seems to be something to do with the charset of the font that is used for the watermark. Beyond that I am not sure of a work around yet.
-justin