From: Timothy Sample <samplet@ngyro.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 54111@debbugs.gnu.org
Subject: bug#54111: guile bundles (a compiled version of) UnicodeData.txt and binaries
Date: Wed, 16 Mar 2022 17:42:13 -0600 [thread overview]
Message-ID: <87sfrhzcq2.fsf@ngyro.com> (raw)
In-Reply-To: <87ee32fa1v.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 16 Mar 2022 11:47:56 +0100")
Hi Ludo,
Ludovic Courtès <ludo@gnu.org> writes:
> Timothy Sample <samplet@ngyro.com> skribis:
>
>> Of course, to use this script as part of the Guile build, someone™ will
>> have to double check that we can legally redistribute the Unicode data
>> file (probably okay, but always good to check), and update the build
>> rules to generate the C file. I can’t guarantee that I’ll get to it....
>
> I’ll check with Andy if he’s fine with this option. Would you like to
> turn it into a patch against Guile? If not, I could do that.
I’ll do it. It always feels good to submit a patch!
>> # unidata_to_charset.awk --- Compute SRFI-14 charsets from UnicodeData.txt
>> #
>> # Copyright (C) 2009, 2010, 2022 Free Software Foundation, Inc.
>
> Is this correct? (Maybe yes because it’s a translation of the original
> Perl script, right?)
That’s my understanding. This is technically a modification of the
original work, so the old copyright years are still relevant.
-- Tim
next prev parent reply other threads:[~2022-03-16 23:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 16:42 bug#54111: guile bundles (a compiled version of) UnicodeData.txt and binaries Maxime Devos
2022-02-27 13:52 ` Ludovic Courtès
2022-02-27 19:45 ` Maxime Devos
2022-02-27 19:52 ` Maxime Devos
2022-02-27 23:07 ` Bengt Richter
2022-02-28 11:45 ` Ludovic Courtès
2022-02-28 17:46 ` Maxime Devos
2022-03-14 18:27 ` Timothy Sample
2022-03-16 10:47 ` Ludovic Courtès
2022-03-16 23:42 ` Timothy Sample [this message]
2022-03-19 18:20 ` Timothy Sample
2022-03-24 13:33 ` Ludovic Courtès
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=87sfrhzcq2.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=54111@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.