[Redirecting to vim-dev (looks buggy, and at the least is very techy).]
On Tue, 26 Jul 2011, Caleb Eggensperger wrote:
I think this is a bug. With ambiwidth=double, the unicode character '₀' (U+2080, the subscript '0') is single-width, but '₁-₉' (U+2081-U+2089, subscripts 1-9) are double-width.
The current Vim sources list: 0x2081 - 0x2084 (subscripts 1-4) as ambiguous. (src/mbyte.c line 1323) Here's the whole set for testing: ₀₁₂₃₄₅₆₇₈₉ Alternatively, use this test program to generate that range: perl -CDS -lwe 'print map chr, 0x2080..0x2089'
From my reading of http://unicode.org/reports/tr11/, none of these characters should be considered to be of ambiguous width (they should all be single-width).
In whatever font rxvt-unicode is currently using, ₁₂₃₄ indeed shows up incorrectly. (even outside of Vim). Is this something that changed?
/usr/lib/perl5/5.12.1/unicore/UnicodeData.txt doesn't seem to indicate that there's a difference (looks like it's Unicode 5.2).
(I apologize if this is the wrong place to report bugs. I was directed here by http://sourceforge.net/tracker/?atid=391887&group_id=27891)
Yikes. Looks like there are quite a few misdirected bug reports on that tracker. (some for Vim itself, some for plugins)
-- Best, Ben -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
