we'd have to store marked up content as converted HTML (easy) and then convert the HTML back to markup at editing time (hard). Hard to constrain to markup-friendly HTML only and avoid losing info in process.

 

I'd probably just lean towards a cardtype. # of users requesting markup is small. # requesting both means of editing for a given card...  hardly any right?

 

--Ethan

---

The biggest problem with using cardtypes is it makes it impossible for it to be a user preference. If it's a Markdown card, everyone has to use Markdown when editing it. Also, don't we want to go in the direction of fewer cardtypes, and show different editors by other means? (e.g. Pointers' *input does now, and we've talked about merging Phrase and Plaintext)

 

Regarding losing info, are you thinking we allow HTML that may not have corresponding markup? Markdown allows arbitrary HTML, and among the varied wiki markup languages I imagine we could research or develop similar functionality.

  --John Abbe.....Mon Aug 30 14:25:28 -0700 2010

---

Book on Markdown, may be helpful for someone who wants to really dig into it: http://macsparky.com/markdown/

  --John Abbe.....2013-03-25 03:29:44 +0000