[pdftex] pdftex manual LaTeX conversion for 2024

Karl Berry karl at freefriends.org
Tue Jan 9 00:53:00 CET 2024


Hi Ulrike,

    I couldn't test everything as I'm missing some input files 

I made an error in the Makefile about making incl/pdfmin-fmt.pdf (should
be fixed now). If something else is missing, let me know.  My intent was
to have everything needed to remake the doc in the repo.

    but it looks basically "taggable". 

I had tried it too, by adding:
\DocumentMetadata{testphase={phase-III,firstaid}}
before the \documentclass. Should I use a different command?

I got many warnings about
Package tagpdf Warning: The structure Sect can not be closed.
and other things, ending with a fatal error. I gave up. (My log attached.)

By the way, the first warning is
  Package hyperref Warning: Option 'ocgcolorlinks' is unknown or deprecated...
but I don't specify that option; I suppose it's a hyperref default.
Seems like some sort of hyperref/tagging clash. Maybe a candidate for
firstaid?

    In both cases a \par is missing before the group is closed:

It's just a {verbatim} block. Is inserting such a
unnecessary-for-normal-output \par going to be a requirement forever?
That would be painful. Anyway, ok, I went ahead and inserted it.

\myverbatim just uses the standard command \verbatiminput. Why isn't
that taggable as is? Being in a group seems immaterial in that case.
Not that I know anything.

    The primitive \moveright /\hbox construction gives a faulty
    structure. 

Yeah, not surprising. What do you suggest? I want the output to look
right.  I just did the simplest thing that came to mind.  Is there a way
to make such code invisible to tagging? The precise position on the page
is not relevant for an accessible reader, after all. And the whole thing
is for an inaccessible image anyway.

    The faked headings in the licence aren't perfect either.

Indeed. I just copied the FSF's file. If I get enough energy, I'll
change them to normal subsections. (I tried commenting it out, but the
myriad errors persisted.) --thanks, karl.


P.S. Is there a document/web page/q&a somewhere about "here are the
errors you're likely to get when tagging, and here's what to do about
them"?  I get errors with pretty much every real document, and I don't
know what to do about them. I'm not going to research every error from
scratch, nor do I want to bother you with every error, nor are the
answers at all apparent. For instance, I could never guess that a
gratuitous \par was needed.

I wrote the pdftex manual as generically as I could manage, except for
that one irritating \moveright I used at the end.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pdftex.log.gz
Type: application/octet-stream
Size: 6571 bytes
Desc: not available
URL: <https://tug.org/pipermail/pdftex/attachments/20240108/b52695bf/attachment.obj>


More information about the pdftex mailing list.