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.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no
	version=3.4.4
Received: (qmail 18027 invoked from network); 24 May 2023 13:36:45 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 24 May 2023 13:36:45 -0000
Received: from mx1.riseup.net ([198.252.153.129]) by 9front; Wed May 24 09:35:13 -0400 2023
Received: from mx0.riseup.net (mx0-pn.riseup.net [10.0.1.42])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
	(No client certificate requested)
	by mx1.riseup.net (Postfix) with ESMTPS id 4QRBxv3hTZzDqMT
	for <9front@9front.org>; Wed, 24 May 2023 13:34:59 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
	t=1684935310; bh=1LTEE49O6Umwfk7dlnM2A7Yl7cLo3bNTwpRI5unoT/A=;
	h=Subject:To:References:From:Date:In-Reply-To:From;
	b=DJQ57OZc31m2BRJdGIEKXg0JyWJoTpqAZSVL6cv9MU8XCq0SRJ1q0ls7joQCPc4+C
	 UduLozOmFTOQ9lqVZjFD6FiJtK4BEjF85FuCrnpyY98Q5WaiGKdJR0kupAZjevAlpA
	 d92K52m3x1wGmsONF1csEKQ0zdpLdFaNR1NJUYWo=
Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "mail.riseup.net", Issuer "R3" (not verified))
	by mx0.riseup.net (Postfix) with ESMTPS id 4QRBxj6SRbz9scb
	for <9front@9front.org>; Wed, 24 May 2023 13:34:49 +0000 (UTC)
X-Riseup-User-ID: BCAB8EE612E03C8F48B8AE4D2E597920D6981400F5DBEC42FB74E10BCB827787
Received: from [127.0.0.1] (localhost [127.0.0.1])
	 by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4QRBxj0rNvzJn99
	for <9front@9front.org>; Wed, 24 May 2023 13:34:48 +0000 (UTC)
To: 9front@9front.org
References: <C3A0EBC8A1043CC66E7E63F426B89FD3@smtp.pobox.com>
From: mkf9 <mkf9@riseup.net>
Message-ID: <efae2621-ae63-55be-fabe-bd3060f955c5@riseup.net>
Date: Wed, 24 May 2023 17:04:45 +0330
MIME-Version: 1.0
In-Reply-To: <C3A0EBC8A1043CC66E7E63F426B89FD3@smtp.pobox.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: optimized hardware dependency layer 
Subject: Re: [9front] vnc: fix farsi key symbols
Reply-To: 9front@9front.org
Precedence: bulk

unobe@cpan.org wrote:
> 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.


Hi, sorry for late reply.
this patch only fixes vncv->tigervnc, vncv->vncs works already.
the reason I didn't updated other keysyms is we don't currently have an 
Arabic/Urdu/etc kbmap to type those characters.