|
|
| formicant |
| Posted: Jul 8 2010, 06:22 AM |
 |
|
Newbie
Group: Members
Posts: 2
Member No.: 27957
Joined: 8-July 10
|
What do you think about supporting script files in unicode (UTF-8 or UTF-16) rather than ANSI with ‘\x’ escape sequences for non-ANSI characters?
As a non-english speaker I think it’s not very convenient to deal with such ‘\x’-ed file names in VDub scripts. |
|
| formicant |
| Posted: Jul 8 2010, 07:12 AM |
|
|
Newbie
Group: Members
Posts: 2
Member No.: 27957
Joined: 8-July 10
|
Sorry! I was wrong. VirtualDub does support UTF-8 scripts. It is BOM that VirtualDub doesn’n support, not Unicode itself.
Sorry once more! |
|
| phaeron |
| Posted: Jul 9 2010, 05:16 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
You need to be careful about this. Not all of the strings that VirtualDub takes are UTF-8; older script functions and functions that don't deal with filenames actually take MBCS. The reason for this is that the script interpreter works in byte strings, and it's actually the script functions that do the conversion. That's the reason that I can't allow the script interpreter to take a UTF-8 input stream.
|
|
