LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "J.B. Nicholson" <jbn@forestfield.org>
To: libreplanet-discuss@libreplanet.org
Subject: Re: UTF-8 banned from being default in Chrome, Firefox
Date: Sat, 19 Aug 2017 18:05:15 -0500	[thread overview]
Message-ID: <618232be-9704-fec8-c536-a0eebaa78eb6@forestfield.org> (raw)
In-Reply-To: <9c5bcec9-9b3f-12be-d254-2579351d0c9b@nominal-animal.net>

Nominal Animal wrote:
> We've lost another freedom, choosing the default character set encoding
> in Firefox and Chrome/Chromium browsers.

That sounds like upstream developers are making something you want more 
inconvenient. We should distinguish between what's going on with Firefox (a 
free software browser) and Chrome (a nonfree browser).

Users aren't losing freedoms either way: Firefox remains editable (as you 
say in your post) and Chrome users never had software freedom with Chrome 
(so they can't lose what they never had).

_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

  parent reply	other threads:[~2017-08-19 23:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19  9:10 UTF-8 banned from being default in Chrome, Firefox Nominal Animal
2017-08-19 21:29 ` Andy Oram
2017-08-19 22:36   ` Nominal Animal
2017-08-19 23:05 ` J.B. Nicholson [this message]
2017-08-20  9:09   ` François Téchené
2017-08-20 10:32   ` David Hedlund

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://lists.gnu.org/mailman/listinfo/libreplanet-discuss

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

  git send-email \
    --in-reply-to=618232be-9704-fec8-c536-a0eebaa78eb6@forestfield.org \
    --to=jbn@forestfield.org \
    --cc=libreplanet-discuss@libreplanet.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 read-only IMAP folder(s) and NNTP newsgroup(s).