I should probably just leave my layout as is...
Monday, August 24th, 2020 18:51So, was once again looking up journal layouts, because I can't leave well enough alone, even though I'm honestly pretty happy with my current layout and probably wouldn't find one that meets my desires any better than what I already have, but...eh, I'm one of those people who just can't stop tinkering, I guess.
Anyway, in the process, I found out that due to a coding change last year, the @ symbol is now interpreted as a call instead of a unicode character. So if one types, for example, "@username", it is rendered into
username. And if one types "@username.site" (such as @PBS.twitter), other domain usernames can also be called (such as
PBS).
Thus, in order to get the @ to render properly in something like the (@_@) kaomoji, you need to escape the autocoding with "\", aka type "
_@).
My point is, if you look through my old entries and find weird moments where "
_@" pops up, it's because the old code would have rendered it as "@_@". So just...replace it mentally or something.
Anyway, in the process, I found out that due to a coding change last year, the @ symbol is now interpreted as a call instead of a unicode character. So if one types, for example, "@username", it is rendered into
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Thus, in order to get the @ to render properly in something like the (@_@) kaomoji, you need to escape the autocoding with "\", aka type "
(\@_@)
" to get (@_@), otherwise it will render into (![[profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
My point is, if you look through my old entries and find weird moments where "
![[profile]](https://www.dreamwidth.org/img/silk/identity/user.png)