On Mar 30, 2009, at 2:46 PM, Matthew Lundin wrote:
Sebastian Rose <sebastian_r...@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
_______________________________________________
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
