Re: pytex: a tex engine written in python
Junling Ma <[email protected]> Mon, 13 Jul 2026 10:49:57 -0700
| Newsgroups | gmane.comp.tex.texhax |
|---|---|
| Message-ID | <[email protected]> |
--Apple-Mail=_F0C56AE1-7688-4747-8810-F4FD1E0991CB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Philip, Thanks for your feedback. Yes current \XeTexpictfile and \XeTeXpdffile = are supported, as they are needed by latex. A very limited list of = implemented XeTeX commands are implemented. They are listed at the end = of pytex/xetex.py=20 Best, Junling > On Jul 13, 2026, at 3:59=E2=80=AFAM, Philip Taylor (RHBNC) = <[email protected]> wrote: >=20 >=20 >=20 > On 13/07/2026 11:30, Joseph Wright wrote: >> Hello Junling,=20 >>=20 >> Looks interesting. With XeTeX essentially unmaintained, this could be = a path for users to migrate to something with updates possible (though = accessible PDFs likely remain more realistic with LuaTeX). Have you = considered adding \XeTeXinterchartoks support?=20 >>=20 >> Regards,=20 >>=20 >> Joseph > I too would be most interested in anything that is (a) maintained, and = (b) capable of doing everything that XeTeX currently does =E2=80=94 I = use no other engine. But while I rarely use \XeTeXinterchartoks, I use = \XeTeXpdffile and \XeTeXpicfile on a daily basis, so would definitely = require those (and the other XeTeX + e-TeX primitives) to be supported. >=20 > --=20 > Philip Taylor >=20 > This email, its contents and any attachments are intended solely for = the addressee and may contain confidential information. In certain = circumstances, it may also be subject to legal privilege. Any = unauthorised use, disclosure, or copying is not permitted. If you have = received this email in error, please notify us and immediately and = permanently delete it. Any views or opinions expressed in personal = emails are solely those of the author and do not necessarily represent = those of Royal Holloway, University of London. It is your responsibility = to ensure that this email and any attachments are virus free. >=20 >=20 --Apple-Mail=_F0C56AE1-7688-4747-8810-F4FD1E0991CB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" = content=3D"text/html; charset=3Dutf-8"></head><body = style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; = line-break: after-white-space;">Hi Philip,<div><br></div><div>Thanks for = your feedback. Yes current \XeTexpictfile and \XeTeXpdffile are = supported, as they are needed by latex. A very limited list of = implemented XeTeX commands are implemented. They are listed at the end = of = pytex/xetex.py </div><div><br></div><div>Best,</div><div>Junling<br = id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote = type=3D"cite"><div>On Jul 13, 2026, at 3:59=E2=80=AFAM, Philip Taylor = (RHBNC) <[email protected]> wrote:</div><br = class=3D"Apple-interchange-newline"><div> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"> <div><p><br> </p> <div class=3D"moz-cite-prefix">On 13/07/2026 11:30, Joseph Wright = wrote:<br> </div> <blockquote type=3D"cite" = cite=3D"mid:[email protected]"> Hello Junling, <br> <br> Looks interesting. With XeTeX essentially unmaintained, this could be a = path for users to migrate to something with updates possible (though = accessible PDFs likely remain more realistic with LuaTeX). Have you = considered adding \XeTeXinterchartoks support? <br> <br> Regards, <br> <br> Joseph <br> </blockquote><p>I too would be most interested in anything that is (a) = maintained, and (b) capable of doing everything that XeTeX currently = does =E2=80=94 I use no other engine. But while I rarely use = \XeTeXinterchartoks, I use \XeTeXpdffile and \XeTeXpicfile on a daily = basis, so would definitely require those (and the other XeTeX + e-TeX = primitives) to be supported.</p><p>-- <br> <i>Philip Taylor</i><br> </p><p>This email, its contents and any attachments are intended solely = for the addressee and may contain confidential information. In certain = circumstances, it may also be subject to legal privilege. Any = unauthorised use, disclosure, or copying is not permitted. If you have received this email in error, please notify us and = immediately and permanently delete it. Any views or opinions expressed = in personal emails are solely those of the author and do not necessarily = represent those of Royal Holloway, University of London. It is your responsibility to ensure that this email and any = attachments are virus free.</p><div><br = class=3D"webkit-block-placeholder"></div> </div> </div></blockquote></div><br></div></body></html>= --Apple-Mail=_F0C56AE1-7688-4747-8810-F4FD1E0991CB--