Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error raised with simplest custom line style not using \par #9

Closed
jfbu opened this issue Jan 11, 2024 · 0 comments
Closed

Error raised with simplest custom line style not using \par #9

jfbu opened this issue Jan 11, 2024 · 0 comments
Labels
at-2024-01-02 2024-01-02 has the issue at-2024-01-03 2024-01-03 has the issue at-2024-01-05 2024-01-05 has the issue fixed-at-2024-01-12 Fixed at 2024-01-12 tag tagging Relative to support of the `LaTeX tagged PDF` project

Comments

@jfbu
Copy link
Owner

jfbu commented Jan 11, 2024

Document using

\etocsetstyle{section}
  {}
  {\etocname, }% no error if a \par here
  {}
  {}% no error if a \par here

%\def\etocaftercontentshook{\par}% no error if using this

\tableofcontents
\section{foo}
\end{document}

generates on second compilation warnings then errors with

! Package tagpdf Error: The number of automatic begin (2) and end (3)
(tagpdf)                text-unit para hooks differ!

@jfbu jfbu added tagging Relative to support of the `LaTeX tagged PDF` project at-2024-01-02 2024-01-02 has the issue labels Jan 11, 2024
jfbu added a commit that referenced this issue Jan 11, 2024
! Package tagpdf Error: The number of automatic begin (2) and end (3)
(tagpdf)                text-unit para hooks differ!

	new file:   gh9_error_if_no_par_is_used.tex
@jfbu jfbu added at-2024-01-03 2024-01-03 has the issue at-2024-01-05 2024-01-05 has the issue labels Jan 11, 2024
@jfbu jfbu changed the title error raised with simplest custom line style not using \par Error raised with simplest custom line style not using \par Jan 11, 2024
@jfbu jfbu closed this as completed in 393e210 Jan 11, 2024
@jfbu jfbu added at-2024-01-02 2024-01-02 has the issue at-2024-01-03 2024-01-03 has the issue and removed at-2024-01-02 2024-01-02 has the issue at-2024-01-03 2024-01-03 has the issue labels Jan 11, 2024
jfbu added a commit that referenced this issue Jan 12, 2024
Matters of the para-tagging boolean here.
jfbu added a commit that referenced this issue Jan 12, 2024
Make them \protected.  Add a demo file, in the same spirit as the TOC as
molecule examples: \tableofcontents serves only to build a \foo macro
which is then expanded later.
@jfbu jfbu added the fixed-at-2024-01-12 Fixed at 2024-01-12 tag label Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
at-2024-01-02 2024-01-02 has the issue at-2024-01-03 2024-01-03 has the issue at-2024-01-05 2024-01-05 has the issue fixed-at-2024-01-12 Fixed at 2024-01-12 tag tagging Relative to support of the `LaTeX tagged PDF` project
Projects
None yet
Development

No branches or pull requests

1 participant