Re: Interaction of org-mode and Muse

"Patrick Hawkins" <[email protected]> writes:

> Only slightly off-topic, I have a few, probably not so serious
> reservations about putting Markdown support into Muse. Markdown was
> designed to be converted into (X)HTML only, and thus many little
> decisions must have gone into the design of Markdown that, whilst
> making transitions into HTML fantastic, probably provide some thorny
> issues for integration with Muse. For example, <lisp> tags. Markdown
> allows for valid XHTML tags, but throw in anything crazy like that
> and it will cease to be a generic, parses-anywhere Markdown
> document. If we're trying to serve those who use Markdown on a
> regular basis, and ease their transition to Muse, it would be well
> for those we serve to maintain integration with their other Markdown
> workflow. If they are comfortable switching their workflow entirely,
> then I suppose this isn't as much of an issue, but there are
> numerous (maybe even tens of) tools that parse Markdown and would
> choke on a Muse/Markdown hybrid.

I don't understand why this is an issue.  If someone wants to preserve
compatibility with Markdown in their document, all they have to do is
use only Markdown-specific markup.  If there is a concern that someone
might unknowingly use Muse-specific markup, would it be sufficient to
just throw an optional warning message at them?

-- 
Michael Olson -- FSF Associate Member #652 -- http://www.mwolson.org/
Interests: Emacs Lisp, text markup, protocols -- Jabber: mwolson_at_hcoop.net
  /` |\ | | | IRC: mwolson on freenode.net: #hcoop, #muse, #PurdueLUG
 |_] | \| |_| Project involvement: Emacs, Muse, Planner, ERC, EMMS

_______________________________________________
emacs-wiki-discuss mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/emacs-wiki-discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFEUMue+1Ho2POo0xkRAkJEAJsFQq6n6VLG9RE+igHultBb32krPwCfRFe1
fdRgpNf7NgINka88t7k3LJ4=
=9cGO
-----END PGP SIGNATURE-----