emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Stefan Nobis <stefan-ml@snobis.de>
To: emacs-orgmode@gnu.org
Subject: Re: [Worg] Proposing a few CSS changes
Date: Sun, 26 Sep 2021 10:29:16 +0200	[thread overview]
Message-ID: <m1lf3jbuzn.fsf@nobis-it.eu> (raw)
In-Reply-To: <87sfxropnl.fsf@alphapapa.net> (Adam Porter's message of "Sun, 26 Sep 2021 00:46:06 -0500")

Adam Porter <adam@alphapapa.net> writes:

> So I think it's very important to respect the user's settings,
> especially for long texts and documentation (i.e. not the "home page"
> parts of Web sites whose purpose is to present projects as a whole).

+1.

HTML pages are neither books nor PDFs nor advertising columns. I have
a LaTeX background and I like to tweak the micro-typography of my PDF
documents (and I find many documents out there quite ugly and hard to
read). Therefore I think I understand and kind of sympathize with
Timothoys point of view.

But the web is quite a different beast. User choices like
Window/viewport size, fonts (serif, non-serif, size,...) are way too
often ignored and even battled against. Sometimes I get the
impression, that every time a web designer gets informed about a new
way for users to override design decisions they try to block these
possibilities - and in most cases to the disadvantage of users.

Yes, today seldom people play with the font settings in their
browsers. But why? I think, because they see that these settings seem
to never really work. Even if you configure your browser to ignore
font settings from HTML/CSS and always use the browser settings, many
pages will be next to unreadable - the layout breaks down, if the
wrong fonts/sizes are used.

Therefore I support Adams wish to honor the configuration of users.
The web should be more seen as a documentation system, not an
installation of art.

-- 
Until the next mail...,
Stefan.


  reply	other threads:[~2021-09-26  8:29 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 [this message]
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
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=m1lf3jbuzn.fsf@nobis-it.eu \
    --to=stefan-ml@snobis.de \
    --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).