From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.79.193 with SMTP id q1cs43183bkk; Thu, 13 May 2010 05:34:31 -0700 (PDT) Received: by 10.224.43.100 with SMTP id v36mr6036454qae.201.1273754069736; Thu, 13 May 2010 05:34:29 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 27si957474qyk.56.2010.05.13.05.34.29; Thu, 13 May 2010 05:34:29 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id EFC861858346; Thu, 13 May 2010 08:34:25 -0400 (EDT) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 2737E185831A for ; Thu, 13 May 2010 08:33:50 -0400 (EDT) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1OCXbq-0003JT-LJ for sup-devel@rubyforge.org; Thu, 13 May 2010 08:33:50 -0400 From: William Morgan To: sup-devel In-reply-to: References: <1273250528-sup-9662@zyrg.net> <1273605454-sup-2267@masanjin.net> Date: Thu, 13 May 2010 08:33:50 -0400 Message-Id: <1273753871-sup-7238@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-devel] Arch utf8 vs UTF-8 fix and wide character support X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org 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 _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel