full.md

title
LaTeX package/class tagging status

<style> td.compatible {background-color: #DDFFDD55;font-weight:bold;} td.partially-compatible {background-color: #FFFFDD55;font-weight:bold;} td.no-support {background-color: #FFDDDD55;font-weight:bold;} td.currently-incompatible {font-weight:bold;} td.unknown {background-color: #FFEE9955;font-weight:bold;} td.date {white-space: nowrap;font-size:90%;} .markdown-body table tr { vertical-align: baseline;} .markdown-body table thead tr { border-bottom: solid thick black;} .markdown-body table p { margin-bottom: 0pt;} </style> <script src="sorttable.js"></script>

Tagging Status of LaTeX Packages and Classes

{% assign t-s = site.data.tagging-status %}

This file shows the status of {{t-s | size }} LaTeX Packages and Classes with respect to PDF tagging. phase-III is generally needed and not explicitly shown.

This is the full list of data in the YAML file. Revert to the filtered tables of compatible or higher priority classes and packages.

The values in the Status column have the following meaning:

• compatible This package or class works without any issues when tagging is enabled. If there are problems, please open an issue in the tagging-project repo. ({{t-s | where: "status", "compatible" | size }} entries)
• partially-compatible The package or class is currently partially compatible, e.g., some parts may not work yet, but with some restrictions it can already be used. See comments for details. ({{t-s | where: "status", "partially-compatible" | size }} entries)
• currently-incompatible The package or class is currently incompatible with the tagging code, but we expect it to be updated eventually. ({{t-s | where: "status", "currently-incompatible" | size }} entries)
• no-support This package or class or class is incompatible with the tagging code and we do not believe that it will ever be supported. ({{t-s | where: "status", "no-support" | size }} entries)
• unknown The status of this package or class is not known, because there aren't reliable tests yet. Help with testing to determine the real status is very much appreciated. ({{t-s | where: "status", "unknown" | size }} entries)

Click on the column headings to sort the table by the chosen column.

{%- for p in t-s -%} {%- endfor -%}

Type	Name	Status	TLC3	ArXiv %	Priority	Comments	Relevant issue(s)	Tasks	Last updated
{{p.type}}	{{p.name}}	{{p.status}}	{% if p.included-in contains "tlc3" %}TLC3{% endif %}	{%- if p.included-in contains "arxiv10" %}10{% endif -%} {%- if p.included-in contains "arxiv5" %} 5{% endif -%} {%- if p.included-in contains "arxiv1" %} 1{% endif -%} {%- if p.included-in contains "arxiv01" %}0.1{% endif -%} {%- if p.included-in contains "arxiv001" %}0.01{% endif -%}	{{p.priority}}	{{p.comments | markdownify}} {%- if p.references %} See {% for r in p.references %} [{{r}}] {% endfor %} {%- endif -%} {%- if p.supported-through -%} Tagging support: {% for t in p.supported-through %} {%- if t == "package" and p.package-repository -%} {{t}} {%- else -%} {{t}} {%- endif -%} {%- unless forloop.last -%}, {% endunless -%} {%- endfor %}. {%- endif -%}	{%- if p.issues -%} {% for i in p.issues %} #{{i}} {% endfor %} {%- endif -%} {% if p.related-issues %} {%- if p.issues -%} {%- endif -%} Related: {% for i in p.related-issues %} #{{i}} {% endfor %} {% endif %} {% if p.external-issues %} {%- if p.issues or p.related-issues -%} {%- endif -%} Other: {% for u in p.external-issues %} {%- assign ltext = u | replace: "issues/", "" | replace: "-/","" | split: "/" -%} {{ltext | slice: -2}}/{{ltext | slice: -1}} {% endfor %} {% endif %} {% if p.tests %} test(s) {% endif %}	{{p.tasks | markdownify}}	{{p.updated}}

---

References

{% for r in site.data.references %}

{{r.number}}. {{r.authors}}. {{r.title}}

{% endfor %}