<story><title>How we ported LaTeX to the iPad</title><url>http://texpadapp.com/2012/09/19/latex-ported-to-ipad/</url></story><parent_chain></parent_chain><comment><author>khaled</author><text>The most clueless TeX related piece I have read since their previous one. For example, kpathsea is a library that TeX engines call, so no forking is done to “grab search paths from the Kpathsea system”. And the bright future for C implementation didn&apos;t happen when TeX WEB code was hand converted into much more readable C code 8 years ago (&lt;a href=&quot;http://metatex.org/&quot; rel=&quot;nofollow&quot;&gt;http://metatex.org/&lt;/a&gt;), not to mention the existence of an actively maintained, extended TeX engine written in C (&lt;a href=&quot;http://www.luatex.org/&quot; rel=&quot;nofollow&quot;&gt;http://www.luatex.org/&lt;/a&gt;), wait, this is GPL “encumbered” so it does not count. Did I mention that XeTeX does not “skip the DVI step” at all, but it actually &lt;i&gt;does&lt;/i&gt; fork an external binary to convert its ‘extended’ DVI into PDF.</text></comment>
<story><title>How we ported LaTeX to the iPad</title><url>http://texpadapp.com/2012/09/19/latex-ported-to-ipad/</url></story><parent_chain></parent_chain><comment><author>kibwen</author><text>Very interesting, but does anyone here feel like this would be useful to them? For example, in my limited experience with LaTeX I&apos;ve also needed to generate graphs (via Graphviz or R). Even if there existed apps for these, I&apos;m under the impression that the iPad has no user-accessible filesystem, nor allows iPad apps to talk to each other. Please correct me if this is mistaken.</text></comment>