User talk:GentlemensDame883

The slash actually is missing from our FSN page, though? Or are there plans to mass-rename it to include the slash and bring in line with Wikipedia's naming?

The slash was removed (by @Looney Toons, if I recall correctly) because of how MediaWiki handles subpages.

If it wasn't for the fact that there are other Fates (the Fates from Classical Mythology, Fate Averruncus from Negima, Fate Testarossa from Lyrical Nanoha, the titular Doctor Fate, and so on), I'd suggest turning "Fate" into a franchise page for Fate/stay night, Fate/kaleid liner Prisma Illya, Fate/Zero, Fate/hollow ataraxia, Fate/Grand Order, and so on - which would let us restore the slash to the FSN pagename.

Since the other Fates do exist, Fate needs to remain a disambiguation page and we can't use it as a franchise page. I think.

Yeah, as I recall we went back and forth on that a few times some years back -- enough so that I forgot which was the actual page and which was the redirect (hence my change and immediate revert).

We experimented with using the DISPLAYTITLE magic word to make the page name look right, but it didn't work, because the slash is part of namespacing and DISPLAYNAME basically won't misrepresent the page by making it look like it's located somewhere else than it actually is. Right now the way we have things, while unsatisfying, is probably the best solution within the context of the wiki and its focus.

Thanks for clearing that up for me.

Thanks for the spoiler warning insert. I have to admit I've never read Worm -- and every Worm crossover I've read starts with Taylor getting killed, so I wasn't aware it was any kind of twist. In fact, I'm wondering if it's on the verge of turning into It Was His Sled, given how casually it's tossed around in stories like these.

Ah. I'm sorry if the note in the change came across too harshly. Taylor's eventual fate (it's more complicated than just getting killed), as well as the identity of the final villain, are big spoilers for canon, but I guess a large part of the fandom - particularly the fanfiction segment - is indeed awfully blasé about them.

I got that too, it appears to be a backend issue on Miraheze's end, not local breakage. If it does not clear up by tomorrow, let me know and I'll file a report with their staff.

Okay, thanks.

Found what was causing the error, refresh any pages that have issues to clear the cache if need be to flush them of issues.

I'm still seeing it on the Weathering with You page even when I use Incognito Mode, I'm afraid.

You may need to purge your web browser cache on your end, you could be seeing earlier saved remnants of the problem from the cache.

Okay, it seems to be gone for now.

In some cases, like pluralizing links, it's completely unnecessary. For example: [[Trope]]s is a perfectly valid and legal construction (and we recommend it in several help pages), and produces a link like this: Tropes. Putting a spurious <nowiki/> between the link and the "s" does absolutely nothing but make you type more and require an admin to edit the page to remove it.

Similarly, don't use the nowiki markup to "escape" an apostrophe when you want to keep it from inadvertently causing a boldface markup. We have a template, {{'}}, which does that in fewer characters: ''[[Titanic]]''{{'}}s script, which produces: Titanic‍'‍s script.

We strongly request that you stop using the nowiki markup.

-- Looney Toons, admin

CC: @GentlemensDame883, @Labster, @Robkelk, @QuestionableSanity, @Derivative, @SelfCloak, @GethN7

I just noticed that we didn't actually say this anywhere in the Style Guide, so this isn't something that we would penalize you for doing up until now.

I've just added this to the Style Guide, under "Italics, Boldface, and Other Emphasis", so... now it's part of the wiki's guidelines. It is faster to use the template, after all - it's four keystrokes instead of nine.

-- robkelk, admin

Five, but who's counting but obsessive-compulsives like me? <grin> Thanks for doing that, Rob.

Well, I wasn't counting the apostrophe itself... so five keystrokes instead of ten. 😀

Sorry, I don't understand what's going on. I do most of my editing in visual mode and had no idea that whatever this is was going on underneath the hood. It's definitely not something that I'm going to all the trouble to type out manually.

Ah, that's different. We'd already noticed that the visual editor does some pretty stupid stuff to the underlying page source; we didn't know this was one of things it was doing. <sigh>

That said, thank you for pointing this out to me. I will strive to avoid repeating this mistake in future.