emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Pieter Praet <pieter@praet.org>
To: Dror Atariah <drorata@gmail.com>,
	Manuel Giraud <manuel.giraud@univ-nantes.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Changing the font family in HTML export
Date: Tue, 28 Jun 2011 11:59:09 +0200	[thread overview]
Message-ID: <87oc1itgya.fsf@praet.org> (raw)
In-Reply-To: <87boxifh4t.fsf@praet.org>

On Tue, 28 Jun 2011 11:18:58 +0200, Pieter Praet <pieter@praet.org> wrote:
> On Tue, 28 Jun 2011 11:00:43 +0200, Dror Atariah <drorata@gmail.com> wrote:
> > This solved the problem. However, as you pointed out, in case I want to publish/share this generated html, I have to send as well another file, and it is not longer self contained. In the automatically, generated html, there is a section at the beginning:
> > --==--
> > <style type="text/css">
> >  <!--/*--><![CDATA[/*><!--*/
> >   html { font-family: Times, serif; font-size: 12pt; }
> >   .title  { text-align: center; }
> >   .todo   { color: red; }
> >   .done   { color: green; }
> >   .tag    { background-color: #add8e6; font-weight:normal }
> > ...
> > --==--
> > 
> > Isn't there a way to tell orgmode to change this part, and, for example, use a different font?
> 
> This is hardcoded @ org-html.el:122.
> 
> You can change this manually, but keep in mind that in order to make it
> stick, you'll need to run "make it stick" (sans the "it stick").
> 
> For more info, see http://orgmode.org/worg/org-faq.html#sec-3_3
> 
> 
> Also, word of advice: this is a public mailing list, so it might not be
> such a fantastic idea to divulge everything apart from your shoe size
> and favourite colour in your signature.
> 
> 
> > On Jun 28, 2011, at 10:42 AM, Manuel Giraud wrote:
> > 
> > > Dror Atariah <drorata@gmail.com> writes:
> > > 
> > >> Thanks for the quick answer!
> > >>> I think you could use an external css file for that. You can do so by
> > >>> setting the STYLE property in you org file like that:
> > >>> 
> > >>> --8<---------------cut here---------------start------------->8---
> > >>> #+TITLE: My page
> > >>> #+STYLE: <link rel="stylesheet" href="my_own.css" type="text/css"/>
> > >>> 
> > >>> * My first title
> > >>> --8<---------------cut here---------------end--------------->8---
> > >> This means that I have to generate and put "my_own.css" file in the
> > >> right place. 
> > > 
> > > Yes. But I don't know how you publish things after having generated the
> > > html. You may just have to copy this file in the right place once.
> > > 
> > > 
> > >> What should this file contain? 
> > > 
> > > It's a css file it could contain many things (see
> > > http://www.w3schools.com/css/ for good tutorials and test). But in your
> > > case this will do the trick:
> > > 
> > > --8<---------------cut here---------------start------------->8---
> > > html { font-family: Helvetica, sans-serif; font-size: 12pt; }
> > > --8<---------------cut here---------------end--------------->8---
> > > 
> > > 
> > >> I'm happy with the formatting of the exported html, I only want to
> > >> change the font. Is this still the right approach?
> > > 
> > > I still think it is the best option because one day you'd like to change
> > > the color of h1's title and this approach still stand (in fact that's
> > > what css are for).
> > > 
> > > Best regards,
> > > -- 
> > > Manuel Giraud
> > 
> > Dror Atariah
> > ---------------------------------------------------------------
> > Landline:        +49-30-43024501
> > Mobile:         +49-176-67116376
> > Mobile (in IL): +972 54 5912389
> > IM:  		      drorata@gmail.com
> > 		   drorata@hotmail.com
> > 
> > 
> 
> 
> Peace
> 
> -- 
> Pieter

For posterity's sake:

The following is part of my response to an off-list
reply from Dror Atariah.

Didn't bother to ask permission for full inclusion,
so I've cut everything but the relevant part.

>> [SNIP]
>>
>>   It appears I've spoken a bit too soon:
>>
>>   Customizing the variables:
>>   - `org-export-html-style'
>>   - `org-export-html-style-extra'
>>   - `org-export-html-style-include-default'
>>   should suffice to do your bidding.
>>
>>   See org-html.el:163-167.
>>
>>   Don't let this keep you from reading the provided link though,
>>   it'll come in handy sooner rather than later.
>>
>> [SNIP]


Peace

-- 
Pieter

  reply	other threads:[~2011-06-28  9:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28  7:18 Changing the font family in HTML export Dror Atariah
2011-06-28  8:19 ` Manuel Giraud
     [not found]   ` <508A016C-064F-48B4-9C56-294D980EB4E6@gmail.com>
     [not found]     ` <87r56egxdj.fsf@univ-nantes.fr>
2011-06-28  9:00       ` Dror Atariah
2011-06-28  9:18         ` Pieter Praet
2011-06-28  9:59           ` Pieter Praet [this message]
2011-06-28 12:10         ` Christian Moe
2011-06-28 13:01           ` Dror Atariah
2011-06-28  9:58 ` 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=87oc1itgya.fsf@praet.org \
    --to=pieter@praet.org \
    --cc=drorata@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=manuel.giraud@univ-nantes.fr \
    /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).