This is the exact point that I’m (unsuccessfully?) trying to make. While I would love to see more of Tinderbox’s features applied to exported Markdown notes (links! it’s always about links!! ), I don’t think it’s as simple as “run Tinderbox’s normal export process and then pipe it to markdown,” because Tinderbox and Markdown use some of the same syntax to represent different things. I used the quicklist as one example, where it may be difficult to divine the author’s intent – do they want a Tinderbox quicklist, or a series of HTML headers?
That is just one specific syntax example, maybe there are others, I’m not sure. In any case, if eastgate has any interest in making Markdown export richer, they will need to account for the interplay between Tinderbox export syntax and Markdown syntax.
Well, anyone who posts on this forum is using Markdown It might be more common among the Tinderbox user community than you suspect.
), I don’t think it’s as simple as “run Tinderbox’s normal export process and then pipe it to markdown,” because Tinderbox and Markdown use some of the same syntax to represent different things. I used the quicklist as one example, where it may be difficult to divine the author’s intent – do they want a Tinderbox quicklist, or a series of HTML headers?