Hi,
At Sun, 1 Apr 2001 16:32:41 -0500 (EST),
<[EMAIL PROTECTED]> wrote:
> I have noticed one problem with this: characters like U+300A, U+300B and
> U+201C, U+201D are single column according to my_wcwidth(), but simsun.ttf
> display them as double column. Especially U+300A and U+201C, when it is
> displayed, it is overwritten by the character following it.
Do you know Robert Brady's patch? The newest version of his patch
(http://www.xfree86.org/pipermail/i18n/2001-March/001380.html)
has three width modes. Though there three modes are not yet perfect
for CJK people, it covers almost cases. (Some imperfectness come from
problem of conversion table between Unicode and other encodings.)
Robert is one of active developers of XTerm. AFAIK, the doublewidth
and combining character support of current XTerm is written by him.
I expect his newest patch for locale-sensibility/XIM/language-tag/bidi/etc
is also integrated into XTerm sooner or later.
Note that the patch is XTerm-152-based.
BTW, XTerm has a policy that doublewidth character is supported using
another font from normalwidth character. Thus, it does not support,
for example, GNU unifont. Though I don't checked your patch yet,
your patch seems to be like a support for GNU unifont (if your patch
is extended to support not only FreeType but also normal font).
I don't know how strong the policy is, because the policy has been
already determined when I joined the development of XTerm. IMO, if
"common font both for singlewidth and doublewidth" way is proved to
be convenient, it may be supported, though it may bring width-conflict
problem.
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
