From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] the proper way of determining the encoding
Date: Sun, 06 Jan 2008 22:04:21 -0800 [thread overview]
Message-ID: <1199685831-sup-2011@south> (raw)
In-Reply-To: <1199569265-sup-4567@clarabella.clarabella>
Excerpts from Giorgio Lando's message of Sat Jan 05 13:46:43 -0800 2008:
> I had initially some problems with encoding in sup (accented chars
> were not displayed). So I have looked in lib/sup.rb and I have seen
> that sup tries to determine the $encoding from the $ctype, determined
> on its turn by LC_CTYPE and LANG. This failed in my case (I do not
> know why: my $LANG is it_IT and my $LC_ALL - implying $LC_CTYPE - is
> it_IT at euro).
The current way I choose the encoding is a complete hack, and clearly
doesn't work for your case. (It looks for a .<something> at the end of
LANG or LC_CTYPE). But I'm not really sure what the correct way is.
What does this command produce on your system? "locale -c LC_CTYPE |
head -6".
> $encoding = ENV["CHARSET"]
I don't really want to use a non-standard environment variable if at all
possible...
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-01-07 6:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 21:46 Giorgio Lando
2008-01-07 6:04 ` William Morgan [this message]
2008-01-07 8:44 ` Giorgio Lando
2008-01-07 8:51 ` Giorgio Lando
2008-01-09 18:00 ` William Morgan
2008-01-10 0:39 ` Giorgio Lando
2008-01-13 2:22 ` William Morgan
2008-01-13 13:09 ` Giorgio Lando
2008-01-15 16:30 ` Grant Hollingworth
2008-01-16 1:45 ` William Morgan
2008-01-16 2:20 ` Nicolas Pouillard
2008-01-16 2:57 ` William Morgan
2008-01-16 3:09 ` William Morgan
2008-01-16 8:51 ` Nicolas Pouillard
2008-01-16 3:14 ` Nicolas Pouillard
2008-01-16 3:23 ` William Morgan
2008-01-16 3:28 ` Nicolas Pouillard
2008-01-16 3:38 ` William Morgan
2008-01-16 8:46 ` Nicolas Pouillard
2008-01-18 16:40 ` Nicolas Pouillard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1199685831-sup-2011@south \
--to=wmorgan-sup@masanjin.net \
/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