Latest revision |
Your text |
Line 18: |
Line 18: |
| I'm having trouble viewing this article. Redirect from 259 works, but direct URL gives out "No input file specified.". 15:52, 13 December 2020 (UTC) | | I'm having trouble viewing this article. Redirect from 259 works, but direct URL gives out "No input file specified.". 15:52, 13 December 2020 (UTC) |
| | | |
− | As of March 11, 2024, an issue occurs with the title text and after the word "with" it displays "clich$eacute;s." Possibly, an error with the code displaying the acute above the e. Is this a bug on my end (chrome) or is it an issue with the comic itself, and should I add it to the trivia? {{unsigned ip|204.113.154.25}} 18:57, 11 March 2024 (UTC) | + | As of March 11, 2024, an issue occurs with the title text and after the word "with" it displays "clich$eacute;s." Possibly, an error with the code displaying the acute above the e. Is this a bug on my end (chrome) or is it an issue with the comic itself, and should I add it to the trivia? |
− | :Indeed, checking myself (on several browsers, just in case it ''was'' differently served according to the agent requesting), I found that it was because it was <code>title="It&<!-- nowiki tag doesn't properly disable character references, apparently, so forcing additional ampersand encoding all over here, for strictly illustrative purposesñ-->#39;s like they say, you gotta fight fire with clich&amp;eacute;s."</code>. What should have been <code>&eacute;</code>, to give an "é", was doubly-escaped to "ampersand the ampersand". (Incidentally, googling "xkcd 259" gives the result's page/link title (for the xkcd match, but not explainxkcd) as "Clichd", so clearly Google just decided to junk the funny characted in the title-tag of the page/whatever it uses.)
| |
− | :I suppose we ought to check if other (previously properly given) title texts with simple ampersanding have ''also'' become double-ampersanded. This might reveal an improper export/transfer from one system to another (like you used to see with things like jobsite reaggregators, "Salary: &amp;amp;pound;30,000 p/a", often ironicly for positions like website roles...). But I suspect that it's entirely unintentional and unwanted. And is quite easy to fix, if that's what happened, so maybe Randall just needs a nudge to de-escape (by one level) any affected things in his backend database. [[Special:Contributions/172.69.194.182|172.69.194.182]] 02:16, 12 March 2024 (UTC)
| |
− | :...checked around. Disappointingly, nothing that has the same 'accidentally re-encodable" structure. Of the ones with (non-apostrophe, non-quote) 'extended characters', I've only seen them appearing straight. Like [[2606: Weird Unicode Math Symbols]] having its way-off-ASCII character as literal, totally unencoded! Maybe someone else can find another similar treatment, though. [[Special:Contributions/172.71.178.157|172.71.178.157]] 02:40, 12 March 2024 (UTC)
| |