Yukihiro Nakadaira wrote: > On Tue, Feb 21, 2012 at 7:10 PM, raf <[email protected]> wrote: > > Yukihiro Nakadaira wrote: > > > >> On Mon, Feb 13, 2012 at 10:19 AM, raf <[email protected]> wrote: > >> > i just upgraded my vim and applied this patch but it didn't affect > >> > the failing of test83 for me. this patch assumes that the cause of > >> > the failure was iconv not supporting cp932 but iconv on macosx-10.6.8 > >> > and ubuntu-11.04 do support cp932. i checked that at the time when > >> > Yukihiro Nakadaira suggested it. > >> > >> I have no idea why it fails. > >> Could you run test case 2 by hand? > >> > >> $ cd vim/src/testdir > >> $ cat >Xtags2.txt <<EOF > >> > text for tags2 > >> > ＡＢＣ > >> > EOF > >> $ ../vim -u NONE > >> :set tags=test83-tags2 > >> :tag /.ＢＣ > >> -- > >> Yukihiro Nakadaira - [email protected] > > > > vim says: E426: tag not found: .ＢＣ > > Thank you. > > Is 'encoding' utf-8?
yes, it is. > If not, retry ":tag /.ＢＣ" command after ":set enc=utf-8". i tried this anyway and it still didn't work. > Perhaps it is iconv problem. If so, latin1 should work because Vim > perform utf8-latin1 conversion itself. I attached test file for latin1. > Try the following command. > > :set enc=utf-8 > :set tags=latin1.tags > :tag /.ÂÃ > -- > Yukihiro Nakadaira - [email protected] that did work. it took me to line 3 of latin1.txt (which is encoded in utf-8). the libiconv that this version of vim (X11-Motif) is using is the one from MacPorts (/opt/local/lib/libiconv.2.dylib (v1.14)). the libiconv that the system-supplied version of vim (/usr/bin/vim) is using is the system-suplied one (/usr/lib/libiconv.2.dylib). if i repeat the test using the system-supplied vim (/usr/bin/vim) the behaviour is different: vim says: E434: Can't find tag pattern and then takes me to line 1 of Xtags2.txt (but not to line 2 where the tagged text is). however, the MacPorts non-gui version of vim (/Applications/MacPorts/MacVim.app/Contents/MacOS/Vim) is using the MacPorts version of libiconv but it is exhibiting the same behaviour as the system-supplied version of vim described above. i can't tell what version of libiconv is being used by the MacPorts version of gui vim (it doesn't show up in otool -l) (/Applications/MacPorts/MacVim.app/Contents/MacOS/MacVim) but it's behaviour is also the same as the system-supplied version of vim. so the mapping between libiconv and behaviour isn't consistent. i am seeing the same behaviour on a linux system (the system-supplied vim on linux behaves like the system-supplied vim on macosx and my compiled vim on linux behaves the same as my compiled vim on macosx) but there is no libiconv at all on the linux host (it has /usr/bin/iconv). in summary: behaviour 1 = E426: tag not found: .ＢＣ behaviour 2 = E434: Can't find tag pattern macosx ubuntu my vim 1 1 system vim 2 2 macports Vim 2 macports MacVim 2 cheers, raf p.s. i don't think it's relevant but when running vim in xterm, the characters ＡＢＣ are displayed correctly when viewing/editing a file and when pasting them in vim's command line to do the :tag command but they are not displayed correctly in the tag-not-found error message. there, they just look like dotted boxes. i figure that can't be a font problem. actually, maybe it is. the error message is in bold. maybe the bold version of that fon't doesn't have those characters but the regular version does. no, that's not it. if i change the xterm font to be the bold version, the same behaviour happens. -- 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
