<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 65: Idea: consider typst as a backend</title><link>https://sourceforge.net/p/texmaths/feature-requests/65/</link><description>Recent changes to 65: Idea: consider typst as a backend</description><atom:link href="https://sourceforge.net/p/texmaths/feature-requests/65/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 08 Dec 2025 09:19:41 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/texmaths/feature-requests/65/feed.rss" rel="self" type="application/rss+xml"/><item><title>#65 Idea: consider typst as a backend</title><link>https://sourceforge.net/p/texmaths/feature-requests/65/?limit=25#26a8/5f5d</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Supporting typst would imply a huge rewriting of TexMaths. The expected benefit is not very appealing to me. &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roland Baudin</dc:creator><pubDate>Mon, 08 Dec 2025 09:19:41 -0000</pubDate><guid>https://sourceforge.netef811eb4b1300fdb92fa157d8277f0482fc92a49</guid></item><item><title>#65 Idea: consider typst as a backend</title><link>https://sourceforge.net/p/texmaths/feature-requests/65/?limit=25#26a8</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Indeed typst is a typesetting engine with a totally different syntax than LaTeX. But it serves a similar purpose (going from a textual description of the layout you want to obtain to the layout in a vector image format) and it works in a similar way (tagged text + preamble in → pdf out). The output pdf is said to be convertible in svg.&lt;/p&gt;
&lt;p&gt;So "backend" was possibly not the best term. But the idea was to adapt the texmaths code to let typst too be used as a layout engine. In detail:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Also the location of the binary of typst (and possibly pdf2svg) would need to be configurable and stored;&lt;/li&gt;
&lt;li&gt;Both a typst and a latex preamble would need to be available either at the global or at the document level;&lt;/li&gt;
&lt;li&gt;At the first creation of an equation, when the author picks the "engine", with the equation it should also be stored if the "language" is typst or latex. From this moment on, editing the equation would only allow to switch the engine among those suitable for the syntax (latex, xelatex or lualatex for latex and only typst for typst);&lt;/li&gt;
&lt;li&gt;According to the previous choices, compiling the equation would either call a latex engine or the typist engine.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The main advantage would be having an engine that is much faster than the latex ones. Quantifying the practical advantage needs knowing how much of the compilation time is currently spent in the latex engine and how much is texmaths overhead, but I would expect the first to be largely dominant and the second to be almost negligible. Being faster would be great since the best latex engine (lualatex) is really very slow for interactive use in a tool like texmaths and things get even worse when you need to do things like recompiling all the equations in a page (e.g. to change the font).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sergio Callegari</dc:creator><pubDate>Mon, 08 Dec 2025 07:42:05 -0000</pubDate><guid>https://sourceforge.netf8da8d8927732e89b7b3a564482731475d9ac442</guid></item><item><title>#65 Idea: consider typst as a backend</title><link>https://sourceforge.net/p/texmaths/feature-requests/65/?limit=25#42de</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;You may know that typst is not a LaTeX backend, it's a different language, so you can't write LaTeX equations and compile them with typst.&lt;br/&gt;
So it's simply not possible to use typst as a backend in TexMaths...&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roland Baudin</dc:creator><pubDate>Sun, 07 Dec 2025 16:29:44 -0000</pubDate><guid>https://sourceforge.net5dcdaf6bd94f6538ed47e208119bced52039cc4a</guid></item><item><title>#65 Idea: consider typst as a backend</title><link>https://sourceforge.net/p/texmaths/feature-requests/65/?limit=25#4065</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket moved from /p/texmaths/bugs/207/&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Roland Baudin</dc:creator><pubDate>Sun, 07 Dec 2025 16:22:29 -0000</pubDate><guid>https://sourceforge.net065dfa8caed56bc71342c5f56f3e8759eccd9cdb</guid></item><item><title>Idea: consider typst as a backend</title><link>https://sourceforge.net/p/texmaths/bugs/207/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi, as usual, thanks for the excellent texmaths. I would like to suggest an idea  that you might have thought about already (and maybe discarded).  If this message is redundant, my apology in advance.&lt;/p&gt;
&lt;p&gt;As you surely know, there is a new contender in the typesetting arena: typst. Even if it is still young, there are already some things it does well, including math, and one of its main advantages over latex is that it is much faster (particularly if the comparison is wrt lualatex). More speed would be greately beneficial to a tool like texmaths.&lt;/p&gt;
&lt;p&gt;So I wonder if you might have considered a typst backend.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sergio Callegari</dc:creator><pubDate>Tue, 02 Dec 2025 10:15:18 -0000</pubDate><guid>https://sourceforge.net649e859dbbdb7fab16601039f5bf3416a4a1b4e4</guid></item></channel></rss>