freetype
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ansi x3.64 specification


From: crusius_at_stanford . edu
Subject: ansi x3.64 specification
Date: Sun, 05 Nov 2000 01:08:42 -0800

hi there. i'm writing this mail from a terminal written for ggi which
uses freetype2 (i'm seeing everything in cmtt10!). there are a few
problems with the terminal emulation, however. my plan is to make it
ansi x3.64 compatible --- the problem is that i don't have a precise
specification... all i have is a vt100 specification, which doesn't
have some commands (such as DCH), and doesn't specify some stuff
precisely.

does any of you have the ansi specification available to me? it would
be great if i could release this thing one day... i also need very
precise specifications of what to do when things like LF or CR are
received. for example, do i clear the rest of the line or not on LF?
(may seem stupid, but it seems that some programs assume that the line
will be cleared)

as you can see from this mail --- since this mail exists ---, the
terminal has basic functionality (i'm editing from within vim), but i
will not release it unless it is fully ansi compliant because i don't
want to hear about bugs (no time for that).

(for those who wonder: i'm writing this thing because i'm tired of
waiting for generic font support on the console. i am finally able to
run 800x600 with a 10-pixel wide font now, and it looks quite good.
i bet it would look fantastic on 1280x1024, with something like
13-pixels wide!!!)

--
Cesar Augusto Rorato Crusius    __o      __o      __o      __o      __o    
Stanford University           _`\<,    _`\<,    _`\<,    _`\<,    _`\<,    
e-mail:address@hidden    (_)/(_)  (_)/(_)  (_)/(_)  (_)/(_)  (_)/(_)   
www.stanford.edu/~crusius
                                       o      _     _         _
   __o      __o      __o      __o     /\_   _ \\o  (_)\__/o  (_)
 _`\<,    _`\<,    _`\<,    _`\<,    _>(_) (_)/<_    \_| \   _|/' \/
(_)/(_)  (_)/(_)  (_)/(_)  (_)/(_)  (_)        (_)   (_)    (_)'  _\o_

He who sacrifices functionality for ease of use
Loses both and deserves neither



reply via email to

[Prev in Thread] Current Thread [Next in Thread]