Not signed in

Want to take part in these discussions? Sign in if you have an account, or apply for one below

• Username
• Password
• Remember me

• Sign in using OpenID
• Remember me

• Forgot your password?
• Apply for membership

2-category 2-category-theory abelian-categories adjoint algebra algebraic algebraic-geometry algebraic-topology analysis analytic-geometry arithmetic arithmetic-geometry book bundles calculus categorical categories category category-theory chern-weil-theory cohesion cohesive-homotopy-type-theory cohomology colimits combinatorics complex complex-geometry computable-mathematics computer-science constructive cosmology deformation-theory descent diagrams differential differential-cohomology differential-equations differential-geometry digraphs duality elliptic-cohomology enriched fibration finite foundation foundations functional-analysis functor gauge-theory gebra geometric-quantization geometry graph graphs gravity grothendieck group group-theory harmonic-analysis higher higher-algebra higher-category-theory higher-differential-geometry higher-geometry higher-lie-theory higher-topos-theory homological homological-algebra homotopy homotopy-theory homotopy-type-theory index-theory integration integration-theory k-theory lie-theory limits linear linear-algebra locale localization logic mathematics measure-theory modal modal-logic model model-category-theory monad monads monoidal monoidal-category-theory morphism motives motivic-cohomology nlab noncommutative noncommutative-geometry number-theory of operads operator operator-algebra order-theory pages pasting philosophy physics pro-object probability probability-theory quantization quantum quantum-field quantum-field-theory quantum-mechanics quantum-physics quantum-theory question representation representation-theory riemannian-geometry scheme schemes set set-theory sheaf sheaves simplicial space spin-geometry stable-homotopy-theory stack string string-theory superalgebra supergeometry svg symplectic-geometry synthetic-differential-geometry terminology theory topology topos topos-theory tqft type type-theory universal variational-calculus

1. • CommentRowNumber1.
   • CommentAuthorAndrew Stacey
   • CommentTimeOct 5th 2010
   • PermaLink
   Author: Andrew Stacey
   Format: MarkdownItexNot all of iTeX is full LaTeX-compatible. Jacques Distler's aim is that it should be as compatible as possible, but there are a few things that predate his incumbency and cannot be removed without breaking backward-compatibility. One of the most obvious of these is the `\array` command. The reasons why this is a problem are: 1. There _is_ an `\array` command in LaTeX, but it is *not* what `\array` is used for in iTeX. The `\array` command in LaTeX is actually a synonym for `\begin{array}` so the contents of the array (in LaTeX) is what follows the command rather than an argument to it. 2. For some reason, people on the nLab have adopted the `\array` command for aligning stuff. This means that when exporting an nLab page, `\array` breaks the compilation. Fortunately, there is a relatively simple solution. ### Immediate Solution After exporting the page, use a text editor to replace all occurrences of `\array` by something safe like `\itexarray`. Then add the following code in the preamble: \newcommand{\itexarray}[1]{\matrix #1 \endmatrix} ### Long-term Solution Whenever you come across the `\array` construction in an nLab page, replace it by `\begin{matrix} ... \end{matrix}`. Note that the `\array` command makes use of the fact that arrays in MathML are a little different to arrays in LaTeX so there are occasions that these extras are used and _those_ situations should not be changed. But if none of these are used, it's safe to replace `\array` by the matrix environment. For more on the difference, see [this page](http://golem.ph.utexas.edu/~distler/WebTeX/docs/wtxsec7.html#ARRAY) on the iTeX version. (That page might also be the source of why `\array` appears so much in nLab pages as there is an example there of a commutative diagram which probably got cut-and-pasted in to the first commutative diagram on the n-Cafe!)

   Not all of iTeX is full LaTeX-compatible. Jacques Distler’s aim is that it should be as compatible as possible, but there are a few things that predate his incumbency and cannot be removed without breaking backward-compatibility. One of the most obvious of these is the \array command. The reasons why this is a problem are:

   1. There is an \array command in LaTeX, but it is not what \array is used for in iTeX. The \array command in LaTeX is actually a synonym for \begin{array} so the contents of the array (in LaTeX) is what follows the command rather than an argument to it.
   2. For some reason, people on the nLab have adopted the \array command for aligning stuff.

   This means that when exporting an nLab page, \array breaks the compilation. Fortunately, there is a relatively simple solution.

   Immediate Solution

   After exporting the page, use a text editor to replace all occurrences of \array by something safe like \itexarray. Then add the following code in the preamble:

   \newcommand{\itexarray}[1]{\matrix #1 \endmatrix}
   

   Long-term Solution

   Whenever you come across the \array construction in an nLab page, replace it by \begin{matrix} ... \end{matrix}.

   Note that the \array command makes use of the fact that arrays in MathML are a little different to arrays in LaTeX so there are occasions that these extras are used and those situations should not be changed. But if none of these are used, it’s safe to replace \array by the matrix environment. For more on the difference, see this page on the iTeX version.

   (That page might also be the source of why \array appears so much in nLab pages as there is an example there of a commutative diagram which probably got cut-and-pasted in to the first commutative diagram on the n-Cafe!)

2. • CommentRowNumber2.
   • CommentAuthorMike Shulman
   • CommentTimeOct 5th 2010
   • PermaLink
   Author: Mike Shulman
   Format: MarkdownItexWouldn't a better long-term solution be to modify the TeX output feature of instiki so that it translates `\array` into something like `\itexarray` itself? No one is going to be writing `\array` in iTeX and wanting it to come out as the LaTeX version.

   Wouldn’t a better long-term solution be to modify the TeX output feature of instiki so that it translates \array into something like \itexarray itself? No one is going to be writing \array in iTeX and wanting it to come out as the LaTeX version.