That snippet my answer is referring broke things indeed.
For example setting temperature of Discourse AI personas:
So, AI helped me poorly 
1 like
Would watched words > replace not work for this?
No. I tried. We can use © or µ directly on posts, but not using watched word.
1 like
Strange, it seems to work saw for me:
Raw:
(c) © <casually uses older test topics instead of making a new one>
1 like
Really 
Good to know, I have to dig deeper then what is the issue in my end.
1 like
Maybe worth using the unicode character instead of the © HTML entity. (I suspect that’s what @Firepup650 did, based on the watched-word config screenshot?)
I’m sure there’s a proper way to insert… but I tend to just copy-paste it from somewhere else (e.g. google ‘unicode copyright’) 
1 like
I see. And all of that hazzle because one american lawyer needed to use (c) as a list separator?
Well. All that hazzle comes actually from fact that IT side is really far fay away from other galaxy, where was no working standards 
But I’m bit curious, even the topic got its answer. I really would like to understand this.
Why the core of Discourse can’t use HTML entities via watched words, but a component like Topic List Previews can show those?
Probably, I just pasted the one off of gboard.
1 like
This starts to be quite funny, actually.
First I wrote one liner using HTML entities © as © and µg (because of limitation made by Apple) for µg.
Then I copypasted those two and made two watched words:
- (c) → ©
- myyg → µg
Problem solved[1]. Now I got copyright sign without a plugin and micro-sign without overpriced keyboard.
Thanks!
but guys, seriously; now is year 2024
↩︎
3 likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.