3 ms·
I regularly edit large equations in LaTeX. I don't see how it's not manageable, just break your equations into multiple lines. \begin{equation} H_n(i) =
by leni536 10y ago
I regularly edit large equations in LaTeX. I don't see how it's not manageable, just break your equations into multiple lines.
\begin{equation}
H_n(i) =
\begin{cases}
\left(
H_{n-1}(i)_2,
H_{n-1}(i)_1
\right) &
0 \le i < 2^{2(n-1)}
\\
\left(
H_{n-1}(i-2^{2(n-1)})_1,
H_{n-1}(i-2^{2(n-1)})_2 + 2^{n-1}
\right) &
2^{2(n-1)} \le i < 2 \cdot 2^{2(n-1)}
\\
\left(
H_{n-1}(i-2\cdot2^{2(n-1)})_1 + 2^{n-1},
H_{n-1}(i-2\cdot2^{2(n-1)})_2 + 2^{n-1}
\right) &
2 \cdot 2^{2(n-1)} \le i < 3 \cdot 2^{2(n-1)}
\\
\left(
- H_{n-1}(i-3\cdot2^{2(n-1)})_2 + 2^{n}-1,
- H_{n-1}(i-3\cdot2^{2(n-1)})_1 + 2^{n-1}-1
\right) &
3 \cdot 2^{2(n-1)} \le i < 4 \cdot 2^{2(n-1)}
\\
\end{cases}
\end{equation}
> For instance, doesn't the fact that people do pure algebra with Mathematica (forgetting about all the numerics, integrals, etc.) demonstrate that TeX loses for sufficiently large equations?
I use Mathematica, and I just use the plaintext Mathematica syntax for large equations too. I also break these into multiple lines.
- jessriedel 10y ago> regularly edit large equations in LaTeX. I don't see how it's not manageable, just break your equations into multiple lines. I understand how to indent TeX, but when you have a hundred algebraic terms it's very unwieldly, and Mathematica becomes clearly superior (for me) just to visualize it. Anyways, it sounds like you're just saying you haven't found the graphical visualization for equation trees to be useful, so you stick with the linear representation, but the manipulations of those trees (by mathematica, or some other dedicated editor) is still useful. In this case I would add that we would probably still need some sort of visualization aid for sufficiently large equations, and that the tools are just not good right now. After all, much/most code is written in normal (linear) text editors, but some people still do find it useful to "collapse" sections of code, corresponding to branches of the tree structure induced by indentation. Many people don't bother with this right now because it can cause headaches that simple scrolling does not, but better tools may change this.