Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: israel.herraiz@gmail.com (Israel Herraiz)
Subject: [sup-talk] System encoding versus messages encoding
Date: Wed, 23 Apr 2008 02:09:41 +0200	[thread overview]
Message-ID: <1208908666-sup-5839@elly> (raw)
In-Reply-To: <1208905597-sup-4977@south>

Excerpts from William Morgan's message of Wed Apr 23 01:18:00 +0200 2008:
> The good news is that I've just made it slightly simpler, at least if
> you're running from git. I've published an "ncursesw" branch that
> contains a hacked ncurses-0.9.1 and a dirty script to install it into
> your ../lib/ directory. If you use that AND you run from git next,
> you'll see wide characters. It works!

Great. I have obtained the new changes from the git repository, and
applied the recipe that you give, and yes, it works! Thanks!

I am noting only another odd thing: when I press enter to from the
inbox-mode to the thread-mode, some characters of the inbox view
"persists" in the screen. I will file the bug if you consider that it
is necessary. 

> A gold star to anyone who makes a nice wiki page out of this.

I guess that is my turn :-). I will add a page about UTF-8 with a
summary of this message and the message that you link.

Thanks again for your help.

Cheers,
Israel


  reply	other threads:[~2008-04-23  0:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21 20:37 Israel Herraiz
2008-04-22 11:39 ` Shot (Piotr Szotkowski)
2008-04-22 23:18 ` William Morgan
2008-04-23  0:09   ` Israel Herraiz [this message]
2008-04-23  2:03     ` William Morgan
2008-04-23  1:08   ` Israel Herraiz
2008-04-23  1:53     ` William Morgan
2008-04-24 19:36     ` Marc Hartstein
2008-04-24 23:10   ` [sup-talk] [PATCH] fixed dlopen of libc for os x Grant Hollingworth

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=1208908666-sup-5839@elly \
    --to=israel.herraiz@gmail.com \
    /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