emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Baoqiu Cui <cbaoqiu@yahoo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Patch to fix two bugs in HTML/DocBook exporters
Date: Wed, 8 Apr 2009 17:16:22 +0200	[thread overview]
Message-ID: <6BB5BE3D-4B4D-4D14-BB8C-2F955A93E041@gmail.com> (raw)
In-Reply-To: <bycfxgllazg.fsf@muchbodyking-lm.gateway.2wire.net>

Hi Baoqiu,


On Apr 6, 2009, at 11:37 PM, Baoqiu Cui wrote:

> Hi Carsten,
>
> During the weekend, I found and fixed two bugs that exist in
> HTML/DocBook exporters (see the following descriptions).  I am  
> attaching
> a patch for the fixes at the end of this email.
>
> 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.

>
>   are exported as one ordered list in HTML (see below, similar problem
>   also exist in DocBook).
>
>   : <ol>
>   : <li>
>   : Ordered List Item 1
>   : </li>
>   : <li>
>   : Ordered List Item 2
>   :
>   : </li>
>   : <li>
>   : Itemized List Item 1
>   : </li>
>   : <li>
>   : Itemized List Item 2
>   : </li>
>   : <li>
>   : Itemized List Item 3
>   :
>   : </li>
>   : </ol>
>
> 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.

- Carsten

  reply	other threads:[~2009-04-08 15:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 21:37 Patch to fix two bugs in HTML/DocBook exporters Baoqiu Cui
2009-04-08 15:16 ` Carsten Dominik [this message]
2009-04-09  5:27   ` Baoqiu Cui
2009-04-09  7:25     ` Leo
2009-04-09  8:06       ` Baoqiu Cui
2009-04-09 10:33     ` Carsten Dominik
2009-04-09 18:29       ` Baoqiu Cui
2009-04-11  6:19         ` Carsten Dominik
2009-04-09 21:03       ` Mike Newman
2009-04-11  6:20         ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6BB5BE3D-4B4D-4D14-BB8C-2F955A93E041@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=cbaoqiu@yahoo.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).