From: Eric Wong <e@80x24.org>
To: Hongli Lai <hongli@phusion.nl>
Cc: Michael Fischer <mfischer@zendesk.com>,
Gary Grossman <gary.grossman@gmail.com>,
unicorn-public <unicorn-public@bogomips.org>,
Michael Grosser <michael@grosser.it>
Subject: Rack encodings (was: Please move to github)
Date: Mon, 4 Aug 2014 08:48:06 +0000 [thread overview]
Message-ID: <20140804084806.GA22323@dcvr.yhbt.net> (raw)
In-Reply-To: <CAM3ce8GnCGaODj0SptDW2cTF_cQQS1eBZH1n5E5Xs7J_0DL8Zw@mail.gmail.com>
(Long overdue Subject: change)
Hongli Lai <hongli@phusion.nl> wrote:
> Hi guys. Phusion Passenger author here. I would very much support
> standardization of encoding issues.
> At this point, I don't really care what the standard is, as long as
> it's a sane standard that everybody can follow.
Fair enough. Would you/Phusion be comfortable taking the lead here?
This feels like another "hot potato" issue :>
> In my opinion, following Encoding.default_external is not helpful.
> Most users have absolutely no idea how to configure
> Encoding.default_external, or even know that it exists. I've also
> never, ever seen anybody who does *not* want default_external to be
> UTF-8. If it's not set to UTF-8, then it's always by accident (e.g.
> the user not knowing that it depends on LC_CTYPE, that LC_CTYPE is set
> differently in the shell than from an init script, or even what
> LC_CTYPE is).
Perhaps we need to educate users to set LC_CTYPE/LC_ALL/LANG so
Encoding.default_external works as intended? Adding another
option to Rack will just as likely to get missed.
Maybe servers could emit a big warning saying:
WARNING: Encoding.default_external is not UTF-8 ...
And add a --quiet-utf8-warning option for the few folks who really do
not want UTF-8.
next prev parent reply other threads:[~2014-08-04 8:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 7:51 Please move to github Gary Grossman
2014-08-02 7:54 ` Kapil Israni
2014-08-02 8:02 ` Eric Wong
2014-08-02 8:50 ` Eric Wong
2014-08-02 19:07 ` Gary Grossman
2014-08-02 19:33 ` Michael Fischer
2014-08-04 7:22 ` Hongli Lai
2014-08-04 8:48 ` Eric Wong [this message]
2014-08-04 9:46 ` Rack encodings (was: Please move to github) Hongli Lai
2014-08-02 20:15 ` Please move to github Eric Wong
-- strict thread matches above, loose matches on Subject: below --
2014-08-05 5:56 Rack encodings (was: Please move to github) Gary Grossman
2014-08-05 6:28 ` Eric Wong
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://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140804084806.GA22323@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=gary.grossman@gmail.com \
--cc=hongli@phusion.nl \
--cc=mfischer@zendesk.com \
--cc=michael@grosser.it \
--cc=unicorn-public@bogomips.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://yhbt.net/unicorn.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).