Bug? Text before HTML comment output as Plain

Bug? Text before HTML comment output as Plain

[BP Jonsson]

The HTML writer outputs any text in a markdown paragraph
which precedes an HTML comment as Plain text rather than
Para; see markdown example, native and HTML output below,
where the beginning of the second non-empty line before the
comment ends up outside the Para/<p>!

Is this a bug or a feature?  If the latter, what purpose
does it serve?

/bpj

----

Ut enim ad minim veniam

Duis aute irure <!-- FOO --> dolor in reprehenderit

Excepteur sint occaecat cupidatat non proident

----

Pandoc (Meta {docTitle = [], docAuthors = [], docDate = []})
[ Para [Str "Ut",Space,Str "enim",Space,Str "ad",Space,Str 
"minim",Space,Str "veniam"]
, Plain [Str "Duis",Space,Str "aute",Space,Str "irure"]
, RawHtml "<!-- FOO --> "
, Para [Str "dolor",Space,Str "in",Space,Str "reprehenderit"]
, Para [Str "Excepteur",Space,Str "sint",Space,Str 
"occaecat",Space,Str "cupidatat",Space,Str "non",Space,Str 
"proident"] ]

----

<p
 >Ut enim ad minim veniam</p
 >Duis aute irure<!-- FOO --> <p
 >dolor in reprehenderit</p
 ><p
 >Excepteur sint occaecat cupidatat non proident</p
 >

Re: Bug? Text before HTML comment output as Plain

[John MacFarlane]

+++ BP Jonsson [Nov 09 10 16:40 ]:
> The HTML writer outputs any text in a markdown paragraph
> which precedes an HTML comment as Plain text rather than
> Para; see markdown example, native and HTML output below,
> where the beginning of the second non-empty line before the
> comment ends up outside the Para/<p>!
> 
> Is this a bug or a feature?  If the latter, what purpose
> does it serve?

I'll call it a bug, or at least an undesirable feature.
The problem is that an HTML comment sometimes needs to be
construed as "inline," and sometimes as block-level.

But I think it should be possible to fix things so that
it does the right thing...

Why don't you submit a bug report, or I'll forget!

John


> 
> /bpj
> 
> ----
> 
> Ut enim ad minim veniam
> 
> Duis aute irure <!-- FOO --> dolor in reprehenderit
> 
> Excepteur sint occaecat cupidatat non proident
> 
> ----
> 
> Pandoc (Meta {docTitle = [], docAuthors = [], docDate = []})
> [ Para [Str "Ut",Space,Str "enim",Space,Str "ad",Space,Str
> "minim",Space,Str "veniam"]
> , Plain [Str "Duis",Space,Str "aute",Space,Str "irure"]
> , RawHtml "<!-- FOO --> "
> , Para [Str "dolor",Space,Str "in",Space,Str "reprehenderit"]
> , Para [Str "Excepteur",Space,Str "sint",Space,Str
> "occaecat",Space,Str "cupidatat",Space,Str "non",Space,Str
> "proident"] ]
> 
> ----
> 
> <p
> >Ut enim ad minim veniam</p
> >Duis aute irure<!-- FOO --> <p
> >dolor in reprehenderit</p
> ><p
> >Excepteur sint occaecat cupidatat non proident</p
> >
> 
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> For more options, visit this group at http://groups.google.com/group/pandoc-discuss?hl=en.
> 

Re: Bug? Text before HTML comment output as Plain

[John MacFarlane]

+++ John MacFarlane [Nov 09 10 18:35 ]:
> +++ BP Jonsson [Nov 09 10 16:40 ]:
> > The HTML writer outputs any text in a markdown paragraph
> > which precedes an HTML comment as Plain text rather than
> > Para; see markdown example, native and HTML output below,
> > where the beginning of the second non-empty line before the
> > comment ends up outside the Para/<p>!
> > 
> > Is this a bug or a feature?  If the latter, what purpose
> > does it serve?
> 
> I'll call it a bug, or at least an undesirable feature.
> The problem is that an HTML comment sometimes needs to be
> construed as "inline," and sometimes as block-level.
> 
> But I think it should be possible to fix things so that
> it does the right thing...
> 
> Why don't you submit a bug report, or I'll forget!

No need.  Fixed (I think) in  21556e37f4596cd7020337f1a8f039364c47c04b.

John