From: "Ludovic Courtès" <ludo@gnu.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: 54111-done@debbugs.gnu.org
Subject: bug#54111: guile bundles (a compiled version of) UnicodeData.txt and binaries
Date: Thu, 24 Mar 2022 14:33:38 +0100 [thread overview]
Message-ID: <87fsn7bhl9.fsf@gnu.org> (raw)
In-Reply-To: <87fsndztwe.fsf@ngyro.com> (Timothy Sample's message of "Sat, 19 Mar 2022 12:20:17 -0600")
Hello,
Timothy Sample <samplet@ngyro.com> skribis:
> I’ve attached two patches, the second of which is gzipped (the
> UnicodeData.txt file is nearly 2M).
>
> The first patch replaces the Perl script with the Awk script. The Awk
> script produces an identical ‘srfi-14.i.c’, except for changing “.pl” to
> “.awk” in a comment.
>
> The second patch removes ‘srfi-14.i.c’, adds ‘UnicodeData.txt’, and
> teaches the build machinery how to generate the former from the latter.
> I did my best with the Makefile, but I’m still a noob when it comes to
> Automake conventions. This is the part that warrants the most review!
> Finally, I added support for comments to the Awk script so that I could
> put the Unicode license text in the data file itself. This is probably
> the simplest way to dispatch our legal obligations to Unicode, Inc. (and
> follow the guidelines of the FSF). For all the details, see
> <https://www.unicode.org/copyright.html> and
> <https://www.gnu.org/licenses/license-list.html#Unicode>.
This all looks good to me.
Pushed in Guile as commit 9f8e05e513399985021643c34217f45d65c66392,
thank you!
Ludo’.
prev parent reply other threads:[~2022-03-24 13:34 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
2022-03-19 18:20 ` Timothy Sample
2022-03-24 13:33 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsn7bhl9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=54111-done@debbugs.gnu.org \
--cc=samplet@ngyro.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).