From: Bill Kelly Date: 2008-09-05T23:03:09+09:00 Subject: Re: win32 unicode filename support? From: "Jarek Kubos" > Daniel Berger wrote: >> On Feb 12, 9:49 pm, "Bill Kelly" wrote: >>> >>> Sorry if I've misunderstood your post - but does this mean >>> that there's currently no way to open/create a file with a >>> unicode filename with the win32 tools? >> >> At the moment, no. > > Is there any new progress in support of unicode filenames? Plans? > > Bill: Did you find another solution? I went with a crude workaround. In our case, we're embedding ruby into a C++ app, so I added hooks so that I could call the subset of our unicode-aware file I/O routines on the C++ side that I actually needed, from ruby. If I had needed anything more comprehensive than just a few routines like "read_binary_file(path)" and "write_binary_file(path, data)", I might have considered a different approach, like actually patching the win32 ruby source to convert utf8 to utf16 at the last moment before making the equivalent "wide" API calls. The last mention of win32 unicode API support I saw was in a ruby-core message [ruby-core:17759] , entitled, "Ruby 1.9.1 Feature and 1.9.0-3 release plan". See the "What will not" section, below: == Rough plan of the 1.9.1 features === What will be included in 1.9.1 * default values in block parameters * built-in coverage measurement * improved version of transcode * transcode C API (experimental; only for internal use) * unicode console support on mswin32, mswin64 and mingw32 * some platforms will no longer be supported. === What will not * miniunit (we need more discussion. it will possibly be included) * Win32 unicode API support (1.9.2?) * one-byte trap instruction (1.9.2?) * dtrace (1.9.2?) * Multi-VM (1.9.5?) It's encouraging that it's at least on the list. But it looks like it may be awhile. Regards, Bill