From: Carsten Dominik <firstname.lastname@example.org> To: Baoqiu Cui <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Re: Patch to fix two bugs in HTML/DocBook exporters Date: Thu, 9 Apr 2009 12:33:55 +0200 [thread overview] Message-ID: <AFCBF8C9-2453-49A4-9C78-35C5A7046394@gmail.com> (raw) In-Reply-To: <email@example.com> On Apr 9, 2009, at 7:27 AM, Baoqiu Cui wrote: > Carsten Dominik <firstname.lastname@example.org> 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
next prev parent reply other threads:[~2009-04-09 10:34 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-06 21:37 Baoqiu Cui 2009-04-08 15:16 ` Carsten Dominik 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 [this message] 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=AFCBF8C9-2453-49A4-9C78-35C5A7046394@gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Re: Patch to fix two bugs in HTML/DocBook exporters' \ /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
Code repositories for project(s) associated with this 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).