Posted 03 December 2012 - 12:47 PM
Firstly I think that implementing unicode is not a good idea, since there is so many glyph and not created to be used in monospace
But I think that we must being able to use the full ASCII chart, and additionnaly, like old computer setting codepages.
If we don't change the actual character size, the codepage file would be 2ko
the graphical appearance of the characters would be defined in binary format like that by 64 bit :
When running a program could load a codepage or modify directly the character by setting directly codes
One implementation I have though could be :
Firstly it could be good for somes person making programs that require special characters, but with glyph() it could be possible to animate without rewriting text, and finaly to make localized programs.
But I think that we must being able to use the full ASCII chart, and additionnaly, like old computer setting codepages.
If we don't change the actual character size, the codepage file would be 2ko
the graphical appearance of the characters would be defined in binary format like that by 64 bit :
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
01111110
10000001
10100101
10000001
10111101
10011001
10000001
01111110
01111110
11111111
11011011
11111111
11000011
11100111
11111111
01111110
...
When running a program could load a codepage or modify directly the character by setting directly codes
One implementation I have though could be :
term.glyph(char,line,value) -- to change the way a glyph is draw ( don't apply directly)
term.apply() -- apply modification make by glyph()
term.codepage(string or filename) -- directly change all glyph depending to the codepage
Firstly it could be good for somes person making programs that require special characters, but with glyph() it could be possible to animate without rewriting text, and finaly to make localized programs.
Edited on 04 December 2012 - 01:55 PM