Skip to content

Commit 4c9c6f1

Browse files
FrankMittelbachFrankMittelbach
committed
various fixes amd regen
1 parent 3be0cba commit 4c9c6f1

File tree

6 files changed

+298
-104
lines changed

6 files changed

+298
-104
lines changed

‎_posts/2024-07-06-tagging.md

Lines changed: 15 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ layout: post
33
title: "How to make accessible PDF"
44
date: 2024-07-06 00:00:00
55
description: "Info on making accessible PDF"
6-
excerpt: "The "LaTeX Tagged PDF" project is now advanced enough that more and
6+
excerpt: "The LaTeX Tagged PDF project is now advanced enough that more and
77
more people start using it. We have therefore begun with building
88
usage documentation ..."
99
categories: news
@@ -19,20 +19,25 @@ repositories as this is the case at the moment.
1919

2020
For issues encountered with the project code we have added a dedicated
2121
[`tagging-project`
22-
repository](https://github.com/latex3/tagging-project) a while ago,
23-
where people can report problems and look up the current state of
22+
repository](https://github.com/latex3/tagging-project) a while ago.
23+
In this repository people can report problems and look up the current state of
2424
known issues. It is also hosting discussions related to the project.
2525

26-
We have now extended this to use GitHub pages providing a small [Web
27-
browser-friendly site](https://latex3.github.io/tagging-project/). So
28-
far this holds
26+
We have now extended this repository to use GitHub pages providing a
27+
small [number of web
28+
pages](https://latex3.github.io/tagging-project/). So far it holds
2929

3030
- Examples of Tagged PDFs conforming to the WTPDf, PDF/UA-1, and PDF
31-
- A simple documentation what to do to produce accessible PDF
31+
32+
- Guidelines on [how to produce accessible
33+
PDF](https://latex3.github.io/tagging-project/documentation/prototype-usage-instructions.html)
3234
(describing the current tempoary interfaces)
33-
- Tables the record the status of various packages and classes (i.e.,
34-
whether or not they can be used with the ned tagging code) based on
35-
the issues that are documented
35+
36+
- [Tables that record the
37+
status](https://latex3.github.io/tagging-project/tagging-status/)
38+
of various packages and classes (i.e., whether or not they can be
39+
used with the new tagging code) based on the issues that are
40+
already on record
3641

3742
This documentation and the tables are all work in progress and will
3843
get updated whenever there is new information.

‎_site/feed.xml

Lines changed: 73 additions & 81 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,82 @@
55
<description></description>
66
<link>https://latex-project.org//</link>
77
<atom:link href="https://latex-project.org//feed.xml" rel="self" type="application/rss+xml" />
8-
<pubDate>Thu, 13 Jun 2024 23:20:20 +0200</pubDate>
9-
<lastBuildDate>Thu, 13 Jun 2024 23:20:20 +0200</lastBuildDate>
8+
<pubDate>Sun, 07 Jul 2024 09:55:37 +0200</pubDate>
9+
<lastBuildDate>Sun, 07 Jul 2024 09:55:37 +0200</lastBuildDate>
1010
<generator>Jekyll v4.3.3</generator>
1111

1212
<item>
13-
<title>LaTeX 2024-061-01 PL1 released and distributed</title>
13+
<title>How to make accessible PDF</title>
14+
<description>&lt;h1 id=&quot;how-to-make-accessible-pdf&quot;&gt;How to make accessible PDF&lt;/h1&gt;
15+
16+
&lt;p&gt;The “LaTeX Tagged PDF” project is now advanced enough that more and
17+
more people start using it. We have therefore begun with building
18+
usage documentation that is not scattered across different
19+
repositories as this is the case at the moment.&lt;/p&gt;
20+
21+
&lt;p&gt;For issues encountered with the project code we have added a dedicated
22+
&lt;a href=&quot;https://github.com/latex3/tagging-project&quot;&gt;&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;tagging-project&lt;/code&gt;
23+
repository&lt;/a&gt; a while ago.
24+
In this repository people can report problems and look up the current state of
25+
known issues. It is also hosting discussions related to the project.&lt;/p&gt;
26+
27+
&lt;p&gt;We have now extended this repository to use GitHub pages providing a
28+
small &lt;a href=&quot;https://latex3.github.io/tagging-project/&quot;&gt;number of web
29+
pages&lt;/a&gt;. So far it holds&lt;/p&gt;
30+
31+
&lt;ul&gt;
32+
&lt;li&gt;
33+
&lt;p&gt;Examples of Tagged PDFs conforming to the WTPDf, PDF/UA-1, and PDF&lt;/p&gt;
34+
&lt;/li&gt;
35+
&lt;li&gt;
36+
&lt;p&gt;Guidelines on &lt;a href=&quot;https://latex3.github.io/tagging-project/documentation/prototype-usage-instructions.html&quot;&gt;how to produce accessible
37+
PDF&lt;/a&gt;
38+
(describing the current tempoary interfaces)&lt;/p&gt;
39+
&lt;/li&gt;
40+
&lt;li&gt;
41+
&lt;p&gt;&lt;a href=&quot;https://latex3.github.io/tagging-project/tagging-status/&quot;&gt;Tables that record the
42+
status&lt;/a&gt;
43+
of various packages and classes (i.e., whether or not they can be
44+
used with the new tagging code) based on the issues that are
45+
already on record&lt;/p&gt;
46+
&lt;/li&gt;
47+
&lt;/ul&gt;
48+
49+
&lt;p&gt;This documentation and the tables are all work in progress and will
50+
get updated whenever there is new information.&lt;/p&gt;
51+
52+
&lt;p&gt;If you want to help improving this, then this is easily possible. We
53+
are looking for volunteers who try out the tagging code in various
54+
ways and report problems or package incompatibilites and help with
55+
developing tests that prove or disprove that the tagging code can be
56+
used with packages for which we don’t have enough data so far.&lt;/p&gt;
57+
58+
&lt;p&gt;— Frank&lt;/p&gt;
59+
60+
</description>
61+
<pubDate>Sat, 06 Jul 2024 02:00:00 +0200</pubDate>
62+
<link>https://latex-project.org//news/2024/07/06/tagging/</link>
63+
<guid isPermaLink="true">https://latex-project.org//news/2024/07/06/tagging/</guid>
64+
65+
<category>Accessibility</category>
66+
67+
<category>tagged PDF</category>
68+
69+
<category>latex</category>
70+
71+
<category>development</category>
72+
73+
<category>PDF/UA-1</category>
74+
75+
<category>PDF/UA-2</category>
76+
77+
78+
<category>news</category>
79+
80+
</item>
81+
82+
<item>
83+
<title>LaTeX 2024-06-01 PL1 released and distributed</title>
1484
<description>&lt;h1 id=&quot;latex-2024-06-01-pl1-release-distributed&quot;&gt;LaTeX 2024-06-01 PL1 release distributed&lt;/h1&gt;
1585

1686
&lt;p&gt;We sent the 2024-06-01 release (patch level 1) of the LaTeX kernel to CTAN. By now it should be available to most users &lt;em&gt;via&lt;/em&gt; TeX Live or MiKTeX.&lt;/p&gt;
@@ -531,84 +601,6 @@ by using &lt;a href=&quot;https://amzn.to/40yY7gD&quot;&gt;Amazon.de in Germany&
531601
<category>TLC</category>
532602

533603

534-
<category>news</category>
535-
536-
</item>
537-
538-
<item>
539-
<title>Towards automated PDF tagging: Pre-release of LaTeX 2023-06-01 is available for testing</title>
540-
<description>&lt;h1 id=&quot;towards-automated-pdf-tagging-pre-release-of-latex-2023-06-01-is-available-for-testing&quot;&gt;Towards automated PDF tagging: Pre-release of LaTeX 2023-06-01 is available for testing&lt;/h1&gt;
541-
542-
&lt;p&gt;We submitted the second pre-release version for the 2023-06-01 LaTeX
543-
kernel to CTAN recently. It should have made its way into TeX Live
544-
(both 2022 and the 2023 pre-test) for everyone by now, so it’s ready
545-
for users to try.&lt;/p&gt;
546-
547-
&lt;p&gt;It does not yet contain all updates to the LaTeX format that will
548-
become part of the standard in June, but the new code already provided
549-
is worth checking out.&lt;/p&gt;
550-
551-
&lt;h2 id=&quot;automated-tagging-of-pdf-documents&quot;&gt;Automated tagging of PDF documents&lt;/h2&gt;
552-
553-
&lt;p&gt;We have now enabled new automatic tagging functionality for additional
554-
LaTeX elements, among them most display environments, standard
555-
sectioning commands and content, figure and table listings.&lt;/p&gt;
556-
557-
&lt;p&gt;This can be activated through&lt;/p&gt;
558-
&lt;div class=&quot;language-plaintext highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;\DocumentMetadata{testphase=phase-III}
559-
\documentclass{...} % article, book or report
560-
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;
561-
&lt;p&gt;In addition there is also a (very early) prototype for tagging formulas, which can be activated through&lt;/p&gt;
562-
&lt;div class=&quot;language-plaintext highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;\DocumentMetadata{testphase={phase-III,math}}
563-
\documentclass{...}
564-
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;
565-
&lt;p&gt;It offers support for LaTeX’s standard math environments but also for
566-
all environments provided through the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;amsmath&lt;/code&gt; package.&lt;/p&gt;
567-
568-
&lt;p&gt;All of this automation is currently in a prototype state and
569-
restricted to the use of standard classes (&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;article&lt;/code&gt;, &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;report&lt;/code&gt;, and
570-
&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;book&lt;/code&gt;) and it supports only a limited number of add-on package. See the
571-
draft version of the &lt;a href=&quot;/news/latex2e-news/ltnews37.pdf&quot;&gt;LaTeX2e News
572-
Issue 37&lt;/a&gt; newsletter for further details. It provides information
573-
how to submit feedback on the new functionality.&lt;/p&gt;
574-
575-
&lt;p&gt;The newsletter also covers various other small enhancements or
576-
corrections that we intend to provide with the June release.&lt;/p&gt;
577-
578-
&lt;h2 id=&quot;outlook&quot;&gt;Outlook&lt;/h2&gt;
579-
580-
&lt;p&gt;We expect to produce another pre-release around the end of April, which will
581-
give us time to finish the release by June. Please help with the testing.&lt;/p&gt;
582-
583-
&lt;p&gt;Processing your documents with the pre-release is straightforward. All you have
584-
to do is to replace the invocation command by appending &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;-dev&lt;/code&gt; to the executable,
585-
e.g., on the command line you would run&lt;/p&gt;
586-
587-
&lt;ul&gt;
588-
&lt;li&gt;&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;pdflatex-dev myfile&lt;/code&gt; or&lt;/li&gt;
589-
&lt;li&gt;&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;lualatex-dev myfile&lt;/code&gt; or&lt;/li&gt;
590-
&lt;li&gt;&lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;xelatex-dev myfile&lt;/code&gt;&lt;/li&gt;
591-
&lt;/ul&gt;
592-
593-
&lt;p&gt;instead of using &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;pdflatex&lt;/code&gt;, &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;lualatex&lt;/code&gt; or &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;xelatex&lt;/code&gt;. If you use an integrated
594-
editing environment, then it depends on the system how to configure it to use an
595-
alternative format; but in any case the necessary modification should be
596-
straightforward.&lt;/p&gt;
597-
598-
&lt;p&gt;Enjoy — Frank&lt;/p&gt;
599-
600-
</description>
601-
<pubDate>Mon, 13 Mar 2023 01:00:00 +0100</pubDate>
602-
<link>https://latex-project.org//news/2023/03/13/latex-dev-1/</link>
603-
<guid isPermaLink="true">https://latex-project.org//news/2023/03/13/latex-dev-1/</guid>
604-
605-
<category>latex2e</category>
606-
607-
<category>beta-testing</category>
608-
609-
<category>development formats</category>
610-
611-
612604
<category>news</category>
613605

614606
</item>

‎_site/index.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,9 @@ <h1>LaTeX – A document preparation system</h1>
7373
<h2>Recent News</h2>
7474
<ul class="news-posts">
7575

76-
<li><span class="post-date">13 June, 2024</span><a class="post-link" href="/news/2024/06/13/issue39-of-latex2e-released/">LaTeX 2024-061-01 PL1 released and distributed</a></li>
76+
<li><span class="post-date">6 July, 2024</span><a class="post-link" href="/news/2024/07/06/tagging/">How to make accessible PDF</a></li>
77+
78+
<li><span class="post-date">13 June, 2024</span><a class="post-link" href="/news/2024/06/13/issue39-of-latex2e-released/">LaTeX 2024-06-01 PL1 released and distributed</a></li>
7779

7880
<li><span class="post-date">24 April, 2024</span><a class="post-link" href="/news/2024/04/24/l3prog-dev/">Development releases for the L3 Programming Layer</a></li>
7981

@@ -85,8 +87,6 @@ <h2>Recent News</h2>
8587

8688
<li><span class="post-date">4 November, 2023</span><a class="post-link" href="/news/2023/11/04/issue38-of-latex2e-released/">LaTeX 2023-11-01 released and distributed</a></li>
8789

88-
<li><span class="post-date">10 June, 2023</span><a class="post-link" href="/news/2023/06/10/issue37-of-latex2e-released/">LaTeX 2023-06-01 released and distributed</a></li>
89-
9090
</ul>
9191
<small><a href="/news/">All News</a> &middot; Subscribe to our <a href="/feed.xml"><span class="fa fa-rss-square"></span>RSS News Feed</a></small>
9292
</div>

‎_site/news/2024/06/13/issue39-of-latex2e-released/index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
<head>
44
<meta charset="utf-8">
55
<meta http-equiv="X-UA-Compatible" content="IE=edge">
6-
<title>LaTeX 2024-061-01 PL1 released and distributed</title>
6+
<title>LaTeX 2024-06-01 PL1 released and distributed</title>
77
<meta name="description" content="We sent the 2024-06-01 release (patch level 1) of the LaTeX kernel to CTAN. By now it should be available to most users via TeX Live or MiKTeX....">
88
<meta name="viewport" content="width=device-width">
99
<link rel="stylesheet" href="/css/screen.css">

0 commit comments

Comments
 (0)