From: Christian Moe <firstname.lastname@example.org> To: Tim Cross <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [PATCH] tweaks to ox-html style Date: Sat, 13 Feb 2021 14:32:27 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Tim Cross writes: > BTW I think it would be nice if the html export was able to produce/use > a separate CSS file rather than in-line styles. This would make it > easier to drop exported HTML files into existing sites with custom > styles or update the look of exported files without needing to re-export > or manually edit. The complication is with exporting of HTML snippets, > where you probably want in-line styles. Isn't this already covered by existing capabilities? From the manual: The HTML export back-end includes a compact default style in each exported HTML file. To override the default style with another style, use these keywords in the Org file. They will replace the global defaults the HTML exporter uses. #+HTML_HEAD: <link rel="stylesheet" type="text/css" href="style1.css" /> #+HTML_HEAD_EXTRA: <link rel="alternate stylesheet" type="text/css" href="style2.css" /> To just turn off the default style, customize ‘org-html-head-include-default-style’ variable, or use this option line in the Org file. #+OPTIONS: html-style:nil The only thing I don't think it does is export the default style as a separate .css file rather than inline. Maybe there's a use case where that would be better than turning it off and specifying a linked style, but I can't really think of one. I suppose one would need a new option to specify a path for the exported stylesheet, so it wouldn't save a lot on option lines. Yours, Christian
next prev parent reply other threads:[~2021-02-13 13:42 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-20 10:46 [PATCH] TEC 2021-01-20 11:00 ` [PATCH] tweaks to ox-html style TEC 2021-02-12 6:16 ` Kyle Meyer 2021-02-12 16:57 ` Jens Lechtenboerger 2021-02-12 17:08 ` Jens Lechtenboerger 2021-02-12 18:22 ` Timothy 2021-02-13 14:43 ` Jens Lechtenboerger 2021-02-12 18:16 ` Timothy 2021-02-12 21:46 ` Tim Cross 2021-02-13 9:28 ` Eric S Fraga 2021-02-13 13:32 ` Christian Moe [this message] 2021-02-14 4:36 ` Timothy 2021-04-28 3:38 ` [PATCH] Bastien 2021-04-28 3:53 ` [PATCH] Timothy 2021-04-28 6:36 ` [PATCH] Bastien 2021-04-28 6:33 ` [PATCH] 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] tweaks to ox-html style' \ /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
Code repositories for project(s) associated with this 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).