Re: Updating utf8's Unicode char sets
Pietro Cerutti via Chicken-users <[email protected]>
| Newsgroups | gmane.lisp.scheme.chicken |
|---|---|
| Message-ID | <01070197cc9c91a4-2ebcd473-804d-4b55-9f6d-6f63ea6a3e80-000000@eu-central-1.amazonses.com> |
> On 2 Jul 2025, at 19:00, Wolfgang Corcoran-Mathe via Chicken-users <[email protected]> wrote: > > Hi all, Hi Wolfgang, > The utf8 egg's unicode-char-sets component is woefully out of date: > according to the header comment, the current set definitions were > generated in July 2007. Since then, Unicode has been enriched with > new characters & with wonderful things like emoji. It's time the > sets were updated. > > Therefore, I've made a new version of utf8 which generates all > character sets at build time, from the official UCD data files. I've > attached my low-dependency build script & related files to the > following ticket: > > http://bugs.call-cc.org/ticket/1851 > A minor issue which I haven't yet solved is how to compile the > generated modules. Currently, the script invoked by custom-build > simply runs csc (without custom options) on each module file. This > ignores the compiler options that would usually be added by > chicken-install, but I'm not sure how to retrieve those options & > to invoke the compiler "correctly". I'm not in love with fetching files at build time. How about having a refresh script that fetches them and generates the modules? You could then commit the generated modules and solve the compilation problem too. You would rerun the refresh script whenever you want to update the egg to new tables as new Unicode versions come out. This would make the build more reproducible and remove a potential point of failure (data fetch) from every user's builds. -- Pietro Cerutti I've pledged to give 10% of income to effective charities and invite you to join me. https://givingwhatwecan.org Sent from a small device - please excuse brevity and typos.