emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: Adam <ahcnz@ihug.co.nz>
Cc: emacs-orgmode@gnu.org
Subject: Re: CSS and Publishing to HTML Tutorial
Date: Fri, 09 Jul 2010 22:26:36 +0200	[thread overview]
Message-ID: <87zky0tn9f.fsf@gmx.de> (raw)
In-Reply-To: <201007100730.47486.ahcnz@ihug.co.nz> (Adam's message of "Sat, 10 Jul 2010 07:30:45 +1200")

Adam <ahcnz@ihug.co.nz> writes:
> Thanks for reply, guidance and suggestions.
> I agree my cgi has nothing to do with INFOJS_OPT, nor vice versa. 
>
> Regarding CSS, I have gone back to the default position, of including 
> these inside "org-notes" of org-publish-project-alist, and not referring 
> to an external CSS, 
>
>   :style-include-default   t
>   :style-include-scripts  nil
> (after Robert's comments). 
>
> So I am hoping to use the default style output, and then adjust the style
> in the org file header using  #+STYLE:  < ... > 
>
> In the org file, I have used  org-insert-export-options-template   and have 
> deleted the line #+INFO-JS_OPT: ...
>
> I publish as per the tutorial, then open the HTML result in MS Internet 
> Explorer, which reports in a yellow warning band across the top words to the 
> effect of   "To help protect your security, IE has restricted ... Click here 
> for options". 
>
> If I then edit that HTML file, and remove the 2nd of the two <style> ... 
> </style> blocks, then reloading the HTML form does not cause the yellow 
> warning to be issued. The form also appears to retain its default style, of 
> red color for the TODO etc. 
>
> This 2nd style block appears immediately before the <body> content 
> of the document.  At the very end of the Head, just before </head>.
> It begins with, 
> <script type="text/javascript">
>   ... 
>   function CodeHighlightOn(elim, id)   etc
>
> Looking at  org-exp.el  around line 554,  it almost seems as if javascript 
> is part of the default style. 


Forgot:

  This would indeed be a bug in the HTML exporter.  It should regard
  your setting of `:style-include-scripts'.

  Here it works as expected.

  (setq org-publish-project-alist
      '(("SOME-PROJECT"
         :style-include-scripts nil
         ...)
        ("OTHER-PROJECT"
         ...)))



Bets wishes

  Sebastian

  parent reply	other threads:[~2010-07-09 20:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08  7:48 CSS and Publishing to HTML Tutorial Adam
2010-07-09 13:35 ` Sebastian Rose
2010-07-09 19:30   ` Adam
2010-07-09 20:04     ` Sebastian Rose
2010-07-09 20:26     ` Sebastian Rose [this message]
2010-07-09 15:00 ` Robert Klein

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=87zky0tn9f.fsf@gmx.de \
    --to=sebastian_rose@gmx.de \
    --cc=ahcnz@ihug.co.nz \
    --cc=emacs-orgmode@gnu.org \
    /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).