Also including questions that should be frequently asked but aren’t. See also HowTo.
The characters < and > are interpreted as beginning or ending HTML tags. To make a less-than or greater-than sign in iTeX math mode, use \lt
and \gt
respectively. For example, $0\lt 1$
produces .
By default, the itex syntax $...$
is disabled inside raw HTML. However, you can re-enable it by giving the HTML parameter markdown="1"
. Thus
I can has $m^a_t \hbar$!! |
produces
I can has $(m^a)_t \hbar$!! |
(Well, that used to work, but it seems to have broken along the way!)
At least for tables, you can also use the PHP Markdown Extra syntax inside which $...$
works without a problem.
See the HowTo
One of the notable ways in which itex differs from latex is that in itex’s math mode, a string of letters without spaces in between is interpreted as a single identifier. This has the advantage that you can invent new identifiers without needing to use \operatorname
or \DeclareMathOperator
, but it means that when you don’t want a string of letters interpreted that way you need to put spaces in between. For example, $sin(x)$
produces which is probably what you want, but $h=gf$
produces , whereas you probably wanted to write $h=g f$
to get . On the other hand, you can (and, for the sake of the LaTeX output, probably should) use $\sin(x)$
, etc.
There are several bugs (or “edge cases”) in the handling of lists by Maruku (the formatting filter used by Instiki). These include:
iTeX is not LaTeX. iTeX is a pure converter whereas LaTeX is a mixture of a converter and renderer (technically, latex is the rules for converting the input into pure TeX which is then rendered by tex, but since the conversion is also handled by tex, it can cheat and use information about the rendered output to reinterpret the input). Therefore getting the two to do exactly the same is never going to happen.
On the other hand, the aim is to keep iTeX as close as possible to standard LaTeX whilst keeping in mind that iTeX produces MathML. Their similarity can make the differences all the more jarring. Here is a list of the differences that we know about together with suggested work-arounds.
Numbers are one thing. The syntax $10^10$
produces in iTeX but in LaTeX. The safe syntax is to always use braces: $10^{10}$
is consistent.
Numbers include punctuation. Periods and commas within numbers are numbers. This is so that $1,000,000.00$
(or $1.000.000,00$
if you are European) renders correctly as and not . When combined with the previous difference, this means that $t^3.2$
renders as instead of . Either use braces or spaces. (However, for some reason, $t^3,2$
renders as like you'd expect from TeX, so the two differences don't interact entirely logically. This might have been different in earlier versions of iTeX.)
Operator names. Since iTeX does not have macro support, extending the list of operator names would be difficult except for the fact that neighbouring strings of letters get combined into an operator name. Thus $cos$
produces . However, in LaTeX this produces . Where the operator name is a standard LaTeX one, such as \cos
, the backslash can be added so $\cos$
renders correctly in both cases. Where the operator name is not a standard LaTeX one, say Poly
, the safe syntax is to use \operatorname
; thus $\operatorname{Poly}$
renders correctly as in both situations. If you don't want an operator name, then use spaces; thus $c o s$
produces .
Whitespace in embedded text. In LaTeX $x \text{ and } y$
renders as but in iTeX it renders as . This is because MathML says that fore and aft whitespace on mtext
elements should be swallowed. The safe syntax is $x\;\text{and}\;y$
.
Two-character relations. In LaTeX, two neighbouring relation symbols are combined into one relation symbol. Thus $y := f(x)$
becomes , while $y = -f(x)$
becomes because a minus sign is a unary operator instead of a binary relation. Since MathML doesn't know the difference between unary operators and binary relations, it is inconvenient for iTeX to do this, so $y := f(x)$
comes out as instead. The safe syntax is $y \mathrel{:=} f(x)$
, which produces . However, in many cases, there is a combined command that you can use. In this case, $y \coloneqq f(x)$
produces . This method is better when available; even in LaTeX, it will adjust the vertical positioning a bit to look nice.
Non-ascii characters. iTeX is designed only to parse the mathematical sections of any page and so it assumes that any strange characters will be generated via iTeX commands such as \infty
instead of being directly input as ?. iTeX actually takes an extreme view on this and will not parse mathematics if it includes non-ascii characters. In ordinary mathematics this should not be a problem since one should use the iTeX commands themselves to produce such characters. Where it can be a problem is in \text
commands embedded in mathematics because these are still parsed by iTeX even though it does nothing with them. Thus \text{?}
is not a legal construct and will simply produce . Since iTeX does not allow nesting, the construction \text{$\infty$}
will not work. There are two possibilities:
\text
command: \text{in~}\infty{-categories}
produces (note the forced space, simple whitespace there will not work).\text{in ∞-categories
produces . Named entities will not work here as they get converted to unicode internally before being sent to the iTeX parser.Instiki’s search uses regular expressions. That means you can do all sorts of fancy searches, but it also means that pages with special characters in their names are hard to search for. For instance, if you search for (n,r)-category
you will come up with nothing, because Instiki interprets the parentheses as a regular expression grouping construct. To search for actual parentheses, you need to backslash them: search instead for \(n,r\)-category
.
Instiki’s philosophy is that the “Preview” button is the one labeled “Save”. If you don’t like the result, just click “Edit” again. Multiple edits by the same person within a 30 minute interval are collapsed into a single “edit” in the revision history.
One merit of this approach is that in the case when your preview was correct and doesn’t require re-editing, it saves you an extra click. Another is that it prevents you from ever forgetting to make the extra click.
Many web sites “support” LaTeX by running it through a script which converts LaTeX equations to image files for display. While this produces acceptable results for many users, it is not true “support” for mathematics. Images can sometimes be hard to see, and the user cannot easily resize them or change their color or font, nor can software easily read them aloud to a blind user. In contrast, MathML is a markup language, like HTML, specifically designed to carry information not only about the display of mathematics, but its content and meaning. A suitable client application can resize MathML along with the rest of the page, change its color or font, or even read it aloud, making MathML a much more accessible way to display mathematics. See, for instance, this comment.
See this discussion.
You can use HTML/XML/SGML character entity references. If the character you want has a mnemonic HTML name, like é for é, you can use that. Otherwise, you can use an SGML numerical code, like 㒫 for 㒫, that corresponds directly to Unicode. To look up the numbers for SGML characters, try the Unicode Character Names Index. Toby has a complete list of HTML and XML character entity references (or try the Unicode Databank pages listed below) with individual pages where you can check browser compliance (originally for when you couldn't take even things like ↔ for granted, but even now ‎ and   may be lacking). While you can use this technique for mathematical symbols too, it's best to do those in iTeX as explained above.
Did you read the Naming Conventions section on the HowTo?
Questions, comments and other discussions are to be had on the nForum.
You should, of course, include a link or URL to the page or pages that you wish to cite. You should also give the information about which version of the page you are citing, since pages change over time. The version number can be found as follows: look at the bottom of the page where it says “Back in time ( revisions)”; the current version number is .
You can link directly to the version you want to cite by using a url such as
http://ncatlab.org/nlab/revision/PageName/VERSIONNUMBER
We recommend that if you only include one URL, it be of the form show/PageName
which will point to whatever version of the page is current when it is accessed. This is because pages generally improve over time, and whoever is following your reference ought to be taken to the best, up-to-date version of the page. Anyone who cares about finding the exact version of the page that you cited can figure out how to find it in the history.
On the other hand, if you can give two URLs (this would be cumbersome in a printed paper, but is possible with links on a web page), then it may be helpful to give the appropriate revision
link as well as the show
one.
All nLab pages now include a “Cite” link at the bottom of the page which produces a BibTeX entry in accord with the suggestions above.
There are numerous ways you can help out and get acquainted with the community even if you don’t (yet) feel comfortable writing math publically on a wiki.
You can do lab elf? duty, such as correcting typos and spelling errors, fixing links, creating links, creating redirects (there are many pages that still need redirects created for alternate and plural forms of the title), organizing pages, and so on.
You can ask questions (see previous question), and join discussions, at the nForum, and comment at the nCafe.
You can try writing small additions to existing pages, for instance a paragraph or two that helps explain something that puzzled you initially. If you aren’t entirely positive that what you wrote was correct, when you announce your edit at Latest Changes on the nForum, you can mention that you’re unsure and someone will usually reassure you or give a correction.
If you don't sign your edits, then they are attributed to the AnonymousCoward. We prefer that you sign your edits, but anonymous help is better than none at all, so that option is available to you.
Some users have personal areas of the n-Lab where they can have password protected pages and do work without fitting it into the rest of n-Lab. If you would like to have such an area, ask the steering committee.
The n-Lab has a spam filter that checks your IP against a blacklist. The blacklists used are maintained by spamcop.net and spamhaus.org. IPs are added to these lists if they are detected doing things usually associated with computers infected with viruses. There are instructions on the webpages for finding out if your IP has been added to these lists and what to do to remove your IP from them. Three things to point out are:
Sometimes something doesn’t work quite right with the software and it bails out. If you think that you were doing something that should work, please log the error message at the n-Forum. The more information that you log, the easier it is for us to debug. Useful information is: your IP, the time and date, and the URL that you were trying to access.
There is actually more information contained in the HTML source of the error message (“view source”): some errors can be down to malformed input when editing a page and that can help you fix it yourself.
Last revised on May 8, 2022 at 15:23:29. See the history of this page for a list of all contributions to it.