Your issue sounds more like an issue with international text and character encoding. Is this happening in all browsers you test with? A lot of the times this is down to a browser issue because of the way it handles the character encoding. I believe if you use Chrome you can set it to encode websites in a certain way like UTF-8 via the settings. However I believe if someone is not set up this way and adds data to QuickBase you can end up with bad characters as you are seeing. It may be more complicated than this but this is what I have found.
Looking into this in the past and going over years old posts it seems like the consensus is that part of the issue is that QuickBase uses windows-1252 encoding and not UTF-8 as you might expect it to. From reading about it before it seems like something that can sometimes work but it can go wrong very fast when using names or text with accents or characters that windows-1252 cannot handle properly.
