Bug#541704: [emacs-w3m:10999] Re: bug#4090: Bug#541704: emacs-snapshot ruins w3m-el-snapshot tables

2009-08-19 Thread Kenichi Handa
92)) => 1 > ・Emacs23.1 > (char-width (make-char 'mule-unicode-2500-33ff 32 92)) => 2 FYI, with Emacs 23, in non-CJK environment, that value is 1. --- Kenichi Handa ha...@m17n.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#541704: bug#4090: Bug#541704: emacs-snapshot ruins w3m-el-snapshot tables

2009-08-18 Thread Kenichi Handa
no idea why Emacs can't draw them even if that font is selected. --- Kenichi Handa ha...@m17n.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#541704: bug#4090: Bug#541704: emacs-snapshot ruins w3m-el-snapshot tables

2009-08-18 Thread Kenichi Handa
In article <873a7poeoy@jidanni.org>, jida...@jidanni.org writes: >>>>>> "K" == Kenichi Handa writes: >>> In the trunk of CVS, I added CJK fonts for those box-drawing >>> characters in the default fontset. So, in CJK environment, >>

Bug#541704: bug#4090: Bug#541704: emacs-snapshot ruins w3m-el-snapshot tables

2009-08-17 Thread Kenichi Handa
o, in CJK environment, CJK fonts are preferred. Perhaps, the selected CJK font claims that it has glyphs for those characters, but actually doesn't contain valid glyphs. I think those vanishing characters has at least 1 dot width of space. Please put cursor on one of them and type C-u C

Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode]

2007-08-29 Thread Kenichi Handa
input. Please tell me what is shown by ESC : (current-input-mode) RET > I guess I'm just displaying my lack of familiarity with how terminals > work... >>> What other choices were tried? utf-8, latin-X should all >>> work. What is your locale? > With a "

Bug#130397: Bug 130397

2005-01-19 Thread Kenichi Handa
In article <[EMAIL PROTECTED]>, Juri Linkov <[EMAIL PROTECTED]> writes: > Now a new problem was uncovered: after selecting a correct word from > a list of near misses returned from ispell, ispell.el replaces the > misspelled word with a selected word, and inserts it into the buffer > not in its ori

Bug#130397: Bug 130397

2005-01-18 Thread Kenichi Handa
In article <[EMAIL PROTECTED]>, Juri Linkov <[EMAIL PROTECTED]> writes: > Kenichi Handa <[EMAIL PROTECTED]> writes: >> Please try the latest ispell.el. I think at least this >> misalignment error is fixed now. > I tried the latest ispell.el and

Bug#130397: Bug 130397

2005-01-13 Thread Kenichi Handa
In article <[EMAIL PROTECTED]>, David Kastrup <[EMAIL PROTECTED]> writes: >>> If ispell wants utf-8, it's easy enough to convert each input line to >>> utf-8 and deal with offsets into that in the event of a mispelling; >> >> Or account for byte offsets by (variable) multibyte lenght of each >>

Bug#130397: Bug 130397

2005-01-12 Thread Kenichi Handa
In article <[EMAIL PROTECTED]>, Juri Linkov <[EMAIL PROTECTED]> writes: > Agustin Martin <[EMAIL PROTECTED]> writes: >> *Ken*, since you are being cc'ed I vaguely remembered some info I somewhere >> read about this misalignements. I finally found it, >> >> http://lists.gnu.org/archive/html/em

Bug#130397: Bug 130397 (Was: Emacs - Ispell problem with i[no]german dictionary)

2005-01-12 Thread Kenichi Handa
In article <[EMAIL PROTECTED]>, Richard Stallman <[EMAIL PROTECTED]> writes: > People have been discussing this issue for a while now, > and due to the volume of mail, I could not read it all. I'm reading it, and I think I understand what is the problem. > Handa, is it clear what we should do no

Bug#130397: Bug 130397 (Was: Emacs - Ispell problem with i[no]german dictionary)

2005-01-11 Thread Kenichi Handa
In article <[EMAIL PROTECTED]>, Agustin Martin <[EMAIL PROTECTED]> writes: > I meant with oe-1char oe as a single char (U+0153), available > in iso-8859-15 (octal \275 here), but not in iso-8859-1 (you > have one half instead), and with oe-2char the two 7bit chars sequence > 'oe', available anywher

Bug#130397: Bug 130397 (Was: Emacs - Ispell problem with i[no]german dictionary)

2005-01-10 Thread Kenichi Handa
In article <[EMAIL PROTECTED]>, Agustin Martin <[EMAIL PROTECTED]> writes: > (Handa, your patch worked better than I thought, read below) Thank you, that's a good news. > Also Kenichi Handa provided us with a patch to ensure that all equivalent > accented chars are m