I'd argument that, as UTF-8 is de-facto a web standard, using such characters is perfectly fine and much less complex and error prone than doing any of that with JS/CSS extensions. It's a nice hack, have to remember that. 🙂
@xpac in SPL " (Unicode 0022) and “ (Unicode 201C) work differently second one may fail. So while I am really amazed with the way this works and even applies Table Color based on Value from UI, I am not sure whether this will work with all the functionalities like Splunk Dashboard Migration, Copy, Conversion to HTML, PDF Export etc. Splunk Team should probably test this out!
The fact that this approach is unique and surfaced for the first time, I have already up voted the question and bookmarked it 🙂
@stanwin Thanks for sharing. You might have to let us know whether this works for you in all the cases.
Yeah, the different ", “ are the devil's work and should be avoided (looking at you, MS Word!).
We should however do those UTF-8 things more often, test where Splunk breaks and then get it fixed, because, standards! ;D