Markdown / Blockquote conversion giving unexpected results

[Agama]

I am using blockquotes within some markdown text but getting unexpected results. Calibre's resultant html is different to that produced by the standard markdown processor, (see http://daringfireball.net/projects/markdown/dingus).

With sample source text of:

### Blockquote Test

> This is a blockquote
> section of markdown.
>
> Hardwrap with 2 trailing spaces.
> Use for quotations/poetry etc.

Markdown (Daring Fireball) produces:

<h3>Blockquote Test</h3>

<blockquote>
<p>This is a blockquote <br />
section of markdown. </p>

<p>Hardwrap with 2 trailing spaces. <br />
Use for quotations.</p>
</blockquote>

whereas calibre produces:

<h3 class="calibre1">Blockquote Test</h3>
<blockquote class="calibre2"><p class="calibre3">This is a blockquote &gt; section of markdown. &gt; &gt; Hardwrap with 2 trailing spaces. &gt; Use for quotations/poetry etc.
</p>
</blockquote>

These differences obviously display quite diffently in a eBook. Can I get calibre to produce the standard output?

I am using calibre 0.7.46 on Windows 7. In the TXT input conversion options I used Paragraph style: block and Formatting style: markdown.

[Perkin]

In conversion settings, Txt-Input - set the Paragraph style to 'off'
that should do it

[Agama]

The available options are: auto, block, single, print, unformatted.

I tried unformatted and got:

<blockquote class="calibre2"><p class="calibre3">This is a blockquote &gt; section of markdown.
</p>
<p class="calibre3">Hardwrap with 2 trailing spaces.
</p>
<p class="calibre3">Use for quotations/poetry etc.
</p>
</blockquote>

This is closer but still has a spurious &gt; instead of a new line within the paragraph. I'll try all the other options and see what I get.

[Agama]

Single gives:

<blockquote class="calibre2"><p class="calibre3">This is a blockquote
</p>
<p class="calibre3">section of markdown.
</p>
<p class="calibre3">Hardwrap with 2 trailing spaces.
</p>
<p class="calibre3">Use for quotations/poetry etc.
</p>
</blockquote>

but this is not strictly correct and will cause every line in my source to be treated as a paragraph, which is not how markdown works.

(Print and Unformatted were even worse).

[Perkin]

Are you sure you're using calibre 0.7.46, as there was a new setting, especially for markdown/Textile, which is 'off'

I'm also using Win7, and I have auto, block, single, print, unformatted and off.

[Agama]

Ah! my mistake, I'm still on 0.7.45. Thanks, I'll get updated and see what happens.

[DoctorOhh]

Originally Posted by Agama

The available options are: auto, block, single, print, unformatted.

Perkin said Paragraph Style not Formatting style. Paragraph style has a off option, Formatting style does not.

Update: Never mind, sometimes I'm too darn slow.

[Perkin]

Just done a test with your few lines, and there's a problem, the lines still get joined together.

I done a test with Textile styled text

h3. Blockquote Test

bq. This is a blockquote
section of markdown.
 
bq. Hardwrap with 2 trailing spaces.
Use for quotations/poetry

And with the 'off' paragraph setting this converts/works properly.

  <h3 class="calibre1" id="calibre_pb_0">Blockquote Test</h3>

  <blockquote class="calibre2">
    <p class="calibre3">This is a blockquote<br class="calibre4" />
    section of markdown.</p>
  </blockquote>

  <blockquote class="calibre2">
    <p class="calibre3">Hardwrap with 2 trailing spaces.<br class="calibre4" />
    Use for quotations/poetry etc.</p>
  </blockquote>

[Perkin]

Again with Textile (I prefer it to markdown - more options)

h3. Blockquote Test

bq.. This is a blockquote
section of markdown.
 
Hardwrap with 2 trailing spaces.
Use for quotations/poetry etc.

(Any following paragraph that you wanted return to normal, you would just precede with 'p. ')

Converts to

  <h3 class="calibre1" id="calibre_pb_0">Blockquote Test</h3>

  <blockquote class="calibre2">
    <p class="calibre3">This is a blockquote<br class="calibre4" />
    section of markdown.</p>

    <p class="calibre3">Hardwrap with 2 trailing spaces.<br class="calibre4" />
    Use for quotations/poetry etc.</p>
  </blockquote>

[Perkin]

No matter what options I try with markdown text, the lines still get wrapped.
You should probably send a small note to user_none (who maintains that code) to check if the 'off' also applies to markdown, as it does with Textile.

[Agama]

Thanks Perkin, 0.7.46 has fixed it for me, with Paragraph style: Off I get:

<blockquote class="calibre2"><p class="calibre3">This is a blockquote<br class="calibre4"/>
section of markdown.
</p>
<p class="calibre3">Hardwrap with 2 trailing spaces.<br class="calibre4"/>
Use for quotations/poetry etc.
</p>
</blockquote>

I haven't come across Textile but I will look it up.

[user_none]

I'll look into this issue either this or tomorrow evening.

[Perkin]

Originally Posted by user_none

I'll look into this issue either this or tomorrow evening.

Agama says it works properly for him.

I found the lines got combined, unless I added a couple of spaces at end of those lines.
They then worked properly, so with markdown, I can't remember if blockquote text needs the spaces on the end. (So it may be me)

I just copy & pasted his example in his post, which didn't have any extra spaces, which may explain why it didn't work properly for me. (at least until I added them)

[Perkin]

Just checked http://daringfireball.net/projects/m...tax#blockquote and the lines should not be combined.
So we may have other settings which may be causing our differences.

[Agama]

Originally Posted by Perkin

Agama says it works properly for him.

I found the lines got combined, unless I added a couple of spaces at end of those lines.

Yes, this is how markdown works. Two or more trailing spaces cause a <br> tag to be generated, which is exactly what calibre now correctly does to my markdown, (with Paragraph style: off). My trailing spaces were included in the post that I made but they (obviously!) cannot be seen.

So, I'm quite satisfied that calibre is performing exactly as required.

(I've had a look at Textile and it looks very useful: not as readable as markdown, but more flexible as a pre-cursor to book conversion, so I think I'll make the switch).