From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike McLean Subject: Re: CSS link in html export for v. 7.9.3e woes Date: Tue, 26 Feb 2013 11:16:43 -0500 Message-ID: References: <86wqtwh62d.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=e89a8ff1ce24c7cf7a04d6a2fb41 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34774) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UANDm-00040H-1t for emacs-orgmode@gnu.org; Tue, 26 Feb 2013 11:17:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UANDk-0004qk-L7 for emacs-orgmode@gnu.org; Tue, 26 Feb 2013 11:17:37 -0500 Received: from a-pb-sasl-quonix.pobox.com ([208.72.237.25]:64753 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UANDk-0004cw-Fu for emacs-orgmode@gnu.org; Tue, 26 Feb 2013 11:17:36 -0500 Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTP id 5506F90AF for ; Tue, 26 Feb 2013 11:16:45 -0500 (EST) Received: from a-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTP id 4E6B090AE for ; Tue, 26 Feb 2013 11:16:45 -0500 (EST) Received: from mail-ob0-f171.google.com (unknown [209.85.214.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTPSA id EFE9690AD for ; Tue, 26 Feb 2013 11:16:44 -0500 (EST) Received: by mail-ob0-f171.google.com with SMTP id x4so55331obh.16 for ; Tue, 26 Feb 2013 08:16:44 -0800 (PST) In-Reply-To: <86wqtwh62d.fsf@somewhere.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastien Vauban Cc: "emacs-orgmode@gnu.org" --e89a8ff1ce24c7cf7a04d6a2fb41 Content-Type: text/plain; charset=UTF-8 On Monday, February 25, 2013, Sebastien Vauban wrote: > Hi Daniel, > > Daniel Hawthorne wrote: > > Greetings, > > After updating to 7.9.3e, I no longer am able to include a > stylesheet > > link with the following syntax: > > > > #+STYLE: > href="../relative/path/to/mystyle.css"/> > > > > If I go back to my previous version, it works as expected. It is not a > path > > issue; On the resulting site, it never tries to load the stylesheet. The > > release notes do not mention anything that would lead me to believe that > > this should have changed. Suggestions welcome. > > I got into the same trouble days ago. Nicolas' answer was to use the new > syntax therefore, that is: > > #+HTML_STYLE: ... > I've noticed an inconsistency with HTML_STYLE. When I have a few lines of them in a common file, which I include in all of my Org documents via #+SETUPFILE, they work fine. For some specific documents, I have a CSS override, something I desire to look different for just that one documents. Prior to the new exporter I simply added another #+HTML_STYLE line in the file itself. The old exporter would add it after the lines from the #+SETUPFILE and all would look correct. The new exporter skips any such lines from the file while still including the ones from the common file. --e89a8ff1ce24c7cf7a04d6a2fb41 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Monday, February 25, 2013, Sebastien Vauban wrote:
Hi Daniel,

Daniel Hawthorne wrote:
> Greetings,
> =C2=A0 =C2=A0 =C2=A0After updating to 7.9.3e, I no longer am able to i= nclude a stylesheet
> link with the following syntax:
>
> #+STYLE: <link rel=3D"stylesheet" type=3D"text/css&q= uot;
> href=3D"../relative/path/to/mystyle.css"/>
>
> If I go back to my previous version, it works as expected. It is not a= path
> issue; On the resulting site, it never tries to load the stylesheet. T= he
> release notes do not mention anything that would lead me to believe th= at
> this should have changed. Suggestions welcome.

I got into the same trouble days ago. Nicolas' answer was to use the ne= w
syntax therefore, that is:

=C2=A0 #+HTML_STYLE: ...

I've notic= ed an inconsistency with HTML_STYLE. When I have a few lines of them in a c= ommon file, which I include in all of my Org documents via #+SETUPFILE, the= y work fine. For some specific documents, I have a CSS override, something = I desire to look different for just that one documents. Prior to the new ex= porter I simply added another #+HTML_STYLE line in the file itself. The old= exporter would add it after the lines from the #+SETUPFILE and all would l= ook correct. The new exporter skips any such lines from the file while stil= l including the ones from the common file.
--e89a8ff1ce24c7cf7a04d6a2fb41--