Dom Christie

Thanks for this. My only concern is naming. The command should probably match the existing API. However, perhaps the project name should change to something like `html2markdown`, `html2md`, or `htmlToMd`...

I’m sorry I’ve not replied. I’m still thinking about the naming issue, and the implications it may have e.g. for bower and npm

@ahane please see https://github.com/domchristie/turndown/pull/209 and help outwit feedback/documentation. Thanks!

Hi @zumoshi, yes this is a bit of a tricky one, and has been discussed in https://github.com/domchristie/turndown/pull/123 in particular in this comment: https://github.com/domchristie/turndown/pull/123#issuecomment-156198157

> I don't think it's the same issue though. the discussion you linked to had problems figuring out the ideal markdown output since no such output existed that would've recreated...

> however, my issue is not with how the newlines are handled, rather with the placement of delimiters. In this case, the two are linked. The markdown examples given both...

> I would prefer the br being outside, and the rendered html looking correct despite positioning of tag not matching original html, compared to not getting any results at all...

> It may be useful to recommend a different utility that shakes out and properly rearranges HTML tag nesting @spirograph 👍 do you know of any libraries that will do...

Not at the moment. What's your use case?

I should add: whitespace is significant in markdown, so to avoid potential issues when the resulting markdown is parsed, the input is stripped of all insignificant whitespace, and trimmed. For...