9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] Re: removal of /lib/unicode
Date: Sat, 25 Mar 2023 21:25:31 -0600	[thread overview]
Message-ID: <dd71bdf0-4c47-2d8f-ffb3-2ec5131b2cf3@posixcafe.org> (raw)
In-Reply-To: <1AB7C1C576671B627BD6B552AA0E826C@gaff.inri.net>

On 3/25/23 21:05, sl@stanleylieber.com wrote:
>> /lib/unicode was removed in favor of just using the upstream data file
>> it was ripped from. I have updated the references in the man pages
>> to reflect this. I apologize for that mistake.
> 
> ah. no problem, i was just curious what was going on. i'll never
> remember the new file path off the top of my head, but on the other
> hand i guess i'm not manually checking /lib/unicode all that often
> anyway.
> 
> why didn't we just have the mkfile put the information in the original
> place?

Yes a couple reasons. /lib/unicode only included those in the 16bit BMP domain.
When extending this to include all the modern code points you need more hex digits.
Unless you went with using two different zero padded first columns. I could not
find a good way of updating these for things past the BMP and not breaking someone's
script.

Likewise /lib/unicode while derived from UnicodeData.txt does not include the data fields
that are needed to do the generation. So either way I was going to need to update each line
of the file anyway. I figured to instead just say 'we use the official txt file' is bit nicer
in my opinion.

Likewise other files were desired for the generation, so moving things to a directory seemed
to make more sense.


  reply	other threads:[~2023-03-26  3:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26  2:23 [9front] " sl
2023-03-26  2:33 ` [9front] " Anthony Martin
2023-03-26  2:55   ` Jacob Moody
2023-03-26  3:05     ` sl
2023-03-26  3:25       ` Jacob Moody [this message]
2023-03-26  3:08     ` sl
2023-03-26  3:09   ` Sigrid Solveig Haflínudóttir
2023-03-26  4:37     ` Kurt H Maier
2023-03-26 13:26       ` qwx
2023-03-26 14:27         ` ori
2023-03-26 17:43           ` Jacob Moody
2023-03-26 14:52   ` cinap_lenrek
2023-03-26 19:27   ` hiro
2023-03-26 19:42     ` [9front] " Michael Misch
2023-03-26 20:46       ` hiro
2023-03-26 23:24       ` Kurt H Maier
2023-03-27 21:40       ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2023-03-27 22:15         ` hiro
2023-03-28  0:01           ` Sigrid Solveig Haflínudóttir

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=dd71bdf0-4c47-2d8f-ffb3-2ec5131b2cf3@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).