Yes, we know. It’s an old ms word smart character or “curly quotes” problem that’s plagued us before. Don’t know why it’s popping up again. I’ve tackled this previously myself on other projects and it’s difficult to solve. Hoping John gets it sorted out soon.
It happened to us. Turned out that when we updated the jdbc driver for the database, they changed the default translation for Word high order characters. Turns out there was a new flag we had to set in the context uri.