http://www.giuspen.com/topic/req-markdown-and-evernote/ wrote:The first issue I’ve found is that the generated output.html format must be parsed to be imported back into CherryTree as acceptable html for rendering.
e.g. markdown generated tag <strong>markdown output</strong> is not recognised by CherryTree and needs to be changed to <b>markdown output</b>
If I recall correctly, the first encoding is generally viewed as superior to CherryTree's implementation, from a distinction between mere formal mark up -- "bold this text", a practice denominated "What You See Is What You Get" that usually results in what some experts call "tag soup" -- and a more grounded approach to semantically sound mark up -- "highlight this text", an evolution towards best practices usually summed up as "What You Mean Is What You Get".
Whether it might be argued that, in the end, the results are the same in both cases, making this a matter of no substance, it saddens me deeply witnessing such a step back enforced through code by a respected developer... in a least denominator solution, both forms should be accepted.