emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Francesco Pizzolante <fpz@missioncriticalit.com>
Cc: mailing-list-org-mode <emacs-orgmode@gnu.org>
Subject: Re: Embedding the style when exporting to HTML
Date: Tue, 14 Dec 2010 20:29:11 +0100	[thread overview]
Message-ID: <4D07C587.9030407@christianmoe.com> (raw)
In-Reply-To: <87mxo8mh1i.fsf@mundaneum.com>

Hi,

The following would make the exported HTML link to an external stylesheet.

#+STYLE: <link rel="stylesheet" type="text/css" href="my_style.css"/>

But that 's not what you're after? You want the stylesheet to be 
/outside/ (linked from) your Org file, but /embedded in/ the exported 
HTML? Did I get that right?

CM

On 12/14/10 5:54 PM, Francesco Pizzolante wrote:
> Hi,
>
> I'm still in the process of managing a project with Org while trying to
> evangelize my colleagues to Org. The goal is to share documents in the
> simplest possible way.
>
> What I'm trying to do is to have my style be embedded (inline) to my exported
> HTML file.
>
> Today, it can done by customizing org-export-html-style or add my whole style
> in my Org buffer with the #+STYLE directive.
>
> This has the following disadvantages:
>
> - I have to share my .emacs file with my customizations in order for other
>    people be able to export the Org file as required. Thus if someone has
>    another configuration file, it will not work;
>
> - The style itself (the CSS) is not easily testable and not separate from the
>    data (it is included in my Org file or in my .emacs).
>
> It would be good to specify a file for the style in the Org buffer itself and
> have an option telling Org if the style has to be embedded (or inline) to the
> exported HTML or not.
>
> Having this option has the following advantages:
>
> - my exported file is self-contained and is easily shareable;
>
> - anybody can export the Org file and will get the desired result (even with a
>    different Emacs config);
>
> - the CSS itself is easily testable and maintainable by different guys and
>    can even be a different project.
>
> What do you think?
>
> Is it possible to achieve this with the current version of Org?
>
> Any suggestion is welcome.
>
> Regards,
> Francesco
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>


-- 

Christian Moe
E-mail:  mail@christianmoe.com
Website: http://christianmoe.com

  reply	other threads:[~2010-12-14 19:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 16:54 Embedding the style when exporting to HTML Francesco Pizzolante
2010-12-14 19:29 ` Christian Moe [this message]
2010-12-14 21:05   ` Francesco Pizzolante
2010-12-19  8:25     ` Christian Moe
2010-12-24  3:20       ` René

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=4D07C587.9030407@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fpz@missioncriticalit.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).