RC support for non-ASCII characters

extend characters é, ê, ẵ did not work in the RC interface. When sending the 'Ađd' cmd with extend charaters, VLC does not accept it. The same filename works fine if it's added from File->open file->éêẵ.mp3

Duplicate of #747 (closed)

added Status::duplicate label

closed

Actually this is different from #747 (closed)

Seems rc intf is using ANSICP-dependent ReadConsoleInput() and putc()

For unicode to work, we need ReadConsoleInputW() and putwc() with proper conversions.

added Component::Interface: other plugins label and removed Status::duplicate label

reopened

No, it is the same problem as #747 (closed), expressed in a slightly different way. IMHO, it would be a big waste of time to fix this before reworking the whole RC/vlm stuff.

Well but those 2 tickets might have different resolutions.

#747 (closed) might perhaps resolve to Won't fix, since there are very good arguments for always using Unicode.

On the other hand, this ticket is much more related to #817 (closed) stuff.

It wasn't obvious at the first sight since there was no ToLocale/FromLocale involved.

changed milestone to %0.9.0 bugs

occasionally opened #891 (closed) duplicate.

Want to put 2 notes, as told there.

1. windows console and windows GUI use different encodings
2. 2 different lines in console used different mis-encodings (both wrong).

assigned to @Courmisch

I am not the one to fix such Win32 problems. Besides I still believe it's a waste of time to try to fix the bloated RC interface cruft. It has to be merged with telnet and rewritten anyway.

changed title from extend charaters é, ê, ẵ did not work in the RC interface to RC support for non-ASCII characters

added Type::feature label

changed milestone to %Features paradize

unassigned @Courmisch

Does ReadConsoleInputW() handles OEM and ANSI code pages properly? If it uses the wrong one, this is going to be a big waste of time.

My understanding is that -W functions completely ignore any codepage settings.

Text you enter should be only dependent on your active keyboard setting, but you can paste anything - even e.g. chinese characters into shell with western keyboard.

It should make no difference on Windows NT, providing that all settings are correct. However that is better to be tested. Maybe i will have time to think of tests and implement them.

About Windows 95/98/ME i think that should be tested.

ping!

Is the bug still there?