From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Arch utf8 vs UTF-8 fix and wide character support
Date: Thu, 13 May 2010 08:33:50 -0400 [thread overview]
Message-ID: <1273753871-sup-7238@masanjin.net> (raw)
In-Reply-To: <t2s6242182a1005111451uc2781ca0rcd97dbf6d3146684@mail.gmail.com>
Reformatted excerpts from Matti Eiden's message of 2010-05-11:
> Oh right, splitting. Yes right, makes sense. I tried your
> console/string, seems good, except the display_split ignores the
> padding request? Or did I understand this feature wrongly? I mean, it
> slices the string exactly where the end offset is, not by the nearest
> " ", space?
The padding only comes into play when you ask it to slice a string in
the middle of a multi-column character. It will then pad the
left/right/both ends of the string to make the total display width of
the returned string what you asked for.
> With quick testing for resizing the window with different kind of test
> emails, I see no lost characters or text corruption.
Awesome. I'll see what I can do about 1.8-compatibility.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2010-05-13 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <y2j6242182a1005061059w5e32fb54vd10ccfd7e4a1911e@mail.gmail.com>
2010-05-06 18:02 ` Matti Eiden
2010-05-07 16:46 ` Rich Lane
2010-05-11 18:50 ` Matti Eiden
2010-05-11 19:19 ` William Morgan
2010-05-11 21:51 ` Matti Eiden
2010-05-13 12:33 ` William Morgan [this message]
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=1273753871-sup-7238@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@rubyforge.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