vim_multibyte Google Group

Re: Combining characters U+035x are not supported?

b...@moolenaar.net (Bram Moolenaar) — Mon, 04 Jan 2010 19:17:31 UT

There is a script to generate these tables from the Unicode table.
I think Markus Kuhn had this. But it should be easy to reproduce with
Vim script.
Changing all these tables from short to int makes the memory use higher.
But adding code to handle two tables won't be much smaller.

Re: Combining characters U+035x are not supported?

antoine.mechely...@gmail.com (Tony Mechelynck) — Sun, 03 Jan 2010 04:30:16 UT

I see. I suspect other size changes may have to be done then, not only
where the structure is defined but possibly where it is used. I hope
Bram is following this whole thread.
Best regards,
Tony.

Re: Combining characters U+035x are not supported?

yongj...@gmail.com (Iông Chun) — Sun, 03 Jan 2010 02:54:36 UT

Because:
<code>
struct interval
{
unsigned short first;
unsigned short last;
</code>
;)
I guess the type can be "int" instead of "unsigned short" now.
The patch with all Mn and Me character ranges is attached.
Regards,
Iông Chun

Re: Combining characters U+035x are not supported?

antoine.mechely...@gmail.com (Tony Mechelynck) — Sat, 02 Jan 2010 16:24:16 UT

Why without codepoint values higher than U+FFFF? Nowadays gvim can
diplay them (which wasn't the case when I started studying Unicode with
gvim 6.x).
Best regards,
Tony.

Re: Combining characters U+035x are not supported?

yongj...@gmail.com (Iông Chun) — Sat, 02 Jan 2010 14:47:39 UT

Hi Tony,
I should also make use of UnicodeData.txt, instead of looking into every
added code point,
and check the code charts ;)
About Canonical_Combining_Class, from the Standard version 5.2, D52,
item#2, I read:
<quote>
All characters with non-zero canonical combining class are combining charac-

Re: Combining characters U+035x are not supported?

antoine.mechely...@gmail.com (Tony Mechelynck) — Sat, 02 Jan 2010 11:01:26 UT

I'm attaching an extract from the current UnicodeData.txt file where
I've extracted all codepoints with a nonzero Canonical_Combining_Class
(field 3, counting the first field [codepoint number] as field 0). I'm
*not* sure that this property coincides with the "combining character"
property in the Vim sense, but it's the best I've found. You can check

Re: Combining characters U+035x are not supported?

yongj...@gmail.com (Iông Chun) — Sat, 02 Jan 2010 10:43:49 UT

Hi all,
This is a patch to update combining character table from Unicode 5.2.
I add these by eyes and hands, so there might be errors ;)
<patch>
--- work/vim72/src/mbyte.c.bak 2010-01-02 13:33:40.000000000 +0800
+++ work/vim72/src/mbyte.c 2010-01-02 18:33:49.000000000 +0800
@@ -1976,35 +1976,64 @@
/* sorted list of non-overlapping intervals */

Re: Combining characters U+035x are not supported?

yongj...@gmail.com (Iông Chun) — Sat, 02 Jan 2010 08:30:11 UT

Hi Tony and list,
I understand now.
Characters ranged from U+0350 to U+0357, and from U+035D to U+035F,
are added in Unicode 4.0.
Characters ranged from U+0358 (which I used) to U+035C are added even
later in Unicode 4.1.
Check this from this docuent: [link]

Re: Combining characters U+035x are not supported?

antoine.mechely...@gmail.com (Tony Mechelynck) — Sat, 02 Jan 2010 05:25:31 UT

According to the current version (5.2) of the Unicode Standard, all
codepoints U+0300 to U+036F are indeed combining characters AFAICT, see
[link]
However, those in the range U+0350 to U+035F are particularly
"esoteric", and I believe that it is possible that they were added in a

Combining characters U+035x are not supported?

yongj...@gmail.com (Iông Chun) — Sat, 02 Jan 2010 03:47:12 UT

Happy new year, everyone!
I use Vim to edit an input method table these days, and find that
it doesn't work well with one combining character, Unicode U+0358.
Using g8 on "capital O with dot above right" shows "4f" only,
and the dot is another character ("cd 98").
I look from the source to see how Vim check if a character is a

Printing with utf-8 characters on Windows

thm...@gmail.com (Đức Minh Thái) — Sun, 20 Dec 2009 16:36:27 UT

Hello,
I cannot get utf-8 characters printed correctly. For example:
bột
becomes
bá»™t
My printing options are:
set printfont=LMMono10:h10 " This is the LMMono from LaTeX Latin Modern
set printoptions=number:y
set printencoding=ucs-2le bomb
Please help. Thank you!

Vim calendar and T-shirt

b...@moolenaar.net (Bram Moolenaar) — Sun, 13 Dec 2009 12:44:29 UT

Hello Vim users!

The Vim calendar has been updated for 2010. I replaced the info about
my old A-A-P project with Zimbu, which you probably find a bit more
interesting. You can find the calendar in PDF format, ready to print,
here: [link]

You can now order a T-shirt and Polo with the Vim logo from Freewear.

RE: ANSI<>UNICODE and reverse

johnb.beck...@gmail.com (John Beckett) — Fri, 06 Nov 2009 02:22:46 UT

See discussion in vim_use
[link]
John

Re: ANSI<>UNICODE and reverse

winterttr....@gmail.com (winterTTr) — Fri, 06 Nov 2009 00:54:24 UT

What's the value for the option "encoding" ?
if the "encoding" is set to utf-8 when you don't set "fenc" , the file
will open with the same encoding as what you set to enc , which should
become 'utf8'

What do you mean for the "The same coding "?
The coding is always ANSI or UNICODE?

ANSI<>UNICODE and reverse

win...@people.it (wintec Paolo Baruffa) — Thu, 05 Nov 2009 11:56:49 UT

Hi all!
I need to perform ANSI/UNICODE commands in my GVIM.
I read many docs on the web about and I did set these:
"----------------------------- -------------
" .vimrc includes
"----------------------
" (no fileencoding is set in .vimrc)
"----------------------------- -------------
" my menu includes