9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] vnc: fix farsi key symbols
Date: Tue, 16 May 2023 22:31:45 -0600	[thread overview]
Message-ID: <238c17d3-d6b1-b12e-1c1a-39b1b658202b@posixcafe.org> (raw)
In-Reply-To: <D4D2AAAA157CCC92071B33300647B62D@smtp.pobox.com>

On 5/16/23 20:38, unobe@cpan.org wrote:
> Quoth Jacob Moody <moody@mail.posixcafe.org>:
>> 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.

Thank you for the first mail, the links had some good context to read through.
There is likely some explanation for why these specific codepoints use the new format.
If there is some consistent rule, maybe it could be refactored.

> 
> 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.

I also saw other codepoints that were defaulted to the new mapping when
perusing the file. Perhaps a full sync is in order? Is there value in
keeping these old tables around for old software? I am not too sure.

> 
> 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.
> 

It should be possible to create virtual 'headless' vnc servers of arbitrary resolutions.
Maybe that will work in your case. I tend to go the other way with drawterm most of the time.

thanks,
moody

  reply	other threads:[~2023-05-17  4:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17  0:43 unobe
2023-05-17  2:08 ` Jacob Moody
2023-05-17  2:38   ` unobe
2023-05-17  4:31     ` Jacob Moody [this message]
2023-05-17 19:37       ` unobe
2023-05-17 14:35     ` ori
2023-05-17 19:38       ` unobe
2023-05-17 20:15         ` ori
2023-05-17 20:40           ` unobe
2023-05-18 10:27             ` ori
2023-05-19  3:32               ` unobe
2023-05-24 13:34 ` mkf9

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=238c17d3-d6b1-b12e-1c1a-39b1b658202b@posixcafe.org \
    --to=moody@mail.posixcafe.org \
    --cc=9front@9front.org \
    /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).