-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
list-table support for conversion ReST files #3432
Comments
This should be pretty easy to implement. However,
I note that the RST reader seems to have a bug in
recognizing this kind of list, which would need to
be fixed too.
|
Here's a test case for the bug mentioned above:
|
See #3432. Previously the parser didn't handle properly this case: * - a - b * - c - d
hi, when I try to convert a ghc user guide file: https://github.com/bgamari/ghc-users-guide/blob/master/content/using-warnings.rst and I have similar error messages:
... I use a pandoc version 1.19.2.1 in a Ubuntu 16.04 64bit EC2 node. Thanks a lot. |
@gingerhot the problem here is that your document uses some custom rst directives ( One possible change would be to have pandoc emit the block-level contents of any unknown directive. So, in the |
In most cases it's better to preserve the content than to emit it. This isn't guaranteed to have good results; it will fail spectacularly for unknown raw or verbatim directives. See #3432.
In most cases it's better to preserve the content than to emit it. This isn't guaranteed to have good results; it will fail spectacularly for unknown raw or verbatim directives. See #3432.
list-table RST conversion problem
Problem description
I wanted to convert some
.rst
files and pandoc reported the following error:I went through the source file and realized that it does not recognize the list-table directive that is used by reSt to define a table.
How does that work.
The table designed by the list-table directive look like this:
Where:
..list-table::
is the beginning of the table data:widths:
define how wide each column should be:header-rows:
defines the header row (makes it bold)*
represents a new row-
represents a column in that rowThis would make the following output:
Problem solution
It would be nice, if support for understanding tables in this format could be added. Thanks.
The text was updated successfully, but these errors were encountered: