May I suggest a slightly different system?

posted on April 30th, 2010, 3:27 pm

I believe that out of everything the current number system has been rather a barrier. I have been trying to come up with some way as to exactly how this could be fixed. So I have been looking about, and I believe these characters may be available. Just open notepad (stock) and type these codes.

(Red Numbers)
Char.CodeTooltip #
⌠5001
⌡5012
√5073
ⁿ5084
²5095
♪5256
♫5267
☼5278
‼5319
₧6700


Would this be ok? I think it is standard coding, I don't see any of these symbols used in the text, so it might be fine.

posted on May 4th, 2010, 3:53 pm

would be fine if they were ascii chars
(we are limited to ascii and extended ascii, aka, the first 255 symbols

posted on October 11th, 2010, 5:51 pm

would be fine if they were ascii chars
(we are limited to ascii and extended ascii, aka, the first 255 symbols

One question tho... after modding for some time even when using notepad. I would like to ask. Before 3.1.0 the characters were more easily usable (you could even use regular notepad to code with). With notepad++ I find it difficult to manage coding characters used in the Dynamic strings files. Is there any plan towards a new character set?

posted on October 11th, 2010, 5:53 pm

The current set is rather easy to modify as well . Zebh provided a very good explanation for how to go about it on the guide 

posted on October 11th, 2010, 5:57 pm

.h files are opened as ANSI encoding in Notepad++ per default, make sure to switch to UTF-8

here is a table with the ASCII codes for red text:


CharASCII
0127
1129
2141
3143
4144
5157
6160
7173
8190
9215

Hehe... did some hunting.

The current set is rather easy to modify as well . Zebh provided a very good explanation for how to go about it on the guide 

I'll see if it helps.

posted on October 11th, 2010, 11:07 pm

In Notepad++ I would advise against switching to UTF-8.  You could get some currupt data doing that.  Even after switching back to ASCII.

posted on October 11th, 2010, 11:15 pm

In Notepad++ I would advise against switching to UTF-8.  You could get some currupt data doing that.  Even after switching back to ASCII.

I believe that's only applicable if you choose convert. Encode shouldn't cause any issues.

posted on October 11th, 2010, 11:57 pm

Hahaha all this stuff sounds like Chinese 

posted on October 12th, 2010, 12:17 am

Sadly ANSCII doesn't support Chinese

posted on October 12th, 2010, 12:20 am

haha! (I get it...  should I be worried )

posted on October 12th, 2010, 12:28 am

Idk if you should be but im taking programming so it would be sad if i didnt

[Megadroid]

posted on October 12th, 2010, 7:33 am

Last edited by Megadroid on October 12th, 2010, 11:59 am, edited 1 time in total.

Sadly ANSCII doesn't support Chinese

Dominus merges standard and standards authority with abandon!

Edit:

I believe that's only applicable if you choose convert. Encode shouldn't cause any issues.

The only thing I can see Armada barfing on is if the UTF-8 BOM was included at the start of the file. Generally UTF-8 is compatible with ASCII.