On 5/5/2004 10:05:21 AM, Christian Ziemski wrote:
>On 5/5/2004 5:35:29 AM, you wrote:
>>However, Vedit's Unicode conversion macro currently only work with ANSI
>>character set. (BTW, it is called ASCII to Unicode conversion, even if it works
>>with 8-bit ANSI characters, too).
>>It might be good idea to expand the conversion to work with full Windows
>>character set. And maybe with DOS (OEM) character set, and even with Mac
>>character set, too.
>Hmmm, I don't know much about character
>sets and especially UNICODE.
>The UNICODE translation in VEDIT is a
>really simple one:
>It only changes single bytes into
>double-bytes and vice versa.
>No real character set translation!
>IMHO that wouldn't be possible and
>wouldn't make sense via VEDIT macro.
>Somewhere here in WebBoard there has
>been a discussion about that some time
I did some playing with unicode a little while ago.
There are conversion programs, but as stated above all work on ANSI (or whatever ISO the purists call it now). Any enhancement would need to consider Code Page & Locale.
This has lots of stuff, but like most standards documentation is really only comprehensibe to the people who work on it all the time.
The Windows API has some unicode translation functions, I may look at these.
Unfortunately more and more programs output in unicode. For those of us using the US English characters this is not a major problem, and the simple conversions in Vedit work.
At some time in the future Ted might have to include unicode support, but I don't envy him the task, particularly if Vedit is to remain in Assembler, and not include the Microsoft bloatware needed to handle it.