emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Org-Mode Homepage error
Date: Tue, 26 Jul 2011 14:36:24 +0200	[thread overview]
Message-ID: <80bowhxlpz.fsf@somewhere.org> (raw)
In-Reply-To: 87oc0ihwvk.fsf@gnu.org

Hi Bastien,

Bastien wrote:
> thanks for signaling this problem -- I fixed it on the server.
>
> This commit creates problems when exporting using org-info.js: 
>
>   http://orgmode.org/w/?p=org-mode.git;a=commit;h=2f1fbc58be1dc48621217d666da7bc46c3c5d84e
>
> This is no real surprise, as the commit changes the underlying
> div structure of an HTML page produced by Org...
>
> Sebastian, what would be need to make org-info.js compatible
> with both the old HTML structure and the new one, which is:
>
> <body>
>   <div id="preamble"> 
>   </div>
>
>   <div id="content">
>   </div>
>
>   <div id="postamble">
>   </div>
> </body>
>
> (With the "preamble"/"content"/"postamble" strings being defined
> in the variable `org-export-html-divs'.)
>
> If that's too complicate, perhaps we can enforce another structure
> for divs.

I fear this is above my current capability. I tried to understand that code
for a while, but never succeeded (in a reasonable time) to, and never could
simplify it as I wanted (to use it for my own). Of course, this is mainly due
because of my inexperience in good tools to test and debug JS, and to my lack
of knowledge of that language.

But, what did you do to fix the problem?  The current structure of the HTML
page looks good, and follows the above skeleton (except there is no preamble).
So, everything looks right to me?

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2011-07-26 12:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 19:33 Org-Mode Homepage error Renger van Nieuwkoop
2011-07-25 19:42 ` Michael Markert
     [not found]   ` <2152B3DFC552DE47A0A36CCC93D735310439FF7D@mx01.ecoplan.local>
2011-07-25 20:10     ` Michael Markert
2011-07-25 20:26   ` Sebastien Vauban
2011-07-25 20:30   ` Nick Dokos
2011-07-25 21:29     ` Bastien
2011-07-26 12:36       ` Sebastien Vauban [this message]
2011-07-26 15:04         ` Bastien
2011-07-26 16:00           ` Achim Gratz
2011-07-26 21:19             ` Sebastien Vauban
2011-07-27 17:33             ` Bastien
2011-07-28 18:49               ` Achim Gratz
2011-07-31 17:42               ` Achim Gratz
2011-08-16 20:10                 ` Bastien
2011-08-17 15:58                   ` Achim Gratz
2011-08-17 16:18                     ` Bastien
2011-08-17 16:50                       ` Achim Gratz
2011-08-18  7:02                         ` Bastien

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=80bowhxlpz.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).