Dnia 11-05-2007 o godz. 14:45 Bram Moolenaar napisał(a):
> Mikolaj Machowski wrote:
>
> > Vim 7.1b on Windows XP doesn't properly recognizes words. It does not
> > count Polish diacritics in, so each one is treated as separate word.
> >
> > This is serious bug and with taking into account that Windows users can
> > have problems with getting patched versions it is IMO showstopper.
> >
> > In its nature it may be similar to bug fixed by 6.3.052 - not proper
> > recognition of non ASCII characters (but inserting works).
> >
> > On Linux everything works OK.
> >
> > gvim7.1b from ftp.vim.org
> > v:lang = PL
> > v:lc_time = Polish_Poland.1250
> > &encoding = cp1250
>
> What do you mean with recognizing a word? What commands do you use?
Eg. diw
For example when using diw on 'łąka' (meadow) on 1st character it
removes only first two characters, the same for 2nd character, when
using on 3rd or 4th char it removes last 2 chars.
>
> What version of Vim (console/GUI/...)? Did you compile yourself or use
> one of the distributed binaries? What is the ":version" output?
*G*vim binaries from ftp.vim.org
VIM - Vi IMproved 7.1b BETA (2007 May 10, compiled May 10 2007 17:57:09)
MS-Windows 32 bit GUI version
Compiled by [EMAIL PROTECTED]
Big version with GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+cindent +clientserver +clipboard +cmdline_compl +cmdline_hist
+cmdline_info +comments
+cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs -dnd
-ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path
+find_in_path
+folding -footer +gettext/dyn -hangul_input +iconv/dyn +insert_expand
+jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds
+localmap +menu
+mksession +modify_fname +mouse +mouseshape +multi_byte +multi_lang
-mzscheme +netbeans_intg -ole -osfiletype +path_extra -perl -postscript
+printer
-profile -python +quickfix +reltime +rightleft -ruby +scrollbind +signs
+smartindent -sniff +statusline -sun_workshop +syntax +tag_binary
+tag_old_static
-tag_any_white -tcl -tgetent -termresponse +textobjects +title +toolbar
+user_commands +vertsplit +virtualedit +visual +visualextra +viminfo
+vreplace
+wildignore +wildmenu +windows +writebackup -xfontset -xim -xterm_save
-xpm_w32
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\_vimrc"
2nd user vimrc file: "$VIM\_vimrc"
user exrc file: "$HOME\_exrc"
2nd user exrc file: "$VIM\_exrc"
system gvimrc file: "$VIM\gvimrc"
user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$VIM\_gvimrc"
system menu file: "$VIMRUNTIME\menu.vim"
Compilation: cl -c /W3 /nologo -D_MT -MT -I. -Iproto -DHAVE_PATHDEF
-DWIN32 -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DWINVER=0x0400
-D_WIN32_WINNT=0x0400 /Fo.\ObjG/ /Ox -DNDEBUG -DFEAT_GUI_W32
-DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_BIG /Zi /Fd.\ObjG/
Linking: link /RELEASE /nologo /subsystem:windows /incremental:no
/nodefaultlib:libc advapi32.lib shell32.lib gdi32.lib comdlg32.lib
ole32.lib uuid.lib oldnames.lib kernel32.lib gdi32.lib version.lib
winspool.lib comctl32.lib advapi32.lib shell32.lib /machine:i386
/nodefaultlib libcmt.lib user32.lib WSock32.lib /PDB:gvim.pdb
-debug
> What is 'iskeyword' set to and where was it set?
When started normally
@,48-57,_,128-167,224-235
When -U NONE
@,48-57,_
> What if you use "vim
> -u NONE"?
The same.
>
> Very likely this is a problem in your setup, not in Vim. So please
> check your setup carefully before blaming Vim.
This is Vim problem and not only mine. I've got reports about that from
other Polish users.
----------------------------------------------------
INFERNAL: "From Paris to Berlin"
Potężna dawka hitów! CD+DVD już w sklepach!
http://klik.wp.pl/?adr=http%3A%2F%2Fadv.reklama.wp.pl%2Fas%2Finfernal.html&sid=1138
