* Bug? Text before HTML comment output as Plain @ 2010-11-09 15:40 BP Jonsson [not found] ` <4CD96B56.2060905-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 0 siblings, 1 reply; 3+ messages in thread From: BP Jonsson @ 2010-11-09 15:40 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw 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 > ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <4CD96B56.2060905-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]
* Re: Bug? Text before HTML comment output as Plain [not found] ` <4CD96B56.2060905-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> @ 2010-11-10 2:35 ` John MacFarlane [not found] ` <20101110023523.GB22881-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 0 siblings, 1 reply; 3+ messages in thread From: John MacFarlane @ 2010-11-10 2:35 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ 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. > ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <20101110023523.GB22881-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>]
* Re: Bug? Text before HTML comment output as Plain [not found] ` <20101110023523.GB22881-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> @ 2010-11-10 6:52 ` John MacFarlane 0 siblings, 0 replies; 3+ messages in thread From: John MacFarlane @ 2010-11-10 6:52 UTC (permalink / raw) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw +++ 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-11-10 6:52 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-11-09 15:40 Bug? Text before HTML comment output as Plain BP Jonsson [not found] ` <4CD96B56.2060905-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2010-11-10 2:35 ` John MacFarlane [not found] ` <20101110023523.GB22881-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org> 2010-11-10 6:52 ` John MacFarlane
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).