From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [Worg] Proposing a few CSS changes
Date: Sun, 26 Sep 2021 19:12:46 +0700 [thread overview]
Message-ID: <sipo40$jn2$1@ciao.gmane.io> (raw)
In-Reply-To: <87pmswe7ur.fsf@gmail.com>
On 26/09/2021 02:51, Timothy wrote:
>
> I’m a big fan of the shift to a fixed em-based max width. However, I’m not quite
> sold on a few of the other changes, for instance the font change. While it does
> vary, I must say than in particular I find the default serifed font of browsers
> somewhat unattractive. Have you considered instead a sans-serif system font
> stack? For example, this is what I used on the homepage:
> ┌────
> │ -apple-system, BlinkMacSystemFont, San Francisco, Helvetica Neue, Helvetica, Ubuntu, Roboto, Noto, Segoe UI, Arial, sans-serif;
> └────
Sorry if it is a false alarm, I do not have enough experience with CSS.
Since "Noto Serif" font exist, is just "Noto" enough to select namely
"Noto Sans"?
Concerning "em" and "rem", I may be wrong, but Chromium on Linux may
apply font settings from desktop theme to <body> element, while "rem"
units are based on <html> element. So using rem for max-width and
leaving font-size to user defaults may result in too narrow or too wide
text column. Unsure if values like "larger" are more "portable" for
font-size of header elements.
Modern browsers support light and dark themes. I can not suggest CSS
snippets for that since I have never played with such selectors yet.
I do not know what is the proper balance of overriding of defaults. I
consider default built-in styles as compatibility mode with old pages.
That is why I do not think that relying on default styles only (even
some users customize them) is a good idea. Absolute font size may be
left as in user preferences.
next prev parent reply other threads:[~2021-09-26 12:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 2:37 [Worg] Proposing a few CSS changes Adam Porter
2021-09-24 8:00 ` Eric S Fraga
2021-09-25 13:58 ` Bastien
2021-09-26 0:25 ` Adam Porter
2021-09-25 19:51 ` Timothy
2021-09-26 0:37 ` Adam Porter
2021-09-26 3:42 ` Timothy
2021-09-26 5:46 ` Adam Porter
2021-09-26 8:29 ` Stefan Nobis
2021-09-26 8:56 ` Timothy
2021-09-26 10:40 ` Stefan Nobis
2021-09-27 15:45 ` Eric S Fraga
2021-09-27 18:01 ` Thomas S. Dye
2021-09-26 12:12 ` Max Nikulin [this message]
2021-10-02 8:17 ` Timothy
2021-10-02 11:11 ` Adam Porter
2021-10-02 11:29 ` Timothy
2021-10-02 12:07 ` Adam Porter
2021-10-02 12:00 ` Eric S Fraga
2021-10-02 18:24 ` Thomas S. Dye
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 \
--in-reply-to='sipo40$jn2$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public 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).