[-- Attachment #1: Type: text/plain, Size: 504 bytes --] Greetings, After updating to 7.9.3e, I no longer am able to include a stylesheet link with the following syntax: #+STYLE: <link rel="stylesheet" type="text/css" 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. Thanks, Daniel Hawthorne [-- Attachment #2: Type: text/html, Size: 642 bytes --]
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: <link rel="stylesheet" type="text/css"
> 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: ...
Best regards,
Seb
--
Sebastien Vauban
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --] 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: <link rel="stylesheet" type="text/css" > > 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. [-- Attachment #2: Type: text/html, Size: 1629 bytes --]
Hello,
Mike McLean <mike.mclean@pobox.com> writes:
> 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.
I think I have fixed this. Could you confirm it?
If it still doesn't work, would you mind providing an ECM?
Thank you.
Regards,
--
Nicolas Goaziou
[-- Attachment #1: Type: text/plain, Size: 871 bytes --] On Tuesday, February 26, 2013, Nicolas Goaziou wrote: > Hello, > > Mike McLean <mike.mclean@pobox.com <javascript:;>> writes: > > > 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. > > I think I have fixed this. Could you confirm it? Sorry for the delay, but I can confirm that this now works. Thank you. [-- Attachment #2: Type: text/html, Size: 1178 bytes --]
"Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes: > I got into the same trouble days ago. Nicolas' answer was to use the new > syntax therefore, that is: > #+HTML_STYLE: ... There does not seem to be any reference to HTML_STYLE in the Org manual. (Org version 7.9.3e (7.9.3e-1751-g8c47da) — taken this morning). François
François Pinard <pinard@iro.umontreal.ca> writes:
> There does not seem to be any reference to HTML_STYLE in the Org manual.
> (Org version 7.9.3e (7.9.3e-1751-g8c47da) — taken this morning).
I guess Sébastien meant #+HTML_HEAD -- #+HTML_STYLE does not exist
anymore.
--
Bastien
Hi François, Bastien,
Bastien wrote:
> François Pinard <pinard-CRDzTM1onBSWkKpYnGOUKg@public.gmane.org> writes:
>
>> There does not seem to be any reference to HTML_STYLE in the Org manual.
>> (Org version 7.9.3e (7.9.3e-1751-g8c47da) — taken this morning).
>
> I guess Sébastien meant #+HTML_HEAD -- #+HTML_STYLE does not exist
> anymore.
Yes HTML_STYLE has been changed in between, to a better keyword, btw.
Best regards,
Seb
--
Sebastien Vauban