Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] ncurses hack
Date: Mon, 17 Aug 2009 19:43:18 -0700	[thread overview]
Message-ID: <1250563136-sup-432@masanjin.net> (raw)
In-Reply-To: <1250538875-sup-2195@javelin>

Reformatted excerpts from Edward Z. Yang's message of 2009-08-17:
> Today, I decided to throw in the towel and patch my copy of ncurses to
> have the appropriate fix for international characters + tabs.  Does
> anyone know of a list of instructions for carrying this out?

Try http://sup.rubyforge.org/wiki/wiki.pl?UTF8. If you're running Sup
git, I've made a nice branch for this:

  $ git branch --track ncursesw origin/ncursesw
  $ git checkout ncursesw
  $ cd ncurses-0.9.1/
  $ ./run-this-for-sup.sh

Which will generate an ncurses.so file in lib/. You can then switch back
to master or next and it should pick it up.

This should fix many wide-character issues but it won't fix all of them,
because there's still no way of determining the display width of a
unicode character (e.g. Chinese characters take two columns to display).
So the display still ends up funny.

Ruby 1.9 has better encoding support but I don't know if it fixes this.
-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2009-08-18  2:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 19:54 Edward Z. Yang
2009-08-18  2:43 ` William Morgan [this message]
2009-08-18  7:42   ` Dusan
2009-08-18 18:24     ` Benoît PIERRE
2009-08-18 18:46       ` Dusan
2009-08-18 18:59         ` Benoît PIERRE
2009-08-18 19:04           ` Dusan
2009-08-18 19:24           ` Dusan
2009-08-18 19:31       ` Jörg-Hendrik Bach

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=1250563136-sup-432@masanjin.net \
    --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