Comment 10 for bug 1463943

Revision history for this message
Jason Stephenson (jstephenson) wrote : Re: Non-ascii Unicode characters in messages cause client problems

Yes, that is the setting referred to in comment #8.

Ours is set to ascii, but we still get UTF-8. That is why I said "appears to do nothing."

I prefer the Koha-style approach, because it can be set per account.

If you want to merge the two or come up with something better, I'll be happy to try it.