fb7d8a7c37ec34405bcf5bb4bb8adc1130389ec3
However now I understand that CBM GEOS does _not_ use PETSCII so the CBM character specification table doesn't make sense at all. After all this is very plausible because GEOS wants to enable the user to share his files across GEOS variants - so we can share the character specification table too. git-svn-id: svn://svn.cc65.org/cc65/trunk@5527 b7a2c559-68d2-44c3-8de9-860c34a00d81
Description
No description provided
Languages
C
62.7%
Assembly
35.3%
Makefile
0.7%
PHP
0.6%
Perl
0.3%
Other
0.3%