-
Notifications
You must be signed in to change notification settings - Fork 18
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
Move from plaintext to markdown #26
Comments
We have considered this but decided against it. RFC format is great to read. I proposed a xml2rfc.md though. I think that would be really nice. |
If someone can find a way to make xml2rfc output in Markdown that would be a good addition, but I still think we should at least continue to have .txt and .xml. |
I would prefer to keep any unnecessary files out of the repo. Either provide a link to a formatter in the README, or put the markdowns in the wiki. |
markdowns could go in the wiki very well. But we do not know how to convert the xml to markdown yet :) |
I just took a quick look at the XML; it should be no problem at all to write a small SAX-based converter. I'll try to write one later this day, currently I need to do some other things ;) And when I'm already doing this, I can also add LaTeX output (I really like LaTeX, because the documents are very good to read and annotate) |
With #32 we can probably close this. |
I think the specs should be written in markdown, rather than plaintext. This would make it all look prettier, but if you really need to see the plaintext file, the markdown source is still easy to read.
The text was updated successfully, but these errors were encountered: