projects:markdownprocessors
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
projects:markdownprocessors [2014/06/23 08:03] – rlunaro | projects:markdownprocessors [2016/05/22 12:54] (current) – removed rlunaro | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Broad Analisys of markdown processors ====== | ||
- | |||
- | ===== Intro ===== | ||
- | |||
- | Markdown rocks. If you look on google the term " | ||
- | |||
- | ===== What is markdown?? ===== | ||
- | |||
- | According to [[http:// | ||
- | |||
- | // | ||
- | allows you to write using an easy-to-read, | ||
- | // | ||
- | |||
- | In other words, you can write something similar to a normal plain text document, and with | ||
- | this tool you can get a valid web document (html document). | ||
- | |||
- | **What are the advantages?? | ||
- | |||
- | From a technical point of view, I think that the advantages are many: | ||
- | |||
- | * **Clean format:** The original documents are plain text, and perfectly readable as they are. So, the human bodies out there can read it as is, understand them and change them. However, the html results are better reading, of course. | ||
- | * **Easy to process:** As the original documents are plain text, automatic processing of these documents (scanning, searching, changing them by a program) are fairly simple. Comparing in search of changes are easily made also with well know tools (winmerge, diff, fc to mention some of them) and to store properly in source code control systems (like github, cvs, git, subversion). A perfect example [[https:// | ||
- | * **Durability: | ||
- | |||
- | **And the disadvantages?? | ||
- | |||
- | * **Lack of standards: | ||
- | * **Lack of features:** In general, many of the markdown processors I've ever seen lack some features that could be interesting: | ||
- | * Graphs: a minimal support for pie charts, bar charts and line charts would be desirable, altough I find it difficult to implement and to describe using plain text | ||
- | * Diagrams: there is no support for diagrams (although some processors have implemented some sort of support). Again, a problem because it forces you to support this documents in propietary tools and then translate it to images. | ||
- | * **Lots of implementations: | ||
- | |||
- | ===== Some of the tools I've seen and my opinion ===== | ||
- | |||
- | |||
- | |||
- | [[http:// | ||
- | |||
- | Written in Perl. | ||
- | |||
- | [[https:// | ||
- | |||
- | It appears to be one of the most feature rich implementations of markdown: [[http:// | ||
- | |||
- | [[https:// | ||
- | |||
- | [[http:// | ||
- | |||
projects/markdownprocessors.1403510580.txt.gz · Last modified: 2022/12/02 21:02 (external edit)