9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] patch(1) and adding new files
Date: Mon, 12 Apr 2004 21:23:33 -0600	[thread overview]
Message-ID: <Pine.LNX.4.44.0404122114460.3542-100000@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <5a5c5460f0cf4805f733a6c238609797@plan9.ucalgary.ca>

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.



      parent reply	other threads:[~2004-04-13  3:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13  2:21 andrey mirtchovski
2004-04-13  2:25 ` boyd, rounin
2004-04-13  3:23 ` andrey mirtchovski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0404122114460.3542-100000@fbsd.cpsc.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).