-
Notifications
You must be signed in to change notification settings - Fork 1
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
Create LaTeX version #8
Comments
The point in time to switch is for me personally not that important. Wait until stable (more or less) seems to be easier upfront, where switching now may save time later on... Or switch to HTML instead of LaTeX, leaving out the intermediate step of generating a PDF? Although, the macros really seem useful. I have no preference in both regards. |
Not sure if I overlooked it or it was added recently, but the allowed formats (now) are:
Sooo... no need to convert anything!? We just rename (P-number) the document and make sure it adheres to Commonmark and be done with it. Your thoughts on this? |
The Commonmark specification does not allow tables at the moment. I am not sure if this is a strict prerequisite. However, tools like Pandoc or Github's own renderer allow to easily convert Markdown to HTML or other formats. |
(That said, I think we should continue using Markdown at the moment.) |
To submit the proposal, it has to be in [HTML or PDF format](https://isocpp.org/std/standing-documents/sd-7-mailing-procedures-and-how-to-write-papers. For the latter, the repository of the C++ standard draft can be used to take a lot of macros.
Personally (@nlohmann), I think we should only take the effort to switch to LaTeX once the proposal stabilizes, because it seems to be a lot of effort to understand all the (definitly useful) commands and environments used in the standard LaTeX template.
The text was updated successfully, but these errors were encountered: