Re: Re: Patch to fix two bugs in HTML/DocBook exporters

[Carsten Dominik <carsten.dominik@gmail.com>]

On Apr 9, 2009, at 7:27 AM, Baoqiu Cui wrote:

> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>>> 1. Bug One: two consecutive lists with different list types at the
>>> same
>>>  level are exported as *one* list.  For example, the following two
>>>  lists
>>>
>>>  1. Ordered List Item 1
>>>  2. Ordered List Item 2
>>>
>>>  - Itemized List Item 1
>>>  - Itemized List Item 2
>>>  - Itemized List Item 3
>>
>> This is, actually, not a bug but on purpose.
>> List boundaries are set by indentation, and the
>> list type is set by the first item.  I prefer to keep it that way.
>> In the same way, the actual numbers in an ordered list are ignored
>> and the list is renumbered on export.
>
> Thanks for the explanation, Carsten!  This makes perfect sense to me.
> No wonder I found the same "problem" in function
> `org-beginning-of-item-list'. :-)
>
> If a lot of people like to mix different list types together in the  
> way
> I showed above, I would prefer that Org mode has finer support for  
> this.

Hi Baoqiu,

I really don't see why.  Under what circumstances would you
want to mix list types like this, without at least on little
transition sentence between the lists?  I cannot remember any
occasion when I would have wanted this to be possible.


> But for now, I think we should keep the existing way.
>
>>> 2. Bug Two: a paragraph *immediately* after a block like quote,  
>>> verse,
>>>  centered block, example, etc. is not wrapped into paragraph tags
>>>  (<p>...</p> in HTML or <para>...</para> in DocBook).  While it is
>>> not
>>>  a big deal for HTML exporter, this bug makes exported DocBook XML
>>>  document invalid.
>>>
>>>  The following lines can reproduce this bug:
>>>
>>>  : Code line one
>>>  : Code line two
>>>  This is a paragraph immediately after the above code block without
>>> an
>>>  empty line before it, and it is NOT wrapped in a paragraph (<p> in
>>>  HTML or <para> in DocBook) in exported format.
>>>
>>> Please let me know if you see any problems in the fix.
>>
>> I would like to fix this bug, and if you send me a patch just
>> for this, I'd be happy to apply it.
>
> OK.  I am attaching the new patch at the end.

Thanks, in particular also for preparing the patch
against the new file org-html.el.  I have applied
it.

- Carsten