I added a disclaimer to the sin-1( page about the limitations of the wiki syntax. What do you guys think of it? Should we add it to other pages, or is it not necessary? If you like it, I think we should add it to the command (and possibly routine) stub.
I like it. I was wondering how to fit in a disclaimer. This will be especially useful for the superscript r. I'll add this into the other pages.
 Actually, I think one more specific to the page would be better. At the top of the page we could list off the commands and then have a link to another page that explains the notation limitation and lists what commands are affected.
That's a really good idea! When you say list off the commands, are you just talking about the commands mentioned on the page, or all of the commands that don't display correctly? I suppose I can start working on putting that together.
On the command/routine page it will list the commands that don't display correctly used on that page, but the main page would list off all the commands not displayed correctly, including a picture of what it is supposed to look like (I think TeX can cover that) (just using ^^ will work since it's not in a code box) or title and how to access it.
So something like: "NOTE: Due to the limitations of the wiki markup language, the commands xxxx on this page do not appear as they would on the calculator"
The xxxx will be a list of the commands on that page, and they will link to the description of what it's supposed to be.
 I think this is all the commands:
r (radian), the circular and hyperbolic inverses (6 of them) , -1 (reciprocal/inverse matrix) , T (transpose)
And something like this could go at the top of the main not-displayed-properly page (what's a better/shorter name for that?): "Due to the limitations of the wiki markup language, some commands will not appear as they would on the calculator. Any page containing one or more of these commands will have a disclaimer and links to more information on the individual commands affected."
I think the Wiki Markup Limitations page should have the information for each of the commands, so something like this for /^r/
r (Radian symbol)
-displayed as /^r/ in this Wiki
-  or use arrows to select r
(I'm using /^r/ since that's what we used to use on the forums before everyone stuck symbols in their sigs)
 Okay, I added the descriptions into the Wiki-Limits page. If you guys like it I can go to each page that has one of the disclaimers and have them link to the individual details for the command. For example, the disclaimer for sin-1( would be:
I like it. The other thing I would do to finish it off is add the disclaimer to the command stub. You could just preface it with the "(this section is usually not present)" statement. Nice work, though :D
I'm thinking of changing /^r/ to ^^r, since the former looks bulky and confusing. I'm using the double ^ because ^r would be confusing too.
What should be used for T? DarkerLine has used '[A]T' in a few places already, so I'm not sure if I should change it to ^^T (or something else). Plus, since it always comes right after a matrix it shouldn't be confusing. As long as we use the same noation for T everywhere I don't think it will matter too much.
I would just use T by itself, without the ^^ before it. The general rule of thumb I tend to follow is once you start displaying something a certain way, you should continue displaying it like that; it helps with continuity and it maintains a standard.
Well both T and r (as well as -1, sin-1(, and others) can be displayed normally throughout most of the article - it's just code that there's problems with.
An alternative to code blocks could be found which would work as well. Quotes almost work, but ignore leading spaces. Maybe some sort of clever div thing could be done, but I don't know how much freedom wikidot gives with those. Finally, you can do pretty much any formatting with LaTeX but that might be more trouble than it's worth.
Also, there's no way to use a smaller font size, which would work better for list L than a special character (which is what we're using now)
I looked in the Wikidot CSS file, and found the code that they use to generate the code block. As it turns out, when they render the code block on the page, they are actually nesting a <code> tag inside a <pre> tag, and both of those are nested inside a <div> tag:
I started recreating that with just a <div> tag, but it still needs some work. Try testing this out on the cosinv page, and tell me what you think:
[[ div style="border: 1px dashed #DDD; background: #F7F7F7; padding: 0 1em; margin-top: 0.4em 0; overflow: auto; font-family: 'Andale Mono','Courier New', monospace;white-space: pre;line-height: 0.6em;"]]
Yeah, that's what I get too. The white-space attribute is what controls that behavior, and when you set it to pre, the spaces are supposed to be preserved. As to why it doesn't work, I don't really know, but I'm going to make a topic in the Wikidot community forum and ask for help. I'll see what they say.
For the inverse commands, how does using sin‾¹( look?