Closed GenWilhelm closed 3 years ago
Damn, how did you figure that out? I would have never through about looking at that before.
This is what I meant by adding the unicode characters in at runtime. Once this is live, the objectives data can be updated to use all caps for keywords, solving the JSON encoding issue, without affecting the appearance to the end user.
As a FYI for myself in the future, do you just copy the text straight from some file that has these characters in them? I was wondering where your source is it of these secondary objectives?
But, I will review this really fast. I will admit, I am very weak when it comes to unicode details.
I was previously using an online tool, just for convenience, but that won't be necessary any more. https://manytools.org/facebook-twitter/smallcaps-text-tool/
Three or more consecutive capital letters in an objective description will be interpreted as a keyword and encoded into small caps.
Closes #5