public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>,
	pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Adding minimal CSS to pandoc's default HTML template
Date: Mon, 24 Aug 2020 13:03:46 -0700	[thread overview]
Message-ID: <m2v9h7x13x.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <c26ebc5e-35e3-0e84-037e-d8fa1f119438-Jdbf3xiKgS8@public.gmane.org>

Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org> writes:

>> The only concern I have is that this could open pandora's box when
>> is comes to requests for CSS tweaks. But this seems like a minor
>> problem.
>
> It's also worth considering that not all HTML output is fed to a 
> browser.  I've used Pandoc to feed to local previews, or to sites that 
> can ingest HTML and work with it.  It's probably embedded into some 
> pipelines someplace as well.

You can always use "fragment" mode if that's what you want (no -s).
The CSS will not be embedded in this case.

For local previews, though, won't it be better with the CSS,
which gives you a sane margin, fonts, etc.?

> I appreciate the thought on this, but I'm not sure it's something we 
> want on by default - and it's also something that can be implemented 
> fairly easily by the user editing their default template.

True, but if this is an argument against it, wouldn't it be an
argument against *everything* in the default template?


  parent reply	other threads:[~2020-08-24 20:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22 11:23 mb21
     [not found] ` <41422a08-cc8d-4480-8bfc-03d907cb2794n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-23 11:54   ` Albert Krewinkel
     [not found]     ` <87r1rxa887.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-08-23 17:24       ` mb21
2020-08-24 17:51       ` Daniel Staal
     [not found]         ` <c26ebc5e-35e3-0e84-037e-d8fa1f119438-Jdbf3xiKgS8@public.gmane.org>
2020-08-24 18:42           ` mb21
2020-08-24 20:03           ` John MacFarlane [this message]
     [not found]             ` <m2v9h7x13x.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-29 10:06               ` Ganriel Nützi
     [not found]                 ` <6497A421-E81B-45BA-8148-47B9CFC94C78-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-08-29 12:52                   ` BPJ

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2v9h7x13x.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=DStaal-Jdbf3xiKgS8@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).