From: Brian Burns <bburns.km@gmail.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: emacs-tangents@gnu.org
Subject: Re: New EmacsWiki theme v2
Date: Tue, 26 Jan 2016 13:33:23 -0600 [thread overview]
Message-ID: <CA+XjW6yag_KQSzMcreO4OWbuOKLS_EXZ9+5OHLgE2oYDwYgeuw@mail.gmail.com> (raw)
In-Reply-To: <CAP_d_8WoH9wXBQRxhrsAKpVWL94eFjRM9JeJZ6sHnKp5CCJB1w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
> Why do you even want to specify a font for body text?
Well, just wanting to pick one that looked nice for the site - some of the
themes specify a font, but the default Bootstrap and the Classic theme
don't, so maybe this one shouldn't either - I pushed up a new version with
no font specified (aside from monospace for code), so it'll just whatever
default they have set.
Brian
On Mon, Jan 25, 2016 at 11:02 PM, Yuri Khan <yuri.v.khan@gmail.com> wrote:
> On Tue, Jan 26, 2016 at 6:36 AM, Brian Burns <bburns.km@gmail.com> wrote:
> > Yeah, I searched through all the Google Fonts to try to find a good serif
> > font but they all seemed either too light or too heavy, so ended up just
> > using Garamond and URW Palladio L - the Garamond was a bit light but I
> kind
> > of got used to it.
>
> Why do you even want to specify a font for body text?
>
> The user already has one favorite serif font, one favorite sans-serif
> font, and one favorite monospaced font, and has them configured in
> their browser preferences. Any change from that will lead to a
> decrease in legibility for that particular user.
>
> (Overriding fonts for headings is okay. But very sparingly.)
>
[-- Attachment #2: Type: text/html, Size: 1699 bytes --]
prev parent reply other threads:[~2016-01-26 19:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 21:05 New EmacsWiki theme v2 Brian Burns
2016-01-25 20:43 ` John Wiegley
2016-01-25 23:16 ` Drew Adams
2016-01-26 0:41 ` Brian Burns
2016-01-26 1:00 ` John Wiegley
2016-01-26 2:14 ` Drew Adams
2016-01-26 2:09 ` Drew Adams
2016-01-26 0:36 ` Brian Burns
2016-01-26 5:02 ` Yuri Khan
2016-01-26 5:47 ` Drew Adams
2016-01-26 19:33 ` Brian Burns [this message]
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=CA+XjW6yag_KQSzMcreO4OWbuOKLS_EXZ9+5OHLgE2oYDwYgeuw@mail.gmail.com \
--to=bburns.km@gmail.com \
--cc=emacs-tangents@gnu.org \
--cc=yuri.v.khan@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.