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.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 19782 invoked from network); 17 May 2023 02:41:06 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 17 May 2023 02:41:06 -0000 Received: from pb-smtp21.pobox.com ([173.228.157.53]) by 9front; Tue May 16 22:38:44 -0400 2023 Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id F187B1FBCF6 for <9front@9front.org>; Tue, 16 May 2023 22:38:38 -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:in-reply-to:mime-version:content-type :content-transfer-encoding; s=sasl; bh=dV9k40v/cJtlw9uqi6nG0u81k nRmAOxQGq/6R0WbjEI=; b=Q+Llzv0VeXWCnqvF9SeIhdPZpwcCZS+iDIIDilUJK STyieKfuGi19BHS9Kmx4s4xIzQyJemaIaV+w4g6C0xp+IWqePe3fYqSr6uDAUm7+ grXdi8hEBPjIxRbWQJrnN0tGOpCJEJ26FqEUqzwKvG9vQwcDZnFG0WGzoirf/wVW PQ= Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id EC8B01FBCF5 for <9front@9front.org>; Tue, 16 May 2023 22:38:38 -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-smtp21.pobox.com (Postfix) with ESMTPSA id B24DA1FBCF4 for <9front@9front.org>; Tue, 16 May 2023 22:38:35 -0400 (EDT) (envelope-from unobe@cpan.org) Message-ID: To: 9front@9front.org Date: Tue, 16 May 2023 19:38:33 -0700 From: unobe@cpan.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: EC12298E-F45B-11ED-9A1C-B31D44D1D7AA-09620299!pb-smtp21.pobox.com List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: managed deep-learning-scale solution Subject: Re: [9front] vnc: fix farsi key symbols Reply-To: 9front@9front.org Precedence: bulk Quoth Jacob Moody : > I was told these were pulled from the openbsd keysymdef.h. > I dont currently have an openbsd around but I believe this is the file, and these lines specifically: > > https://github.com/openbsd/xenocara/blob/d1a8d3ab034044bab40925e51534100a444dd3d6/proto/xorgproto/include/X11/keysymdef.h#L1011-L1100 > > It seems that they have elected to make the "new" unicode mapping the default, alongside the existing older keysyms in a similar way this > patch does. Likewise the X11/keysym.h on my local loonix system has the same mapping. I agree that on paper the use of the new mappings > for these codepoints specifically is a bit weird, but it seems to be consistently weird with "upstream". Thanks moody. In that case, more mappings like Arabic percent, the Arabic digits (not Farsi) etc. could be updated to match. But that's for another day. As a side note which made me interested in this patch: I've only recently started using more Arabic, but haven't used it via VNC, mainly because the computer I'd VNC into has a much higher resolution than my 9front display, so I only see a portion of the screen. I don't see an easy way to scale the viewing window like some other VNC viewers do. So being able to scale, or have the ability to view a different part of the remote buffer, is a blocker.