Comment by tpmoney
3 days ago
Calling attention to it kind of makes it worse. If they didn’t have that note anyone who saw and was bothered could chalk it up to them not caring or not knowing like so many other publications would be. But by dropping this statement at the end, they’re saying they know, they’re claiming they care, they just don’t care enough to actually fix their systems to handle apparently anything other than ascii text despite the fact that even if that was all they could store in their database HTML has support for Unicode escape sequences and they could use that.
So it gets a little weirder too because here[1] is an article on their site where they are very clearly using a diacritical character in the main body of the text for "Hernándas" which means whatever backend they're using must support something other than plain ascii. If it was Latin-1 or a similar code page that might explain why they couldn't use the "macron" or "overline" diacritic characters directly, but it doesn't explain why they couldn't just use the HTML escape sequences then, since they can clearly inject them like they did between "Kau Desert" in the Hawaii article.
And while it doesn't say what their backend can do, certainly if you edit in the ̅ escape sequence after the U into the page HTML it seems work, so nothing in the page content itself would make them unable to display the characters. Just makes their note all the more strange.
[1]: https://www.sfgate.com/sports/article/alcantara-gets-another...