Close Topic Options

Ratch,

Sorry I wanted to say:

MyText dw 'U','n','i','c','o','d','e',' ','1','2','3',0

Not convenient. I just let you to imagine a program in many languages or with many paragraphs. ^^'

LaHire,

Well, the above example is just the problem my MACRO FUNCTION is supposed to alleviate. No need to use all those quotes?

Can't help you there. No one can. Each keyboard and its support is designed for one language. You are not going to input, say Chinese text, with an English keyboard. Ratch

not sure what is this about. i'm using same keyboard to type english, russian, ukrainian and both chinese (traditional and simplified).

there are two problems: hard way to write unicode strings directly in source for assemblers and no support for unicode text by editor. there are solutions for this: usage of macros, converters from unicode text to dw and usage of additional tools to edit unicode strings/text.

everything is soluble, just needs time and work.

shoorick,

It is true that a keyboard can be either a hardware device or a windows input (for Windows OS someone can have an English keyboard and can choose let's say a Chinese and a Japanese keyboard in the language bar - as long as we have installed the keyboard we want in the Regional settings).

Thank you for the analysis of the situation. Just 3 solutions then.
As macro will only work with ANSI typed characters I would be interested with a converter unicode to word. Are you refering to a special software of just an hexa viewer?

ok. here are my ideas which i planned implement via add-ins and/or converters.

solution 1:
add-in - better way.
although IDE is ANSI application, in add-in you may create dialog via DialogParamBoxW - then controls on it will be UNICODE compatible.
then you can keep UNICODE strings in separate file and edit it with this additional window. while saving this UNICODE file the add-in will also generate include file with same strings with hex words instead chars.
you will include this inc-file into your source as it is compatible with any assembler. if you will need to make changes in strings - you call add-in again, edit and save - and again that inc-file is updated to be actual.
it's not too hard to make such add-in, but requires some time.

solution 2:
converter - more universal, but worse to integrate with IDE.
after preparation of UNICODE file with string declarations with any third-side UNICODE editor you may call this converter to produce include file, valid to use with assembler.

in both cases source UNICODE strings are stored in intouched file, easy to check and edit.