Chris Papademetrious

There indeed seems to be some kind of bug in the `html.parser` parser. I think there is a heuristic that tries to identify the ``/`` convention of the content, because...

Smaller testcase: ``` >>> from markdownify import markdownify as md >>> md('TEXT1TEXT2') 'TEXT1TEXT2\n\n' ``` There is no line break before the TEXT2 paragraph content.

I don't think this is a bug. `` is an inline HTML element per the specification, and thus it does not preserve whitespace. If you render ``` line1 line2 line3...

This is definitely a bug. We encountered it too. Ideally, this should be fixed and handled correctly by default, without any additional options needed.

@wilsonzlin - you already quite nicely categorize tags into various categories. Maybe providing a generalized way to change a tag's default category could work? For my purposes, I *do* want...

@stefan-jung - I understand that you cannot share your actual testcase. However, we need something to reproduce the issue. Can you please create a small sanitized testcase that demonstrates the...

I suppose this is not a surprise, but the issue exists with Markdown topics too: ```markdown # My Markdown Topic {audience="novice expert"} This is a topic. ## My Markdown Subtopic...

@stefan-jung - Thanks for filing this pull request! Would you be willing to switch the polarity of this change? It might make more sense to add a `break` class value...

@stefan-jung, I apologize if I was not clear. What I meant was to include `break` for `@placement = "break"` images, but *not* to include `inline` for `@placement = "inline"` images...

@stefan-jung - maybe we can restart this discussion?