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

Single-columned Markdown tables (Origin: bugzilla #681874) #4850

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2012-08-14 18:59:01 +0000, Bastiaan wrote:

The following is not recognised as a table:

Instellingen & diversen
1. \ref special_points
2. etc.

I believe this is valid Markdown format.

Best regards,

On 2013-04-01 11:43:00 +0000, albert wrote:

Created attachment 240298
A more extensive test file

The file aa.c is a more extensive test file with 1 and 2 columns

On 2013-04-01 11:46:19 +0000, albert wrote:

Created attachment 240299
PATCH: enable single columns tables

With this patch it is possible to specify single column tables as well. The table rows have to start and end with a | (pipe symbol).

This is done by setting an extra variable to 1 in case the findTableColumns routine find 1 column and this line starts and end with a |. In the rest of the code this extra variable is considered as well in the tests.

On 2013-05-11 15:16:43 +0000, Dimitri van Heesch wrote:

Thanks, I'll include a slightly simplified version of the patch in the next subversion update.

On 2013-05-19 12:35:53 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.4. 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.

@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