flat assembler
Message board for the users of flat assembler.
![]() Goto page 1, 2 Next |
Author |
|
snrtrui
能用中文变量吗?
|
|||
![]() |
|
bitRAKE
I only know the Mahjong tiles.
![]() |
|||
![]() |
|
shoorick
MHajduk
as for me (50%) he asked: "is it possible to use Chinese variables?" |
|||
![]() |
|
MHajduk
Probably you are right, but what about another 50%.
![]() Hmm... I always was wandering why Chinese and Japanese still use such complicated writing system. Isn't better to use alphabetic writing system based on several dimes of symbols? Personally, I don't like to be only 50% sure or 50% right. ![]() |
|||
![]() |
|
shoorick
maybe, our alphabet looks same strange for them as their for us
![]() |
|||
![]() |
|
MHajduk
They don't have alphabet. Maybe only Korean Hangul with 24 ideograms we can name such way. But I was talking about these few thousands of ideograms existing in Chinese and Japanese writing.
|
|||
![]() |
|
shoorick
i think, they decide to not cut off their history, while study language on many scriptings at once is hard. even chinese simplification gave glyphs more easy to draw, but made two different scripting languages. scripting system is one of national identification basis. similar questions are why jews restored ivrit or why englishmen still write "daughter" instead of "doter" or something else sounding similar but more simple to write?
|
|||
![]() |
|
MHajduk
Nobody says that Chinese should "cut off" their history. NO. But these days they could "translate" all ancient documents to new system of writing. If they would do it, then their heritage could enrich all of us.
Case of Jews and restitution of Israel is very special. They abandoned Yiddish, because it was language based generally on old German (with some words and grammatic constructions taken from Slavic languages), therefore it was very bad associating with Holocaust and WWII. They wanted to create modern country based only on their great (ancient) history. Restitution of Hebrew language (which was mainly used in their liturgy) was one of the elements of this plan. |
|||
![]() |
|
bitRAKE
Google say, "Chinese variables can?"
![]() fasmW不支持中文的變數名稱 由有限範圍內的字節值 許多變化,將需要 Although, I've tried to be concise there is no way for me to know what the Chinese above actually means. I wanted to somehow convey the limitation and also the source of the limitation. [edit]A sly correction of a more gross blunder, lol. Last edited by bitRAKE on 12 Jan 2008, 12:39; edited 3 times in total |
|||
![]() |
|
MHajduk
I didn't use Google translators. Maybe I should start?
![]() |
|||
![]() |
|
shoorick
Quote: fasm不支持中文的變數名稱 have you try? ![]() ![]() =========================================== here is utf-8 encoded source with two variables at once: chinese and russian
|
|||||||||||
![]() |
|
MHajduk
bitRAKE
I've just made some interesting experiment with this damned Google Translator:
![]() ![]() ![]() For your interest I can say, that for "English -> Chinese Traditional" we have the same.
|
|||||||||||||||||||
![]() |
|
bitRAKE
有方法與對UTF-8
|
||||||||||
![]() |
|
bitRAKE
MHajduk wrote: I've typed very popular Second, I think Google is doing some rather creative tuning of their translators to help them cope with the moving target that language is. Combined with censorship that phrase never had a chance. ![]() I've heard the correct word is Baka? (edit: nope that is Japanese) Last edited by bitRAKE on 12 Jan 2008, 13:16; edited 2 times in total |
|||
![]() |
|
shoorick
it is not fasm. it is fasmw
![]()
_________________ UNICODE forever! |
||||||||||||||||||||||||||||
![]() |
|
snrtrui
Thanks,I know FASM can't use Chinese variables..
But I want FASM sustain the Chanese menu ... when I used UTF8.INC File ,It not display the chanese menu for PE file... |
|||
![]() |
|
MHajduk
Use Unicode version of all procedures imported from DLLs (i.e. change all procedure names ending with 'A' to 'W' versions).
|
|||
![]() |
|
snrtrui
How to do it ?
|
|||
![]() |
|
MHajduk
For example
Code: import user,\ CallWindowProc, 'CallWindowProcA',\ CreateWindowEx, 'CreateWindowExA',\ Code: import user,\ CallWindowProc, 'CallWindowProcW',\ CreateWindowEx, 'CreateWindowExW',\ ![]() |
|||
![]() |
|
Goto page 1, 2 Next < Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2020, Tomasz Grysztar. Also on GitHub, YouTube, Twitter.
Website powered by rwasa.