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

HTML Tables with 10+ columns are broken for LaTeX based output (Origin: bugzilla #766787) #6009

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.11 on platform Other
Assigned to: Dimitri van Heesch

On 2016-05-23 11:11:53 +0000, Daniel G. wrote:

If you generate PDF with LaTeX output and use HTML to describe tables (because you need e.g. colspan), the generated LaTeX code using tabu is corrupted.

This is due to the fact, that you need to embrace counts with more than two digits with {}. Simply adding this curly braces to the tex output perfectly works.

Does not work (original generated TeX):
\begin{longtabu} spread 0pt [c]{*17{|X[-1]}|}

Does work (manually fixed version):
\begin{longtabu} spread 0pt [c]{*{17}{|X[-1]}|}

This is especially frustrating, because you need to use HTML tables if you want to use colspan, and colspan is a good reason to require more than 9 culumns...

On 2016-05-23 17:47:30 +0000, albert wrote:

I've just pushed a proposed patch to github (pull request 481)

On 2016-05-23 19:08:38 +0000, Dimitri van Heesch wrote:

Thanks, I've merged the pull request

On 2016-09-05 13:45:30 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.12. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment