Graal Forums - Unicode characters...

Graal Forums (https://forums.graalonline.com/forums/index.php)

- Future Improvements (https://forums.graalonline.com/forums/forumdisplay.php?f=10)

- - Unicode characters... (https://forums.graalonline.com/forums/showthread.php?t=41280)

Unicode characters...

I'm not sure if its possible now, but if it isn't, is there a chance that Graal could read Unicode? There is a font or two that has characters like arrows and things that I'd like to use in my signs, but Graal only reads ASCII code. Perhaps a message code #U that can read the numbers entered and display character at that Unicode address so long as a font like MS Mincho, MS PGothic, or MS PMincho is being used. If there is another way to do this without having to implement something new, I'd be very thankful to know :)

too bad #U is already being used :P

Unicode support would be good, I must study it more to see if we can add support for it easily

Quote:

Originally posted by Python523
too bad #U is already being used :P

#u could work too, but I didn't see #U in the message code list. What does #U do?

Quote:

Originally posted by Stefan
Unicode support would be good, I must study it more to see if we can add support for it easily

Cool :) Easier then to display arrows than creating images. Anyone that has Win9x or greater should have those fonts I mentioned.

Hey, Stefan is reading this forum! :)
I guess this is the first time I've seen him here.

Quote:

Originally posted by G_yoshi

#u could work too, but I didn't see #U in the message code list. What does #U do?

It is used serverside for translating strings.

Graal isn't using ASCII, but ANSI code (like windows normally does).

But you could still use #K(...). The numbers 0..255 have the same meaning in unicode as in ANSI, it would just have to be extended to work from 256...65535.

In the Allegro (open source) library I have for my compiler (DJGPP) there are some functions for Unicode support. I never looked at them before. Maybe they could help Stefan.

Incorrect. #K() is for converting ASCII Code into ASCII Characters.
The keyboard is ASCII based.

Quote:

- new script function ascii(c) to get the
ascii code of a character (ascii(A) is 65);
the other way (converting ascii code to
character) can still be done by using the
#K(num) message code (#K(65) is A)

This is taken from newfeatuers2001.txt

Quote:

Originally posted by G_yoshi
Incorrect. #K() is for converting ASCII Code into ASCII Characters.
The keyboard is ASCII based.

This is taken from newfeatuers2001.txt

No. What I wrote is correct.

Now to go on with the hairsplitting:
ASCII is a defined set of characters in which there are 128 images. Each image can be accessed by a number called the ASCII-Code.
We have 256 numbers in a byte and so the default-ASCII was extended. On DOS you have different code tables with slightly different characters. But the non-latin text characters are unchanged. (Like ä,ö,ü).
Windows is of course using the default ASCII code (128 chars), but not the extended ASCII code used by DOS. Instead they use the ANSI code for the extended code. (128..255). It is not compatible with the old code from DOS (if you are using chars like ä, ö, ü,...). Because of this I am calling the windows code "ANSI" code, but of course the lower 128 chars are ASCII chars.
Unicode is just the next extension which uses the ANSI code for the lower 256 chars, but adds thousands of new chars above.

Edit: I re-read your post and of course: #K is currently not working for Unicode, but I meant it could be extended to do so. We don't need a new message code.

Hmm, sorry. I guess I had been misinformed :(