Should it be replaced with anything specific or just deleted?
Huh. Why?
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard FeynmanDeleted. If the information can be worked into the description, that's fine; otherwise don't mess with it.
My assumption is that it doesn't contain anything that can't be included in the description in text format. Myself, I think it kludges up the description space.
edited 17th Aug '13 5:35:35 PM by Willbyr
Apropos table markup again: Just experimented in the sandbox with various parameters and found that the standard tables always look the same way, no matter how you choose the params, while the other markup allows for tables of different width, borders, border colors etc. Just so you know.
Get rid of the walled gardenKilled that genre box that was brought up on Franchise.Halo, and my sandbox shows what the AATAFOVS boxes look like
Those tables also show borders in the forum, unlike the long bar ones.
I've found the use of [[animated]] explained in an old ATT query (right near the top). It gave an icon in the top corner of a page about an animation trope. Seems to have been put to rest.
edited 30th Aug '13 11:35:39 AM by Telcontar
That was the amazing part. Things just keep going.Search Wiki: That markup is (or rather, was) a link to the search function, yes?
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard FeynmanIt was actually the field where you would type your search, not just a link to it. I don't know where the results displayed.
That was the amazing part. Things just keep going.I think the results actually displayed as a variable added to the Search Wiki URL. So something like "SearchWiki?search=lampshading" or something like that.
And there is yet another markup not mentioned on Text-Formatting Rules: If you put [[#anchor]] on a page, you can link to this specific anchor by appending "#anchor" to the wiki link. Like this: Administrivia/TextFormattingRules#DefinitionLists links to Text Formatting Rules#DefinitionLists . (Edit: The link appears red, but it works.)
(At first I thought this would only work if you used full UR Ls, but apparently... see above.)
edited 8th Dec '13 4:02:05 PM by FELH2
Get rid of the walled gardenThat's mentioned in this thread's OP :P
Hmm, it seems you are right. Although I wonder whether anyone uses the #anchor extension for a wiki link. Have you ever seen it in use, except in this thread?
edited 8th Dec '13 4:30:20 PM by FELH2
Get rid of the walled gardenIf it didn't redlink, I would. there's little reason to click redlinks, so why make them?
Link to TRS threads in project mode here.I've seen about three [[#anchor]]s in all my time editing, two on Text-Formatting Rules and one in a long trope list where it jumped to the C section. That's how I found out about them. However, I've never seen them used with links — only ever the point buried in the page with nothing linking there to make it useful.
Ditto. It could be really useful as a table of contents on long indexes and some Useful Notes, but there's no point as long as it's red since nobody will click it. I brought the issue up in Tech Wishlist ages ago.
edited 9th Dec '13 1:26:13 AM by Telcontar
That was the amazing part. Things just keep going.I just tested with Sandbox.Crazy Samaritan, and it doesn't work as a redirect, so you can't get around the red link issue by creating a fake page, either. It just redirects to the page of the anchor point.
edited 9th Dec '13 6:01:02 AM by crazysamaritan
Link to TRS threads in project mode here.For some reasons, the "floatboxright" markup isn't on the list yet. Neither are lists using '+' instead of '*'.
Also, the # list markup is underused. Quite sure there are many cases of lists that use "* 1." instead, which is another kind of egregious.
edited 1st Mar '14 11:56:08 AM by FELH2
Get rid of the walled gardenI can't find a reference link, but I thought I read at one point that the floatbox thing is depreciated, and should be removed wherever found.
All your safe space are belong to TrumpTo my knowledge, floatboxrights are still cool but genreboxes are officially considered outdated and should be removed wherever you see them.
Yeah, # lists (along with the [numlist] markup) are underutilised. I think that + lists are fine with their current use, though; they get used plenty in index floatboxrights (e.g. on Meta-Concepts), and I don't know where else you'd put them.
That was the amazing part. Things just keep going.That's right.
And there is yet another one we have not mentioned yet: The superscript and subscript markups. It looks like they would be very useful for mathematical and chemical formula, like this: a2 + b2 = c2.
But for some reason, even Trivia.Math does not have them.
edited 1st Mar '14 12:02:44 PM by FELH2
Get rid of the walled gardenAnd those are even listed on Text-Formatting Rules. It's amazing how many people don't read through that before starting around here. You'd think someone would want to read the instructions for the markup before doing anything
On foreign language pages, e.g. De.Home Page, "[[source:en:HomePage]]" (or whatever source language and page it's translated from) is listed at the very bottom. I assume this is for linking translations together, but I can't actually find any trace of what it does.
That was the amazing part. Things just keep going.@Sixthhokage1: Yes, it seems most tropers learn markup from looking at it and figuring it out on the way. Which is exactly why rare markup stays rare.
Get rid of the walled garden
Per some very old staff discussions, please do not insert that particular markup on pages; in fact, kill it wherever you find it.