{"@attributes":{"version":"2.0"},"channel":{"title":"The LaTeX Project","description":{},"link":"https:\/\/latex-project.org\/\/","pubDate":"Fri, 19 Jun 2026 21:26:12 +0000","lastBuildDate":"Fri, 19 Jun 2026 21:26:12 +0000","generator":"Jekyll v4.3.3","item":[{"title":"Webinar on Accessible Mathematical Content in PDF","description":"<h1 id=\"webinar-on-accessible-mathematical-content-in-pdf\">Webinar on Accessible Mathematical Content in PDF<\/h1>\n\n<p>The webinar \u201cAccessible Mathematical Content in PDF\u201d, organized by the PDF Association on June 16th, was a great success from the feedback we received.<\/p>\n\n<p>The four panelists David Carlisle (LaTeX Project &amp; editor of MathML at W3C), Boris Doubrov (Dual Lab &amp; chair LaTeX Project Liasion Working Group), Frank Mittelbach (LaTeX Project lead), Neil Soiffer (creator of MathCAT &amp; co-chair of the Math Working Group at W3C), and moderator Duff Johnson (CEO PDF Association) discussed the current state and demonstrated that there is now a reliable workflow to produce accessible documents with mathematical content and use them in viewers and browsers with AT support.<\/p>\n\n<p>The webinar was divided into a presentation\/demonstration part and a lengthy Q\/A session and was attended by more than 230 people. More than 100 of them filled out the survey afterwards and offered comments and\/or posed additional questions. We plan to answer those as well and post the questions and answers next to webinar recording in the near future.<\/p>\n\n<p>If you haven\u2019t been able to attend but would like to watch the recording and obtain the presentation material, check out the link to the webinar page.<\/p>\n\n<ul>\n  <li><a href=\"https:\/\/pdfa.org\/event\/webinar-accessible-mathematical-content-in-pdf\/\">https:\/\/pdfa.org\/event\/webinar-accessible-mathematical-content-in-pdf\/<\/a><\/li>\n<\/ul>\n\n<p>Enjoy \u2014 Frank<\/p>\n\n","pubDate":"Fri, 19 Jun 2026 00:00:00 +0000","link":"https:\/\/latex-project.org\/\/news\/2026\/06\/19\/PDFA-webinar\/","guid":"https:\/\/latex-project.org\/\/news\/2026\/06\/19\/PDFA-webinar\/","category":["best practice guide","accessibility","accessible math","tagged PDF","PDFA","PDF\/UA-2","LaTeX","news"]},{"title":"LaTeX 2026-06-01 released and distributed","description":"<h1 id=\"latex-2026-06-01-release-distributed\">LaTeX 2026-06-01 release distributed<\/h1>\n\n<p>We sent the 2026-06-01 release of the LaTeX kernel to CTAN at the weekend, and\nits already available in TeX Live (MiKTeX should follow soon).<\/p>\n\n<h2 id=\"news-from-the-tagging-project\">News from the tagging project<\/h2>\n\n<p>Progress in embedding tagging code as part of a more general overhaul continues.\nThe implementation of block structures, such as theorems, and headings\n(sections), has been updated. We are well on the way to providing a flexible\ninterface that many document authors will be able to use without needing\nadditional code or packages.<\/p>\n\n<p>This work is also an opportunity to look back at (long-standing) LaTeX code and\nto see where there are issues. As well as refining some spacing, we have\naddressed a long-standing technical wrinkle: (mis)using math mode simply to\nalign material vertically. This \u2018fake math\u2019 is a serious tagging issue but also\nshows up where the user wants, for example, to apply a color change to all\nmathematics. With this release, the use of math mode is essentially restricted\nto \u2018true math\u2019.<\/p>\n\n<p>Work on better supporting languages has been ongoing, with new <code class=\"language-plaintext highlighter-rouge\">language<\/code> and\n<code class=\"language-plaintext highlighter-rouge\">other-languages<\/code> keys for <code class=\"language-plaintext highlighter-rouge\">\\DocumentMetadata<\/code>; these support standard BCP-47\nstrings such as <code class=\"language-plaintext highlighter-rouge\">en-GB<\/code>.<\/p>\n\n<p>Working on templates has prompted us to further revise some concepts that have\nbeen added to the kernel in recent years, to align the code more closely with\nthe most natural pathways for users.<\/p>\n\n<h2 id=\"other-improvements-and-changes\">Other improvements and changes<\/h2>\n\n<p>Work of course is not restricted to tagging. There are further improvements to\ncopy-paste of symbols, several bug fixes for corner cases in <code class=\"language-plaintext highlighter-rouge\">amsmath<\/code>, and more\nlanguage support for <code class=\"language-plaintext highlighter-rouge\">varioref<\/code>. At the lower level, work on the L3 programming\nlayer continues; notably here, we have made adjustments to better support the up\nengine in creating programmatic strings.<\/p>\n\n<p>The <a href=\"\/news\/latex2e-news\/ltnews43.pdf\">newsletter<\/a>\nalso covers various other small enhancements or corrections that we provide\nwith the June release.<\/p>\n\n<p>Enjoy \u2013 Joseph<\/p>\n","pubDate":"Mon, 01 Jun 2026 00:00:00 +0000","link":"https:\/\/latex-project.org\/\/news\/2026\/06\/01\/issue43-of-latex2e-released\/","guid":"https:\/\/latex-project.org\/\/news\/2026\/06\/01\/issue43-of-latex2e-released\/","category":["latex2e","news"]},{"title":"Time for testing: the final pre-release for 2026-06 is available","description":"<h1 id=\"time-for-testing-the-final-pre-release-for-2026-06-is-available\">Time for testing: the final pre-release for 2026-06 is available<\/h1>\n\n<p>The second and final pre-release version for the 2026-06-01 LaTeX kernel went to\nCTAN few days ago. We encourage everybody to try it out on their documents (and\ndevelopers on their packages) so that there will be no unwanted surprises when\nthe June release hits the streets. Just run your documents with <code class=\"language-plaintext highlighter-rouge\">pdflatex-dev<\/code>\nor <code class=\"language-plaintext highlighter-rouge\">lualatex-dev<\/code> or use <code class=\"language-plaintext highlighter-rouge\">l3build check --dev<\/code> if you are a developer who uses\n<code class=\"language-plaintext highlighter-rouge\">l3build<\/code> for your packages.<\/p>\n\n<p>Further improvements have been made to the <code class=\"language-plaintext highlighter-rouge\">\\DocumentMetadata<\/code> command, with new\nkeys for language support (<code class=\"language-plaintext highlighter-rouge\">language<\/code> and <code class=\"language-plaintext highlighter-rouge\">other-languages<\/code>) which read standard\nBCP-47 strings.<\/p>\n\n<p>We have done more work on revising document command concepts in this\npre-release, with the handling of empty key\u2013value lists by\n<code class=\"language-plaintext highlighter-rouge\">\\NewDocumentCommand<\/code> adjusted to work more smoothly with a move from classical\npositional arguments.<\/p>\n\n<p>The code for block templates has been further refined to allow more fine-grained\ncustomization, and better emulation of the <code class=\"language-plaintext highlighter-rouge\">enumitem<\/code> package. There are also\nimprovements to debugging support for templates.<\/p>\n\n<p>To assist with copy-paste of text from PDFs, we have further improved\nsupport for Unicode mappings for the standard math mode fonts.<\/p>\n\n<p>A number of subtle spacing bugs in <code class=\"language-plaintext highlighter-rouge\">amsmath<\/code> have been addressed in this\npre-release: testing is strongly encouraged in this area.<\/p>\n\n<p>After a bit of consideration, we have renamed the collected documentation for\n\u2018newer\u2019 commands to <code class=\"language-plaintext highlighter-rouge\">cmdguide<\/code> (from <code class=\"language-plaintext highlighter-rouge\">latex-cmds<\/code>): this fits better with the\nlong-standing set of \u2018guide\u2019 files.<\/p>\n\n<p>As always, for full details of all of the changes planned for 2026-06-01, see\nthe draft <a href=\"\/news\/latex2e-news\/ltnews43.pdf\">LaTeX News 43<\/a>.<\/p>\n\n<p>Enjoy \u2014 Joseph<\/p>\n","pubDate":"Sun, 10 May 2026 00:00:00 +0000","link":"https:\/\/latex-project.org\/\/news\/2026\/05\/10\/latex-dev-2\/","guid":"https:\/\/latex-project.org\/\/news\/2026\/05\/10\/latex-dev-2\/","category":["latex2e","beta-testing","development formats","news"]},{"title":"New Best Practice Guide for Mathematical Content in PDF","description":"<h1 id=\"new-best-practice-guide-for-mathematical-content-in-pdf\">New Best Practice Guide for Mathematical Content in PDF<\/h1>\n\n<p>The PDF Association has released the first edition of the <a href=\"https:\/\/pdfa.org\/resource\/best-practice-guide-math-in-pdf\/\">Best Practice Guide: Math in PDF<\/a>.<\/p>\n\n<p>This guide, developed by the LaTeX Project Liaison Working Group (A collaboration between the LaTeX Project and the PDF Association) provides critical recommendations for authors and publishers to ensure complex mathematical and STEM content meets accessibility requirements and assistive technology users\u2019 needs.<\/p>\n\n<p>Comments and more general discussion of Tagging of STEM documents may be sent to the PDF Association at info@pdfa.org or as discussions at the <a href=\"https:\/\/github.com\/latex3\/tagging-project\/discussions\">LaTeX project tagging site<\/a>.<\/p>\n\n<p>Enjoy \u2014 Frank<\/p>\n\n","pubDate":"Thu, 23 Apr 2026 00:00:00 +0000","link":"https:\/\/latex-project.org\/\/news\/2026\/04\/23\/PDFA-BPG-math\/","guid":"https:\/\/latex-project.org\/\/news\/2026\/04\/23\/PDFA-BPG-math\/","category":["best practice guide","accessibility","tagged PDF","PDFA","PDF\/UA-2","news"]},{"title":"PDF Association\u2019s press release: Accessible math in PDF \u2013 finally!","description":"<h1 id=\"pdf-associations-press-release-accessible-math-in-pdf--finally\">PDF Association\u2019s press release: Accessible math in PDF \u2013 finally!<\/h1>\n\n<p>We are pleased to announce that the PDF Association (PDFA) has just issued a press release highlighting the LaTeX Team\u2019s work to make accessible math in PDF a reality. With the latest developments based on PDF 2.0 and PDF\/UA\u20112, LaTeX can now automatically generate PDFs with STEM content, such as mathematics, that are truly accessible and compliant with the PDF\/UA\u20112 ISO standard. This change closes a major accessibility gap for STEM documents and opens the door to recompiling large archives of existing LaTeX\u2011based PDFs in an accessible form.<\/p>\n\n<p>If you followed our work in the <a href=\"https:\/\/latex3.github.io\/tagging-project\/\">Tagging Project<\/a> then this isn\u2019t really news for you, but it\u2019s especially gratifying to see our work appreciated and recognized by the broader community, and it is encouraging that the industry is embracing these standards more and more.<\/p>\n\n<p>In particular, Firefox is now capable (with release 148) to correctly interpret PDFs that are tagged and contain MathML to describe mathematical formulas, and we have high hopes that Chrome will follow soon.<\/p>\n\n<p>Learn more this in the <a href=\"https:\/\/pdfa.org\/accessible-math-in-pdf-finally\/}\">PDF Association\u2019s press release.<\/a><\/p>\n\n<p>Enjoy \u2014 Frank<\/p>\n\n","pubDate":"Thu, 05 Mar 2026 00:00:00 +0000","link":"https:\/\/latex-project.org\/\/news\/2026\/03\/05\/PDFA-press\/","guid":"https:\/\/latex-project.org\/\/news\/2026\/03\/05\/PDFA-press\/","category":["latex2e","accessibility","tagged PDF","press release","PDFA","PDF\/UA-2","news"]},{"title":"Pre-release 1 of LaTeX 2026-06-01 is available for testing","description":"<h1 id=\"pre-release-1-of-latex-2026-06-01-is-available-for-testing\">Pre-release 1 of LaTeX 2026-06-01 is available for testing<\/h1>\n\n<p>The first pre-release version for the 2026-06-01 LaTeX kernel went to CTAN few\ndays ago: it\u2019s now in TeX Live, and we hope people will test it out.<\/p>\n\n<p>Work continues on bringing more flexible and predictable design support to\ndifferent areas of the kernel: this is needed for tagged PDF output but also\nhelps more generally in making it easier to customize LaTeX.<\/p>\n\n<p>Most notably, block environments (such as lists, quotes and proofs), and\nsectioning commands (<code class=\"language-plaintext highlighter-rouge\">\\chapter<\/code>, <code class=\"language-plaintext highlighter-rouge\">\\section<\/code> and so forth) have been\nre-implemented using the template system. This means that the code is entirely\nnew if you use <code class=\"language-plaintext highlighter-rouge\">\\DocumentMetadata<\/code>. This is an area that we\u2019d particularly\nencourage interested users to test, particularly with varied package loading.\nFor the more adventurous, please try out modifying the instances (or even\nproviding additional templates)!<\/p>\n\n<p>We are now emulating all keys of the <code class=\"language-plaintext highlighter-rouge\">enumitem<\/code> package and\n<code class=\"language-plaintext highlighter-rouge\">\\usepackage{enumitem}<\/code> will simply be ignored when <code class=\"language-plaintext highlighter-rouge\">\\DocumentMetadata<\/code>is\nloaded. As this is not yet a full emulation we are very much interested in\nfeedback on things that do not work yet or work differently. Thus, please report\nissues at the <a href=\"https:\/\/github.com\/latex3\/tagging-project\/issues\">tagging project\nrepository<\/a>.<\/p>\n\n<p>Supporting work on the lower-level template and document command architecture\ncontinues, with a modification to the <code class=\"language-plaintext highlighter-rouge\">-NoValue-<\/code> concept and support for\nrecovering instance values.<\/p>\n\n<p>To help users find the various newer features, we have made a start on a single\ndocumentation file, currently called <code class=\"language-plaintext highlighter-rouge\">latex-cmds<\/code> (very much a working title).\nThis already contains the documentation for<\/p>\n\n<ul>\n  <li>Hooks (including shipout, command and generic hooks)<\/li>\n  <li>Properties<\/li>\n  <li>Sockets<\/li>\n  <li>Templates<\/li>\n<\/ul>\n\n<p>and over time we expect to add more information, first for newer features and\nthen more generally.<\/p>\n\n<p>For full details of all of the changes planned for 2026-06-01, see the draft <a href=\"\/news\/latex2e-news\/ltnews43.pdf\">LaTeX News 43<\/a>.<\/p>\n\n<p>Enjoy \u2014 Joseph<\/p>\n\n","pubDate":"Tue, 27 Jan 2026 00:00:00 +0000","link":"https:\/\/latex-project.org\/\/news\/2026\/01\/27\/latex-dev-1\/","guid":"https:\/\/latex-project.org\/\/news\/2026\/01\/27\/latex-dev-1\/","category":["latex2e","beta-testing","development formats","news"]},{"title":"LaTeX 2025-11-01 released and distributed","description":"<h1 id=\"latex-2025-11-01-release-distributed\">LaTeX 2025-11-01 release distributed<\/h1>\n\n<p>We sent the 2025-11-01 release of the LaTeX kernel to CTAN last weekend. By\nnow, it\u2019s available to users in TeX Live and MiKTeX.<\/p>\n\n<h2 id=\"news-from-the-tagging-project\">News from the tagging project<\/h2>\n\n<p>The tagging project remains the major focus of the team, and in this release\nwe have extended what happens when you give the command <code class=\"language-plaintext highlighter-rouge\">\\DocumentMetadata<\/code>.\nThis now <em>always<\/em> loads the new code we are working on in <code class=\"language-plaintext highlighter-rouge\">latex-lab<\/code>. Tagging\nremains opt-in, still needing<\/p>\n<div class=\"language-latex highlighter-rouge\"><div class=\"highlight\"><pre class=\"highlight\"><code><span class=\"k\">\\DocumentMetadata<\/span><span class=\"p\">{<\/span>lang = ..., tagging = on<span class=\"p\">}<\/span>\n<\/code><\/pre><\/div><\/div>\n\n<p>We have worked across the tagging codebase, extending tagging sockets,\nnormalizing key names and starting on support for contexts (for example\nlinked to font size).<\/p>\n\n<p>For better math tagging, we now support intent attributes: these allow for\nexample <code class=\"language-plaintext highlighter-rouge\">|x|<\/code> to be read as more than \u2018bar x bar\u2019. Also notable for math\nmode is that we have fixed an issue with tabular cells: these now get the\ncorrect MathML representation.<\/p>\n\n<h2 id=\"other-improvements-and-changes\">Other improvements and changes<\/h2>\n\n<p>The <a href=\"\/news\/latex2e-news\/ltnews42.pdf\">newsletter<\/a>\nalso covers various other small enhancements or corrections that we provide\nwith the November release.<\/p>\n\n<p>Enjoy \u2013 Joseph<\/p>\n","pubDate":"Tue, 11 Nov 2025 00:00:00 +0000","link":"https:\/\/latex-project.org\/\/news\/2025\/11\/11\/issue42-of-latex2e-released\/","guid":"https:\/\/latex-project.org\/\/news\/2025\/11\/11\/issue42-of-latex2e-released\/","category":["latex2e","news"]},{"title":"Accessibility of STEM documents - talk at PDF days 2025 in Berlin","description":"<h1 id=\"accessibility-for-stem-documents---talk-at-pdf-days-2025-in-berlin\">Accessibility for STEM documents - talk at PDF days 2025 in Berlin<\/h1>\n\n<p>In September, Ulrike, Joseph, and I attended PDF Days in Berlin to present our work on making complex STEM documents truly accessible. The core message: PDF\/UA-1 simply isn\u2019t designed for mathematics, so marking documents as \u201ccompliant\u201d doesn\u2019t mean they\u2019re actually usable by people with disabilities. PDF\/UA-2, on the other hand, handles math properly through MathML support\u2014it\u2019s the standard that actually works for STEM.<\/p>\n\n<p>The challenge is industry support. PDF\/UA-2 is relatively new, so tools and workflows are still catching up. But there\u2019s progress: several hundred LaTeX packages are now compatible with accessible output generation and an end-to-end workflow exist, meaning researchers and technical writers can start to produce accessible documents with minimal extra configuration. And doing so will hopefully push industry adoption further along.<\/p>\n\n<p>The talks are <a href=\"https:\/\/pdfa.org\/presentation\/tagged-and-accessible-pdf-with-latex-revisited\/\">now online<\/a>. Beyond my presentation, there are several worth checking out if accessibility in PDF matters to your work.<\/p>\n\n<p>One note on the recording: you\u2019ll notice I restart the audio output in my examples several times, insisting it wasn\u2019t working. The irony is that the speech recorded perfectly\u2014it was the conference room microphone that failed in real-time. Lesson learned: even at accessibility-focused events, the technology doesn\u2019t always cooperate.<\/p>\n\n<p>We also presented a poster on the topic, which is now <a href=\"https:\/\/pdfa.org\/the-winning-technical-poster-at-pdf-days-europe-2025\/\">also available online<\/a> together with a few others.<\/p>\n\n<p>Enjoy \u2014 Frank<\/p>\n\n","pubDate":"Thu, 30 Oct 2025 00:00:00 +0000","link":"https:\/\/latex-project.org\/\/news\/2025\/10\/30\/pdfadays\/","guid":"https:\/\/latex-project.org\/\/news\/2025\/10\/30\/pdfadays\/","category":["accessibility","tagged PDF","PDFA","news"]},{"title":"Pre-release 3 of LaTeX 2025-11-01 is available for testing","description":"<h1 id=\"pre-release-3-of-latex-2025-11-01-is-available-for-testing\">Pre-release 3 of LaTeX 2025-11-01 is available for testing<\/h1>\n\n<p>The final pre-release version for the 2025-11-01 LaTeX kernel went to CTAN few\ndays ago: it\u2019s now in TeX Live, and we hope people will test it out.<\/p>\n\n<p>As with previous recent releases, the major focus here is tagging: we are\nimproving the code in various places, and moving from \u2018development\u2019 to\n\u2018production ready\u2019 status for tagging - at least if you are using a supported\nsubset of packages.<\/p>\n\n<p>Beyond tagging, we\u2019ve taken the opportunity to address some long-standing\noddities in the kernel. In particular, <code class=\"language-plaintext highlighter-rouge\">\\newcommand<\/code> now avoids making <code class=\"language-plaintext highlighter-rouge\">\\long<\/code>\nmacros if there are no arguments to be collected. This one needs developers to\ntest it: please try out your files using <code class=\"language-plaintext highlighter-rouge\">latex-dev<\/code>! There are as always a\ncollection of bug-fixes too: it is not impossible that these corrections affect\npackage code.<\/p>\n\n<p>For full details of all of the changes planned for 2025-11-01, see the draft <a href=\"\/news\/latex2e-news\/ltnews42.pdf\">LaTeX News 42<\/a>.<\/p>\n\n<p>Enjoy \u2014 Joseph<\/p>\n\n","pubDate":"Thu, 09 Oct 2025 00:00:00 +0000","link":"https:\/\/latex-project.org\/\/news\/2025\/10\/09\/latex-dev-3\/","guid":"https:\/\/latex-project.org\/\/news\/2025\/10\/09\/latex-dev-3\/","category":["latex2e","beta-testing","development formats","news"]},{"title":"LaTeX 2025-06-01 released and distributed","description":"<h1 id=\"latex-2025-06-01-release-distributed\">LaTeX 2025-06-01 release distributed<\/h1>\n\n<p>We sent the 2025-06-01 release of the LaTeX kernel to CTAN over the weekend. It\nwill be appearing to most users <em>via<\/em> TeX Live about now, and shortly in\nMiKTeX.<\/p>\n\n<h2 id=\"news-from-the-tagging-project\">News from the tagging project<\/h2>\n\n<p>Work continues on the tagging project, and this release sees major work on\ntagging mathematics, with automatic generation of MathML now available in\nLuaTeX. The MathML can then be used as an Associated File (AF) for PDF 2.0\noutput: a big step in providing accessible mathematics. There are (as usual)\nsome caveats at present, but for many cases, this is already very usable.<\/p>\n\n<p>Tagging is now easier to turn on, as we\u2019ve improved the keys to\n<code class=\"language-plaintext highlighter-rouge\">\\DocumentMetadata<\/code>: all you need now is<\/p>\n<div class=\"language-latex highlighter-rouge\"><div class=\"highlight\"><pre class=\"highlight\"><code><span class=\"k\">\\DocumentMetadata<\/span><span class=\"p\">{<\/span>lang = ..., tagging = on<span class=\"p\">}<\/span>\n<\/code><\/pre><\/div><\/div>\n<p>This change emphasises that we are now at the stage where a tagging is becoming\nless experimental and more routinely-usable.<\/p>\n\n<p>We\u2019ve adjusted the standard PDF output: it\u2019s now PDF 2.0 when tagging. That\u2019s\nbecause PDF 2.0 is much better for tagging than PDF 1.<i>x<\/i>: but  you can\nstill request the older output format.<\/p>\n\n<p>Other improvements in tagging are there, of course, most notably addressing\nsome spacing oddities following display math mode.<\/p>\n\n<h2 id=\"improving-marks-and-output-routine\">Improving marks and output routine<\/h2>\n\n<p>A few releases ago, we integrated a new marks mechanism into the kernel, but\nleft the classical approach available as a separate code path. That has now\nbeen addressed: the older interfaces now use the new mechanism, and multiple\nmark classes can be used with, for example, <code class=\"language-plaintext highlighter-rouge\">multicol<\/code>.<\/p>\n\n<p>The marks code was originally developed many (many) years ago as part of work\non a new output routine (OR). Whilst today we don\u2019t plan quite such radical\nchanges, we are improving the OR. To support accessibility, we need to\nintegrate a number of hooks, and this is an opportunity to refactor the OR to\nuse the socket\/plug approach. This should make the OR much easier to control\nwithout needing to completely replace it.<\/p>\n\n<h2 id=\"other-improvements-and-changes\">Other improvements and changes<\/h2>\n\n<p>The <a href=\"\/news\/latex2e-news\/ltnews41.pdf\">newsletter<\/a>\nalso covers various other small enhancements or corrections that we provide\nwith the June release.<\/p>\n\n<p>Enjoy \u2013 Joseph<\/p>\n","pubDate":"Mon, 02 Jun 2025 00:00:00 +0000","link":"https:\/\/latex-project.org\/\/news\/2025\/06\/02\/issue41-of-latex2e-released\/","guid":"https:\/\/latex-project.org\/\/news\/2025\/06\/02\/issue41-of-latex2e-released\/","category":["latex2e","news"]}]}}