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=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 18985 invoked from network); 17 May 2023 14:41:09 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 17 May 2023 14:41:09 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 9front; Wed May 17 10:35:36 -0400 2023 Received: from abbatoir (pool-108-27-53-161.nycmny.fios.verizon.net [108.27.53.161]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id b1df96c4 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Wed, 17 May 2023 07:35:33 -0700 (PDT) Message-ID: <998BE9895162385EEF024B0861364117@eigenstate.org> To: 9front@9front.org Date: Wed, 17 May 2023 10:35:32 -0400 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: basic decentralized factory replication pipelining database Subject: Re: [9front] vnc: fix farsi key symbols Reply-To: 9front@9front.org Precedence: bulk Quoth unobe@cpan.org: > 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. > Typically, I use tigervnc, which scales the resolution of the remote virtual X11 server to match the resolution of the output window.