From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4
Received: (qmail 15864 invoked from network); 17 May 2023 00:56:04 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 17 May 2023 00:56:04 -0000
Received: from pb-smtp1.pobox.com ([64.147.108.70]) by 9front; Tue May 16 20:52:28 -0400 2023
Received: from pb-smtp1.pobox.com (unknown [127.0.0.1])
	by pb-smtp1.pobox.com (Postfix) with ESMTP id 0417D19F245
	for <9front@9front.org>; Tue, 16 May 2023 20:43:37 -0400 (EDT)
	(envelope-from unobe@cpan.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=message-id
	:to:subject:date:from:mime-version:content-type
	:content-transfer-encoding; s=sasl; bh=jPJZiGsOLEzdANgsvyO9viAaa
	XUksUzFpa9v7c3aU9k=; b=H3mEfhjAgPerXiSnsLwMc17b135RmSKgb4ixkeJZF
	cCjlOfXCv6PavUkk8et3nqH78d96+rqVGIUI1WTnYVCKBaxzYG7yvErG0LzyrWLG
	hFnOPF3Vo9AG46HbhH90hxw96iufkWl/GGmoKwhzBXAlrXYgg4h7DcrCVvoRy8u4
	f4=
Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1])
	by pb-smtp1.pobox.com (Postfix) with ESMTP id F0E4519F244
	for <9front@9front.org>; Tue, 16 May 2023 20:43:36 -0400 (EDT)
	(envelope-from unobe@cpan.org)
Received: from strider.localdomain (unknown [75.204.169.210])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pb-smtp1.pobox.com (Postfix) with ESMTPSA id EA33819F243
	for <9front@9front.org>; Tue, 16 May 2023 20:43:35 -0400 (EDT)
	(envelope-from unobe@cpan.org)
Message-ID: <C3A0EBC8A1043CC66E7E63F426B89FD3@smtp.pobox.com>
To: 9front@9front.org
Date: Tue, 16 May 2023 17:43:33 -0700
From: unobe@cpan.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID:
 DB8570FE-F44B-11ED-8C7B-C65BE52EC81B-09620299!pb-smtp1.pobox.com
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: event-aware ORM framework framework realtime-java generator 
Subject: [9front] vnc: fix farsi key symbols
Reply-To: 9front@9front.org
Precedence: bulk

Could someone explain the commit today for fixing farsi key symbols a
bit more?  Is this for vncs or vncv?  I assume vncv is more useful
nowadays due to drawterm, but perhaps not.

 From https://cgit.freedesktop.org/xorg/proto/x11proto/tree/keysymdef.h
, lines 60-81 describe the state of affairs (presumably from the last
copyright year at the top of the file, 1998).  If we want to remain
compatible with connecting to older server implementations, then would
it be better to do similar to what is done around line 91 from
https://github.com/AdoptOpenJDK/openjdk-jdk11/blob/master/src/java.desktop/unix/classes/sun/awt/X11/XKeysym.java
? That is, revert the changes to /sys/src/cmd/vnc/utf2ksym.h and
handle the discrepancy more generally in /sys/src/cmd/vnc/kbdv.c ? Or
do we just not care?