[9fans] patch(1) and adding new files

[9fans] patch(1) and adding new files

[andrey mirtchovski]

i'm in a pickle with this one: 

how do we add new files via the patch(1) system?  the man pages only
discuss changing already existing ones...

thanks,
andrey

Re: [9fans] patch(1) and adding new files

[boyd, rounin]

/dev/null?

Re: [9fans] patch(1) and adding new files

[andrey mirtchovski]

nevermind that, i browsed through /bin/patch/create -- it accepted the new
files fine, with just a warning...

i've added support for reading/writing keysyms to vnc[vs], which is what the
RBF defines as the encodings the VNC protocol uses for special characters.

the net effect is that you can type runes > 0xff in vncv and they'll show up
in X correctly (assuming you're using a font there that has them), and vncs
will accept such characters. 

as a bonus, ctrl+pgup/pgdn work now in xterm...

andrey

ps: here's the description from the patch:

This adds support in vncv and vncs for sending/receiving utf-8 text.

The problem comes from the RFB protocol which requires special keys to
pass through as their keysym encodings (<X11/keysimdef.h>). vncv and vncs
do not convert between utf-8 and keysym, therefore they're unusable when
one wants to write in foreign characters that don't match keysyms.

the two header files (ksym2utf.h and utf2ksym.h) declare arrays with
the same names mapping keysym definitions to unicode runes. kbdv.c and
kbds.c get the corresponding character when the rune read from /dev/cons
or from a client.

inadvertantly this fixes a problem with vncv which would cause xterminals
not to scroll on ctrl+[PgUp|PgDn].

also changed is the mkfile to add dependency between kbdv.c → utf2ksym.h
and kbds.c → ksym2utf.h

each array adds a total of ~32K to the run-time memory image of vncv
and vncs.