Content Addition · Articles & templates · Created by
skidznet
accepted
What functionality is missing? What is unsatisfying with the current situation?
There's a
declined request to support emoji characters directly in articles. Actually, I'm assuming that the internal rule is to forbid anything that would require surrogates to represent in UTF-16, i.e., anything outside the BMP. This means no emoji, sure, but it also means that I can't do this (faked using Inspect Element):
Which is annoying, because it was (marginally) important that these were tally marks. I wanted to work around this by using CSS:
.tally5::after {
content: "\01D378";
}
And putting that in as something like:
[section:tally5]Days since last raid: [/section]
...but then I discovered that we can't put quotes in our CSS.
If allowing non-BMP characters in articles is something that would be allowed
but for technical constraints, then could we please have some way to encode them using their Unicode code points? There's some
cool stuff outside the BMP... Some suggestions for workarounds:
- Instead of rejecting the article content whenever it sees a non-BMP code point, maybe have the client-side portion only reject completely invalid text (i.e., unpaired surrogates, assuming UTF-16), and then replace any correctly paired surrogates with internal tags like [wa_internal_codepoint:U+1D378]?
- [char:U+1D378] or similar
- Allow quotes in CSS under a small number of whitelisted circumstances, such as "content" properties
How does this feature request address the current situation?
Authors (who are willing to get a bit weird with it) can use more characters when crafting their articles, including some characters used in uncommon / "dead" writing systems that someone might want to use in creating a world with an authentic "ancient" feel to it.
What are other uses for this feature request?
Follow up
Also alchemical symbols: https://en.wikipedia.org/wiki/Alchemical_Symbols_%28Unicode_block%29
Someone mentioned, in a comment with their vote, that there are several special characters that can be used. This is true, but the usable characters can only be those included in the BMP (Basic Multilingual Plane). i.e., I could write ∀c∈{Representable on WorldAnvil}(c∈{BMP}) in an article, because ∀ is U+2200 and ∈ is U+2208. To oversimplify in at least two ways, if you can find the "U+XXXX" ID of a character, then the ones that I'm asking to be usable on WorldAnvil are the ones with IDs that need 5 hex digits or more. i.e., "U+XXXX" characters like ₿ (U+20BF) are already fine to be used in articles, "U+XXXXX" characters like U+1F6A7 and "U+XXXXXX" characters (which I include for completeness but cannot give a usable example of) are not.
The Team's Response
hmmmmm, we do better than that - yes we can.
Current score
18/300 Votes · +3440 points