emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [REGRESSION] Description List + HTML
Date: Wed, 16 Mar 2011 01:37:50 +0530	[thread overview]
Message-ID: <81ipvk6tbd.fsf@gmail.com> (raw)
In-Reply-To: <87y64g4247.fsf@gmail.com> (Nicolas's message of "Tue, 15 Mar 2011 20:26:00 +0100")

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

Nicolas <n.goaziou@gmail.com> writes:

> Hello,
>
> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> My head is at git commit 6a369 and 
>>
>> With `emacs -Q', do a C-c C-e h on bug.org. 
>>
>> See that the following paragraph (or whatever!)
>>
>> "But in the end, no individual scenes matter but the film as a whole.
>> Important actors in this film are"
>>
>> is NOT within any HTML tags and is floating.
>
> I don't see anything wrong here. What would you expect instead?

Validation with nxml mode is succeeding. So the document is
well-formed. But it does look strange to me.

Anyways, I am attaching the same file exported with release_7.3. You
would notice that the disputed text is enclosed within <p> </p>.

Would you consider enclosing them in paragraph tags. 

Odt exporter pretty much does tag mapping from html->odt. Absence of
these paragraph elements prevents their counterparts - <text:p>
</text:p> from being emitted in my odt exporter. This in turn causes
malformed OpenDocumentText document.

I am in the process of merging my odt changes to the master branch and
am ironing out last minute glitches ...

Jambunathan K.


[-- Attachment #2: bug.html --]
[-- Type: text/html, Size: 5258 bytes --]

  reply	other threads:[~2011-03-15 20:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 19:02 [REGRESSION] Description List + HTML Jambunathan K
2011-03-15 19:26 ` Nicolas
2011-03-15 20:07   ` Jambunathan K [this message]
2011-03-15 20:55     ` Nicolas
2011-03-17 17:09       ` Jambunathan K

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=81ipvk6tbd.fsf@gmail.com \
    --to=kjambunathan@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).