Feature #2255: unicode parameters cannot be passed to ruby

• Status: Closed
• Assignee: windows
• Target version: 2.2.0

[vo.x (Vit Ondruch)]

On windows, Ruby should provide wmain to allow passing unicode parameters (especially file paths are of interest).

[usa (Usaku NAKAMURA)]

Hello,

In message "[ruby-core:26232] [Feature #2255] unicode parameters cannot be passed to ruby"
on Oct.22,2009 20:42:24, [e-mail] wrote:

On windows, Ruby should provide wmain to allow passing unicode parameters (especially file paths are of interest).

It doesn't make sense.

BTW, we have tha plan that UTF-8'ed ARGV with -Eutf-8 option,
but not implemented yet.

Regards,

--
U.Nakamura [e-mail]

[vo.x (Vit Ondruch)]

It doesn't make sense.

Why? May be wmain is not the right thing, but at least Unicode parameters should be possible to accept if it is windows application (probably using GetCommandLineW API function). UTF-8 is nice but that is different story.

[usa (Usaku NAKAMURA)]

Hello,

In message "[ruby-core:26234] [Feature #2255] unicode parameters cannot be passed to ruby"
on Oct.22,2009 21:05:27, [e-mail] wrote:

Why? May be wmain is not the right thing, but at least Unicode parameters should be possible to accept if it is windows application (probably using GetCommandLineW API function). UTF-8 is nice but that is different story.

Yes, using GetCommandLineW() is correct way, and providing wmain()
is nonsence. (Who use it?)

Our current plan is that using UTF-8 instead of UTF-16LE as internal
Windows strings.
We have not fixed whether supporting to pass UTF-16LE'ed ARGV to user
script or not.
If we will do so, the priority might be low.

Regards,

--
U.Nakamura [e-mail]

[vo.x (Vit Ondruch)]

For me, internal encoding doesn't matter, since the conversion is pretty easy. But important is that the following example will work properly:

C:\>echo puts ARGV[0] > uparam.rb

C:\>ruby\bin\ruby.exe uparam.rb của_zufällige_žluťoučký_разлога
c?a_zufällige_žluoučký_???????

C:\>

[naruse (Yui NARUSE)]

Did you try latest ruby-trunk?
It should run already.

[vo.x (Vit Ondruch)]

I tried ruby 1.9.2dev (2009-10-15) [i386-mswin32_90] from win32-unicode-test branch.

[vo.x (Vit Ondruch)]

• File accept_unicode_parameters.diff added

Attached patch should fix this issue.

[vo.x (Vit Ondruch)]

Ouch, sorry, this is patch for something bit different. Please forget about it (delete it if possible).

Thank you

[naruse (Yui NARUSE)]

• File deleted (accept_unicode_parameters.diff)

[znz (Kazuhiro NISHIYAMA)]

• Target version set to 2.0.0

[usa (Usaku NAKAMURA)]

• Status changed from Open to Assigned
• Assignee set to usa (Usaku NAKAMURA)

[usa (Usaku NAKAMURA)]

• Description updated (diff)

I think that if -Eutf-8 is specified ARGV should be parsed from GetCommandLineW()
and converted to UTF-8.
But it's difficult to change ruby with keeping compatibility.
I'll try it till code freeze, but I can't promise that it will be in time for 2.0.

[vo.x (Vit Ondruch)]

Thank you!

[mame (Yusuke Endoh)]

Usa-san, what's the status?

--
Yusuke Endoh [e-mail]

[usa (Usaku NAKAMURA)]

% Done: 0% ;-(

[ko1 (Koichi Sasada)]

• Target version changed from 2.0.0 to 2.1.0

ping -> usa

[hsbt (Hiroshi SHIBATA)]

• Target version changed from 2.1.0 to 2.2.0

[usa (Usaku NAKAMURA)]

• Assignee changed from usa (Usaku NAKAMURA) to windows

[nobu (Nobuyoshi Nakada)]

• Related to Bug #10555: '?' is not match to multibyte character at commandline globbing on Windows added

[nobu (Nobuyoshi Nakada)]

• Description updated (diff)

Seems fixed already.

[nobu (Nobuyoshi Nakada)]

• Status changed from Assigned to Closed