We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Bodies mostly use HTML in e-mail these days clients (thanks MS Outlook365) love using rich markup and all the pitfalls it brings
Today's issue is Tables where they can get pretty messy and long -
But RTK seems to convert them into ASCII tables without using pre tags etc. ?
pre
The rendering uses a lot of space from left and right and only 30% hozirontal space is used and doesn't help rendering tables
It just might be that extending the rendering to 100% would render the ascii table OK in pre-blocks.
Long run might just render them as HTML tables.
The text was updated successfully, but these errors were encountered:
Hi @pinkforest could you add a link to a request where this has happened recently?
Sorry, something went wrong.
Example Request: https://www.righttoknow.org.au/request/strike_it_out_documentation_stri#incoming-35834
No branches or pull requests
Bodies mostly use HTML in e-mail these days clients (thanks MS Outlook365) love using rich markup and all the pitfalls it brings
Today's issue is Tables where they can get pretty messy and long -
But RTK seems to convert them into ASCII tables without using
pre
tags etc. ?The rendering uses a lot of space from left and right and only 30% hozirontal space is used and doesn't help rendering tables
It just might be that extending the rendering to 100% would render the ascii table OK in pre-blocks.
Long run might just render them as HTML tables.
The text was updated successfully, but these errors were encountered: