Unexpected results from html/markdown conversions for arrow character. about pandoc HOT 7 CLOSED

By the way, the reason I use --strict is only to prevent the insertion of JavaScript in the HTML output (to obscure
email addresses I assume, it is really not documented anywhere?). Would perhaps be nice with an cmd line option
for disabling this.

Google Code Info:
Author: [email protected]
Created On: 2008-10-22T20:59:22.000Z

from pandoc.

Conversion from html to markdown seems fine here. The problem is in the conversion
from markdown to html with --strict:

% pandoc --strict
This is a line of < text and more > text.

This is a line of text.</p

I'll look into it.

Your request for more command-line control over email obfuscation is a reasonable
one. Could I ask you to file a separate issue for that, so I can keep track of it?

Google Code Info:
Author: [email protected]
Created On: 2008-10-22T21:32:01.000Z

from pandoc.

Thanks for your quick comment.

Ok, but according to http://daringfireball.net/projects/markdown/syntax (see bottom of page) - it seems that <
does not need escaping to < in markdown.

Google Code Info:
Author: [email protected]
Created On: 2008-10-22T21:44:16.000Z

from pandoc.

Sure enough. Escaping rules are somewhat different in pandoc than in strict
markdown: see http://johnmacfarlane.net/pandoc/README.html#backslash-escapes

So in --strict mode, pandoc's markdown writer should not backslash-escape '<'.
That's one part of the problem. The other part is that pandoc is parsing '< text and
more >' as an HTML tag (that's why the spaces disappear).

Google Code Info:
Author: [email protected]
Created On: 2008-10-22T23:01:10.000Z

from pandoc.

Google Code Info:
Author: [email protected]
Created On: 2008-11-02T17:03:45.000Z

from pandoc.

The escaping issue solved in r1600.

The whitespace issue is one I can't figure out how to address without making pandoc's
acceptance of html-ish tags less liberal. (Currently it is not restricted to
official html tags, and it allows attributes without values, so your example looks
like a tag to it.) So I'm going to leave this as it is for now.

Google Code Info:
Author: [email protected]
Created On: 2009-07-18T19:16:59.000Z

from pandoc.

Understood - and thanks a lot for your continued work on improving pandoc, and for paying attention to the
details.

Google Code Info:
Author: [email protected]
Created On: 2009-07-20T19:02:30.000Z

from pandoc.