Re: Unicode Support

Betov wrote:
> Chewy509@xxxxxxxxxxxxxxxx écrivait:
>
> > So for Randy, Rene, etc, are there any plans to allow source code
in
> > UTF-16 format for your compilers/assemblers? eg to allow
symbols/labels
> > to contain non-ASCII characters, and allow easier unicode string
> > support from within the source file itself?
>
>
> First, addressing both, at a time, "Randy, Rene" is insulting
> for me, but, well... here we go.

Ooh, please. Just because I mention 2 people on the NG that actively
develop assemblers together your offended! In no way, do I imply that
you are both of the same quality character or even ability in producing
assemblers, just the fact that you both actively develop assemblers.

> There is no plan for implementing Unicode in RosAsm,
> neither in the Assembler, nor in the Sources Editor.
>
> There is actually a Developement for the Internationalization
> of the RosAsm Strings. We have done most of the job for
> the Errors Messages, and there is a chineese version.
> At the end, all of the RosAsm Messages Strings will be
> Internationalized. This is done through external Files,
> and, of course, the output Routines are also implemented
> for Unicode.
>
> There is also a Plan (not started), to enable the
> "Unicode Users" to store Unicode Strings, in the
> Sources Data. Actually, the only implemented thing
> is that the RosAsm Data can be direct Unicode, like
> this:

Well, that was somewhat the point of my post. That any user should be
able to store any string from any language/script within a source file.

> [MyUnicodeString: U§ 'BlaBla', 0]
>
> that is same as:
>
> [MyUnicodeString: B§ 'B', 0 'l', 0 'a', 0, 'B', 0, 'l', 0, 'a', 0,
0, 0]
>
> I must apologioze that i have no idea, at all,
> about how this is usable or not usable for the real
> "Unicode Users".

Would you prefer:
"Hello world"
or
48h, 65h, 6ch, 6ch, 6fh, 020h, 77h, 6fh, 72h, 6ch, 64h
within your source file.

I would prefer the first form (as anyone would). Now take the view of
the Hindi student in India who doesn't know english. Are you going to
force the second option on him, so he can use your assembler?

(I know this is a poor example, but think about other languages, eg
hebrew, most asian, etc).

> As for writing, as you suggest, say, the labels
> Names, in Unicode, directly in a RosAsm Source,
> this will never be implemented. I do not see any
> reason for doing so.

So your source code will forever be ASCII?

Even cutting back on on where were the full unicode char set can be
used, and limiting unicode to strings and comments would be a good step
forward.

> The Assembler with the best Unicode support is
> GoAsm. Unfortunately, it is closed Sources, but
> its Author is a very nice guy. If you get in touch
> with him, by Mail, i am am quite sure he could give
> you way better answers than me.

I'll take a look at GoAsm.

Thanks for the input Rene! :D

.

Relevant Pages

  • Re: Unicode Support
    ... oriental user inputs something directly in Unicode. ... in the RosASm MainWindow Messages ... RosAsm always parses the Strings ... from Quotes to Quotes, ...
    (alt.lang.asm)
  • Re: How to check variables for uniqueness ?
    ... characters is the sequence SS. ... is simply capitalizing strings. ... The fact that case mapping in English /is/ simple is neither here not ... That is a fair criticism of the Unicode position. ...
    (comp.lang.java.programmer)
  • Re: Dangerous behavior of CString
    ... If I'm reading a data file or serial port or something, if the raw data are multibyte but the compilation is Unicode or vice-versa, then sometimes the converting constructors in CString are convenient. ... I did not actually write code like this; in fact I was pretty careful always to use the _T macro with any literal strings. ... But it does the conversion using the current 8-bit code page, which is not what I want. ...
    (microsoft.public.vc.mfc)
  • Re: Help please
    ... i would like to provide "CSimString" class code because the settings ... I agree with Tom that first step is project clean and rebuild all. ... with a Unicode string, ... Consider that VS2005 strings are Unicode by default, ...
    (microsoft.public.vc.mfc)
  • Re: passing a string to a dll
    ... bool DLLRect::PullWhisker ... The interface for the DLL exported function could be like so: ... based on _UNICODE flag, e.g. ... I think that in these days those ANSI strings are something from the ...
    (microsoft.public.vc.mfc)