Stable version is not stable in multi-byte environment

[GoogleCodeExporter]

IMPORTANT! Before creating a new Issue please search the old Issues for 
duplicates.  Also, 
please do not use this page to ask questions, instead post to the vim_mac 
mailing list.  There are 
more people on that list that can answer questions.  Only file an issue if you 
have found a bug.  
(You can safely delete this text now that you have read it and enter an issue 
report.  Thank you 
for taking the time to report new bugs!)

What steps will reproduce the problem?

1. Drag the files from a directory which named with Korean, and drop the file 
to a stable version 
of macvim
2. The macvim cannot open the file properly.

What is the expected output? What do you see instead?

1. Dropped file should be opened but blank screen appears

What version of MacVim and OS X are you using (see "MacVim->About MacVim" and  
"Apple 
Menu->About This Mac" menu items, e.g. "Snapshot 40, 10.5.6 Intel")?

Macvim 7.2 Stable-1_2
OS X 10.5.7

Please provide any additional information below.

I don't know which options are used to build the stable release, however a 
macvim built with 
macports doesn't have a bug related with multi-byte strings.

Original issue reported on code.google.com by nae...@gmail.com on 31 Jul 2009 at 3:28

[GoogleCodeExporter]

This bug was recently fixed.  Please download the latest snapshot and let me 
know if that fixes the problem.

Original comment by bjorn.winckler@gmail.com on 31 Jul 2009 at 11:59

[GoogleCodeExporter]

Thx for comment ;) I tried snapshot 47 and I can open file in path which 
contains multi-byte character properly. 

This bug was critical to users who uses CJKV(Chinese, Japanese, Korean, 
Vietnam) environment. so I revcommend 
u to update the stable release. ;)

Original comment by nae...@gmail.com on 31 Jul 2009 at 3:55

[GoogleCodeExporter]

Well, its not exactly a critical bug (nothing crashes) and it is not too hard 
to work around it (just open files with 
":fin" etc.).  Making a new stable build however is a bit of an effort for me, 
so anybody with this particular 
problem should just use the snapshot for now.  As far as I know there are no 
downsides to using snapshot 47 - 
it is just as stable as the "stable" build, plus it contains many improvements.

Original comment by bjorn.winckler@gmail.com on 31 Jul 2009 at 5:31

• Changed state: WontFix