Errors in terminfo.src for vt52, h19 and xterm-vt52 alternate character set info

[Ben Wiley Sittler]

Hi,

After a bit of investigation, it looks like terminfo.src is wrong
about the alternate character set on the h19/z100 terminal family and
on the vt52 (the real thing, as opposed to the vt100 running in vt52
mode).

The h19/z100 family actually have this acsc correspondence:

acsc=~^x`qanbkcjdmelfgg+hai.kwsutvutvozs{

The rest is assorted half- and quarter-block characters, diagonal
line-drawing characters, left and right scanlines, etc. see e.g. the
image on 
http://home.comcast.net/~davidwallace2000/h8/project8080_archive/pgs/h19esc.html#modes
for a description.

And here's the vt52 this acsc correspondence:

acsc=0affgg+h.kolpmqorrss

The rest of the vt52 alternate character set is a bunch of fraction
parts, subscript digits, and other assorted symbols.

However a vt100 or xterm emulating a vt52 (that is, after rceiving
"\E[2l" ) still uses the vt100 alternate character set. so for
"xterm-vt52" this should be as for regular xterm:

acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~

Also, are there any plans to extend terminfo to support unicode acsc
information? That is, the rest of the h19/z100 and vt52 alternate
character sets could easily be described by correspondence to unicode
characters, and ncurses could map appropriately while displaying.

Just a thought... maybe there's a way to do this and i just don't know it?

-Ben