From: "François Téchené" <francois.techene@puri.sm>
To: libreplanet-discuss@libreplanet.org
Subject: Re: UTF-8 banned from being default in Chrome, Firefox
Date: Sun, 20 Aug 2017 11:09:30 +0200 [thread overview]
Message-ID: <8724d1ce-90dc-15e9-2b11-f0b6ec543406@puri.sm> (raw)
In-Reply-To: <618232be-9704-fec8-c536-a0eebaa78eb6@forestfield.org>
On 08/20/2017 01:05 AM, J.B. Nicholson wrote:
> 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).
>
I join J.B.'s point on this.
You cannot lose freedom just because the software developers decided to
drop a feature. This being inconvenient has nothing to do with software
freedom. When a free software is missing a feature, anyone is free to
modify it's code to implement this feature.
If not already done, just drop an issue on the Firefox bugs tracker.
If this feature loss is annoying too many users there may be a patch for
it in future releases... or even an (hopefully free) add-on.
> _______________________________________________
> libreplanet-discuss mailing list
> libreplanet-discuss@libreplanet.org
> https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
--
François Téchené
Director of Creative @Purism
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2017-08-20 13:52 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
2017-08-20 9:09 ` François Téchené [this message]
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=8724d1ce-90dc-15e9-2b11-f0b6ec543406@puri.sm \
--to=francois.techene@puri.sm \
--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).