From: Carsten Dominik <dominik@science.uva.nl>
To: Xerxes Folupa <120715@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: bug: superfluous <p> tags when exporting verse and quote blocks
Date: Sun, 7 Dec 2008 21:17:00 +0100 [thread overview]
Message-ID: <D8F04B0E-4342-4124-94B3-0185A3E3A43A@uva.nl> (raw)
In-Reply-To: <op.uls1xduqtmm3t5@parthenia>
Hi Xerxes,
thanks for the report, I have both issues.
- Carsten
On Dec 7, 2008, at 7:35 PM, Xerxes Folupa wrote:
> Hi,
>
> I spotted a little inconsistency in the way Org strips tags when
> processing #+begin_verse ... #+end_verse, and #+begin_quote ... #
> +end_quote blocks, compared with other literal blocks that strip
> superfluous <p> tags correctly (e.g. #+html)
>
> org-version: Org-mode version 6.14
>
> emacs-version: GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
>
> As usual, it's easier to request a fix than to implement it
> yourself...
>
> ===
>
> * Sample input:
>
>
> #+begin_verse
> one
> two
> #+end_verse
>
> paragraph.
>
> #+begin_quote
> one. --author
> #+end_quote
>
> * Output:
>
> <p>
> <p class="verse">
> one <br/>
> two <br/>
> </p>
> </p>
> <p>
> paragraph.
> </p>
> <p>
> <blockquote>
> <p>
> one. –author
> </p>
> </blockquote>
> </p>
>
> * Desired, 'valid xhtml' output:
>
> <p class="verse">
> one <br/>
> two <br/>
> </p>
> <p>
> paragraph.
> </p>
> <blockquote>
> <p>
> one. –author
> </p>
> </blockquote>
>
> ===
>
> Additional question: is the space before the <br/> in verse blocks a
> design decision?
>
> Cheers,
> Xerxes
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2008-12-07 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 18:35 bug: superfluous <p> tags when exporting verse and quote blocks Xerxes Folupa
2008-12-07 20:17 ` Carsten Dominik [this message]
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=D8F04B0E-4342-4124-94B3-0185A3E3A43A@uva.nl \
--to=dominik@science.uva.nl \
--cc=120715@gmail.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).