emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Matthew Lundin <mdl@imapmail.org>
Cc: emacs-orgmode@gnu.org, "Sébastien Vauban" <zthjwsqqafhv@spammotel.com>
Subject: Re: Re: Export as HTML
Date: Mon, 30 Mar 2009 15:11:37 +0200	[thread overview]
Message-ID: <B71DE66D-C77F-4C5F-A8A5-801113EBB0B2@gmail.com> (raw)
In-Reply-To: <m2eiwfgovl.fsf@fastmail.fm>


On Mar 30, 2009, at 2:46 PM, Matthew Lundin wrote:

> Sebastian Rose <sebastian_rose@gmx.de> writes:
>
>> Could you describe here what's the problem with the <div> element?
>>
>> This was put in recently on a users request. If you don't want to  
>> use it
>> for you're CSS styling, just don't.
>
> In my opinion, a minor issue with the new default <div id="content">  
> is
> that it is used used to wrap the entire body of the page. Though there
> are no hard and fast rules, I believe it is a common convention to use
> the id of "wrapper" or "container" for such a div and to use the id
> "content" for a div that begins after a preamble/menu and ends  
> before a
> postamble/menu. In other words in this order.
>
> <body>
> <div id="container">
> <div id="menu>
> ...
> </div>
> <div id="content">
> ...

I would not object to renaming the outer div to "container" or whatever
other name we can find a consensus for.

I think I would object to removing it alltogether,
I cannot see the benefit of doing that.

On the other hand, I cannot really see ths issue here, because the  
name in the
templates could be changed as well, and I would suspect that this is a  
common issue
name clashes when using templates.

- Carsten


>
> Let me repeat that the new behavior of org-export is not really a
> problem for me, as I simply adapted my css stylings to match it (I had
> been using the id "content" for everything after the preamble). But  
> the
> new behavior could cause *minor* confusion for people trying to  
> adapt a
> generic css for use with org-export.
>
> Best,
> Matt
>
>
> _______________________________________________
> 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

  reply	other threads:[~2009-03-30 13:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30  8:55 Export as HTML Sébastien Vauban
2009-03-30  9:03 ` roc lee
2009-03-30  9:10   ` roc lee
     [not found]     ` <bdfccab30903300210h7a683ae4hc4e4a655ce7327c6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-30  9:26       ` Sébastien Vauban
2009-03-30 12:28         ` Sebastian Rose
2009-03-30 12:46           ` Matthew Lundin
2009-03-30 13:11             ` Carsten Dominik [this message]
2009-03-30 14:45               ` Matthew Lundin
2009-03-30 17:45                 ` Carsten Dominik
     [not found]                   ` <1E2E8AB7-274B-4283-AC02-631D165C06E1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-03-30 19:07                     ` Sébastien Vauban
2009-03-30 19:55                   ` Sebastian Rose
2009-03-30 21:06                     ` Carsten Dominik
2009-03-30  9:53 ` Carsten Dominik
     [not found]   ` <61ECBCBA-4963-4435-82BD-BAA37A03FC50-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-03-30 11:23     ` Sébastien Vauban
2009-03-30 11:59       ` roc lee
2009-03-30 13:48       ` Sebastian Rose

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=B71DE66D-C77F-4C5F-A8A5-801113EBB0B2@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.org \
    --cc=zthjwsqqafhv@spammotel.com \
    /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).