Notes on DGUX port.

What's new:

	Couple of possible mem. leaks are fixed.

	I've found out why johab fonts on X11R5 X Server ever since
	since DGUX 5.4.R2.01 (so far the most rescent version is
	DGUX 5.4.3 - yes, with those good stuff posix thread).

	DGUX XServer does not handle XDrawImageString16() correctly-
	i.e. XServer does now show any johab hangul fonts
	of ASCENT Area of the font box.

	However, I found XDrawString16() is handled correctly by
	DGUX Xserver.

	Using this XDrawString16() in addition to the
	XDrwaImageString16(), we can fill up the missing
	ASCENT Area of the fonts.

	I know I know it's an overhead; but it works :)

	Now the problem is that whoever uses DGUX XServer but uses
	remote hanterm on other platform than DGUX also should use
	this changes since it is the XServer that cannot handle
	XDrawImageString16() with johab fonts.

	In this case, you will have to add -DDGUX_XSERVER to CFLAGS 
	in the Makefile or add "#define DGUX_XSERVER" to hangul.h

DGUX 5.4.* supposed to be USL System 5.4.*; however, tty related stuff
is heavily relying on BSD implementation, so use BSD flavor of tty.

Use __using_BSD and __using_DGUX together.
Use _BSD_TTY_FLAVOR.
Use USE_SYSV_UTMP.

Here, we have some problem since we have to use SYSV UTMP and BSD TTY
since "char *ptyname" is needed to use BSD TTY, but USE_SYSV_UTMP
flag hides it on orig. xterm and hanterm main.c.

Have fun!

Daeshik Kim (dkim@sprint.com)

P.S.: if you don't have any clue on what I'm talking about,
      don't bother trying.        I rather send ELF binary
      version of hanterm than trying to teach someone UNIX.

P.S. 2:  If someone can provide hanterm that do not use johab-style
         fonts, it would be very portable.

         As a matter of fact, I've seen the same problem on one version of SGI.
	 Most version of X server on SGI can handle it.