On 10/09/08 22:59, Szabolcs Horvát wrote:
> 2008/9/10 Szabolcs<[EMAIL PROTECTED]>:
>> It turns out that I was wrong. Vim *can* open these files if I use
>> the :e command, or I browse to the file with Vim as you suggested, or
>> I just drag it onto the Vim window. The problem is only present when
>> I use the "Edit with Vim" entry of the right click menu. So I suppose
>> that the gvimext shell extension is the culprit.
>>
>
> It seems that gvimext does not support Unicode file names, so I
> attempted to "fix" it ... However, I am not a programmer, and I know
> absolutely nothing about Windows programming (I just Googled for
> documentation) ... I would appreciate it very much if someone could
> take a look at my primitive effort to add Unicode support, and tell me
> if I did something stupid. (It does appear to work when tested with
> the őű.txt file.)
Well, I don't know anything about programming Windows for Unicode but
you might test the following names (I'm adding quotes because some of
them have spaces)
"Э-эй ухнем.txt"
"Ĉu.ĉi-tie.ĉiuaŭtune.ŝiriĝas.folioj.htlm"
"爲無爲、則無不治。.txt"
"أَلسَّلامُ عَلَيْكَمْ.txt"
Paste them, don't hand-copy them ;-). I don't think the content of the
files matters. I expect the last two to be particularly "difficult"
because of the high CJK codepoints and the RTL Arabic words with
composing characters in them. I don't guarantee that all values are
"permitted" as filenames but they are "meaningful" text (well, more or
less; let's say they're linguistically OK) and I intentionally didn't
use question marks and asterisks (which I think are forbidden).
Best regards,
Tony.
--
"It was a Roman who said it was sweet to die for one's country. The
Greeks never said it was sweet to die for anything. They had no vital
lies."
-- Edith Hamilton, "The Greek Way"
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
