Talk:Unsupported titles/`amp`amp;

"&" displaying as "&"

@Theknightwho: In two of the four quotations, “&” changes to “&” instead of “&”. I do not know why or how to fix this. J3133 (talk) 16:57, 10 May 2023 (UTC)

@J3133 Fixed. When decoding HTML entities like &, it iterates over each one in turn, converting it into the expected form. However, it was decoding the whole string on each iteration, instead of just the entity in question. That meant if there were two entities in the string they would get double-decoded (i.e. & would become & and then &). Three times and it would resolve & and so on. That's why it was only causing issues for two of the quotes, as the other two only have one entity.

It now works as expected. Theknightwho (talk) 17:44, 10 May 2023 (UTC)

@Theknightwho this is broken again. This, that and the other (talk) 01:09, 8 November 2023 (UTC)

@This, that and the other Fixed. Theknightwho (talk) 01:20, 8 November 2023 (UTC)

Is this dictionary-worthy?

There are lots of other possibilities in XML and elsewhere, e.g. < > (less than, greater than). Hardly "words", nor really human language. Equinox ◑ 14:54, 15 May 2023 (UTC)

It's certainly an unconventional dictionary entry – not part of a lexicon in the usual sense. The current definition ("failed rendering") is something like a typo or scanno, and I wouldn't want us to start making entries for scannos. —Granger (talk · contribs) 15:34, 15 May 2023 (UTC)

@Mx. Granger: We also have ¯_(ツ)_/¯ as a “failed rendering”. J3133 (talk) 19:02, 15 May 2023 (UTC)