36,359 reputation
168150
bio website randomdeterminism.wordpress.c…
location
age
visits member for 4 years, 3 months
seen 6 hours ago

Jun
2
answered formatting natural table header with conTeXt
Jun
2
comment Are there any disadvantages of TeX being Turing complete?
In tex/pdftex, tex the program uses only a fixed amount of memory. Isn't "infinite tape" also a requirement for a Turing machine?
Jun
2
comment Asymptote code integration into Beamer format
Try adding [fragile] option to \begin{frame}
Jun
2
comment How to show section title before section number
@GonzaloMedina: Definitely give it a shot.
Jun
2
answered How to show section title before section number
Jun
2
awarded  Necromancer
Jun
1
comment How to best typeset “special” constants (complex unit i, Euler's number e,…)?
I looked into the Wikipedia and I don't know what 0x+2107 is supposed to represent. But it is strange that Unicode standard includes a separate slot for plank's constant, but not for Euler's number. The Unicode symbols for imaginary number, differential operator, probability, etc are not used too often because (a) until recently there were a few full unicode math fonts, and (b) their default implementations are ugly (though that is font dependent issue). I think that one should use the unicode input for these characters, the actual shape can be changed by patching the font on the fly.
Jun
1
revised How to best typeset “special” constants (complex unit i, Euler's number e,…)?
added 135 characters in body
Jun
1
answered How to best typeset “special” constants (complex unit i, Euler's number e,…)?
May
31
comment flip book in master thesis
Depending on the size of the image, I think that an image in the outer margin will be better (this means that you'll need a double sided layout). That way, the "reader" can easily flip through the pages to see the animation.
May
30
comment Automatic thousands separators?
@mbrok: ConTeXt does parse digits when converting to MathML. For example $1234 x$ will be converted to <mnum> 123 </mnum> <...>x</...> (sorry don't remember MathML tags on top of my head. Of course the parser is written in Lua and, in principle, adding a output formatter for PDF output is easy.
May
30
comment LaTeX Cartooning
@morburg, The MPS to PDF conertor used by pdflatex is provided by context. Perhaps the OP meant that.
May
29
comment Relationship between MathML and TeX
ConTeXt also parses TeX and generates MathML when generating XML/XHTML output.
May
29
comment Relationship between MathML and TeX
FWIW, ConTeXt can parse TeX and generate MathML, but it generates presentation MathML and not content MathML. There are a few helper macros to remove ambiguity. So, if you have a link to few hard to parse TeX examples, I'd be curious to test them out with the ConTeXt parser and see how they behave.
May
28
comment Automating quoting across LaTeX documents
Same as orig.tex.
May
28
comment Automating quoting across LaTeX documents
I have split the orig.tex file in your example to two files, quotes.tex and orig.tex. The new.tex is the same as the new.tex in your question. So, basically, I am using a separate file to define quotes.
May
28
comment Why using a backslash in command definitions?
Compare the above from, say the plainTeX definition of \newif\ifsomething which then goes through some hoops to remove the \if and define \somethingtrue, \somethingfalse. Using \newconditional {something} would be much easier.
May
28
comment Why using a backslash in command definitions?
ConTeXt does this all the time: \define<something> usually defines \start<something> \setup<something>, etc (actually, it defines multi-lingual macros, so in french documents you can use \demarre<something> .. \regale<something>. Internally, all such macros use \setvalue (or its variants \setuvalue, etc), which are similar to the \NewDocumentCommandName macro (actually to \@namedef etc.)
May
28
comment Why using a backslash in command definitions?
The advantage of the former is that you can use it for nested definitions: \NewDocumentCommandName{defineenvironment}{m}{\NewDocumentCommandName{start#1}{‌​whatever}\NewDocumentCommandName{stop#1}{whatever}} etc.
May
28
comment Why using a backslash in command definitions?
I don't understand what you mean "avoid dynamic definitions at document interface level" for LaTeX3. Could you elaborate?