https://bugs.documentfoundation.org/show_bug.cgi?id=169959
--- Comment #4 from peter josvai <[email protected]> --- hi, // just some additional thoughts from another user // I am just about to write a feature suggestion about markdown, and did the search beforehand, and this bug report / concept suggestion reminded me of my frustration yesterday when importing via copy-paste from various markdown editors... My experience was horror :) Being horrified at the sight of the two code blocks with gray background... one with the styles, one with a doc type def? I tried several markdown editors.. wanted to set up a reliable workflow.. and the behavior I found usable was when deleting direct formatting gave me a text with headings and italics and balds... The other type of conversion was that all text became monospace and couldn't apply the document's own style... all of it was overridden... So my empiric conclusion was that direct formatting could be handled easily, while styles, inherited from a markdown doc are PITA. - - - concept-wise: Markdown has no style attributes. It has headings (style), but the attributes to it are up to the viewing environment. In HTML, putting a line (paragraph) into a "h1" block is sufficient already. The rest is up to the viewing device. Sure, we define the h1 attributes, too. But the user can override them, like Firefox does that in "reader mode". I think the good thing would be is only 'markdown' was inherited, like h1, from the markdown document. No style with that, neither direct, nor css. If someone wants style attributes from a markdown editor, s/he should export the document as HTML. I think Markdown is problematic with Writer, cause it is the simplest articulated text format, and LO Writer, as a sophisticated, complex software handles it in complicated ways, whereas it should be handled as simply as simple markdown is :) -- You are receiving this mail because: You are the assignee for the bug.
