emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: org-mode <emacs-orgmode@gnu.org>,
	Richard Riley <rileyrgdev@googlemail.com>
Subject: Re: export and containers
Date: Tue, 03 Mar 2009 11:14:19 +0100	[thread overview]
Message-ID: <87ocwic3r8.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <66006671-E8BB-42F1-A86B-C1141A619C75@uva.nl> (Carsten Dominik's message of "Tue, 3 Mar 2009 11:02:04 +0100")

Carsten Dominik <dominik@science.uva.nl> writes:
> I have now added a "content" container around all of body.
>
> - Carsten


OK, I'll go and adjust org-info.js as needed now.

Best,

  Sebastian

>
> On Mar 3, 2009, at 2:16 AM, Richard Riley wrote:
>
>> Sebastian Rose <sebastian_rose@gmx.de> writes:
>>
>>> Richard Riley <rileyrgdev@googlemail.com> writes:
>>>> Sebastian Rose <sebastian_rose@gmx.de> writes:
>>>>
>>>>> Richard Riley <rileyrgdev@googlemail.com> writes:
>>>>>> I really dont see the plethora of sec-id# that are currently generated
>>>>>> being really useful since they change on each export if new stuff is
>>>>>> entered. This make existing CSS redundant unfortunately.
>>>>>
>>>>> The IDs in the section headings are not meant for CSS styling. That's
>>>>> what the classes are for.
>>>>>
>>>>>
>>>>> Regards,
>>>>
>>>> IDs are frequently used for styling as well as classes.
>>>
>>>
>>> Well, in this case, since we never know the ID of a section in
>>> advance...
>>
>> Or haven't known in the past. See other post. We probably need to be
>> able to control the class and/or ID of individual sections at the higher
>> level.
>

-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose@emma-stil.de, sebastian_rose@gmx.de
Http:  www.emma-stil.de

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

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-28 10:29 export and containers Richard Riley
2009-02-28 11:37 ` Sebastian Rose
2009-02-28 19:23   ` Carsten Dominik
2009-02-28 21:09     ` Sebastian Rose
2009-03-02  8:03   ` Richard Riley
2009-03-02  9:29     ` Sebastian Rose
2009-03-02 11:11       ` Carsten Dominik
2009-03-02 11:58         ` Sebastian Rose
2009-03-02 13:10           ` Carsten Dominik
2009-03-02 16:00             ` Sebastian Rose
2009-03-02 17:03               ` Carsten Dominik
2009-03-02 18:12                 ` Richard Riley
2009-03-02 18:56                   ` Sebastian Rose
2009-03-02 20:22                     ` Richard Riley
2009-03-03  0:52                       ` Sebastian Rose
2009-03-03  1:16                         ` Richard Riley
2009-03-03 10:02                           ` Carsten Dominik
2009-03-03 10:14                             ` Sebastian Rose [this message]
2009-03-03 10:50                               ` Carsten Dominik
2009-03-03 10:57                             ` Sebastian Rose
2009-03-02 19:03                   ` Sebastian Rose
2009-03-02 18:54                 ` Sebastian Rose
2009-03-02 19:06                   ` Sebastian Rose
2009-03-02 14:38       ` Richard Riley
2009-03-02 16:50         ` 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=87ocwic3r8.fsf@kassiopeya.MSHEIMNETZ \
    --to=sebastian_rose@gmx.de \
    --cc=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=rileyrgdev@googlemail.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).