Re: Unicode Support



"Beth" <BethStone21@xxxxxxxxxxxxxxxxxxxxxxx> écrivait
news:6CI9e.24733$443.12538@xxxxxxxxxxxxxxxxxxxx:

> First things first, when you register your RosAsm windows classes, you
> should use the "RegisterClassW" API, not the "RegisterClassA"
> API...the reason for this is that Windows takes this as a "cue" as to
> whether to send the messages with ANSI / UNICODE parameters in ANSI or
> UNICODE form...
>
> If you register with "RegisterClassA" - as you're probably doing -
> then Windows takes this to mean that you want your application window
> to receive ANSI messages (some messages have ANSI / UNICODE
> variants...for instance, the character provided by "WM_CHAR" is an
> ANSI character when the window is "registered" as ANSI...but it will
> be a UNICODE character returned by "WM_CHAR" when the window is
> "registered" as UNICODE :)...so, yes, you won't see any UNICODE
> characters appearing with "WM_CHAR", _IF_ you used "RegisterClassA"...

In fact, i do not want to upgrade RosAsm to Unicode,
at all. I just wish that the "Unicode Programmers",
writing for "Unicode Users" could write Applications
that would make use of Unicode Strings. Not RosAsm
itself. I see no reason, at all, for a Programming
Tool to be any unicode, internaly. The Programmation
is to be done in... English (unfortunately...) as
well for a Chineese as it is for me, as i have no
other choice for anything (Documentation, Menmonics
Names, exchanging with everybody, and so on...).
Personaly, i would much prefer that the international
Language could be Esperanto, but well, it is English,
and the game is over, at this point of view, also...

Also, switching to Unicode (whatever flavour of
Unicode...) can not be simple, in a monster App
like RosAsm, where nothing had ever been desing
for this. There are tons of features scanning the
Source, and all of them should, evidently, require
some modifications, even with UTF 8, in order to
not choke on any additional Char, that would conflict,
as i am afraid they could very easily do, when some
"critical Chars", that are ruling the scans...

The simper thing i want, is that, when declaring
Unicode Strings, like:

[MyUnicodeString: U§ '???????', 0]

The Programmer could input real Unicode Chars
into the String. But, even for something as
trivial as this, i am 100% sure, that there are
scan Functionalities that should be reviewed, in
order, for example, to not choke, on a _Byte_,
inside the Unicode String, that would have the
same walue as a Quote... This is an absurd problem,
when nothing has ever been designed since day one
to assume such cases >>> Much review work, for a
very small thing...

If this is too complicated, i will do it through
a "Tag" feature, runing a dedicated Unicode Dialog
for Unicode Strings pasting Back and Forth...

The RosAsm Editor Window is not an Edit Control.
This is just a flat "Drawing Surface". I do not
know at what extend, like you say, the fact of
having this window itself made Unicode Mode could
inpact on the Messages, but there had been an
oriental User, who implemented a "&WM_IME_CHAR"
case, in the MainWindowProc. So, i suppose that,
when he implemented this, he must have seen something
on his screen. Why would he have committed, if not?

For now, we have only one Oriental user (YeoHs),
who does not seem to be much concerned with these
problems, and if i understood well, in fact, i
think that he does not use really any Chineese
Chars Set, in his daily works... not sure...

Nevertheless i just asked him the question about
the effectiveness of this actual "&WM_IME_CHAR"
thingie... Wait and see.


Betov.

< http://rosasm.org/ >



.



Relevant Pages

  • Re: Trouble subclassing listview to display unicode (chinese)
    ... String" but "ByVal As Long" and Call xyz). ... First, sub-class the window as usual, but use the SetWindowLongW ... function to allow Unicode support (and prevent Windows from converting ... DefWindowProcW hWnd, WM_SETTEXT, 0, StrPtr ...
    (microsoft.public.vb.winapi)
  • Re: Edit windows created with CreatwWindowExA become Unicode windows when manifest active
    ... CreateWindowExA on XP with a manifest active, then IsWindowUnicode reports ... that the window is a Unicode window. ... receives multibyte data. ... However keyboard input sends Unicode data to the ...
    (microsoft.public.win32.programmer.ui)
  • Re: Unicode Button in VB6
    ... control to display Unicode text, ... Any window on Windows is created from a window class. ... using a VB user control when subclassing VB standard controls. ...
    (microsoft.public.vb.winapi)
  • Re: Unicode Button in VB6
    ... I am allowed to Install the Microsoft ActiveX Control Pad with my ... control to display Unicode text, ... Any window on Windows is created from a window class. ... using a VB user control when subclassing VB standard controls. ...
    (microsoft.public.vb.winapi)
  • Re: Unicode Support
    ... There is no plan for implementing Unicode in RosAsm, ... "Unicode Users" to store Unicode Strings, ...
    (alt.lang.asm)