Hi Bruno,
Bruno Haible writes:
> In Unicode 16.0.0, there are composed characters whose constituents are
> Unicode characters with value >= 0x12000. A hardcoded bound in
> lib/uninorm/composition.c no longer works.
Thanks, I was going to look at the new 'DoNotEmit.txt' file added in
Unicode 16.
On 2024-09-13 18:08, Bruno Haible wrote:
Why not use fstatat() directly?
Yes, lstatat is merely a deprecated convenience function.
Eric Gallager wrote:
> I recently ran into a situation where some code tries to use
> lstatat() on a platform where it isn't available (darwin).
lstatat() is not available on _any_ platform.
> I see that
> gnulib has modules for lstat(), fstatat() and statat(), but how about
> lstatat()?
lstatat
Hi, I recently ran into a situation where some code tries to use
lstatat() on a platform where it isn't available (darwin). I see that
gnulib has modules for lstat(), fstatat() and statat(), but how about
lstatat()? Would it make sense for lstatat() to have its own module?
Eric Gallager
These two patches update Gnulib to Unicode 16.0.0.
2024-09-13 Bruno Haible
Implement a new property, added by Unicode 16.0.0.
* lib/gen-uni-tables.c (is_property_modifier_combining_mark): New
function.
(output_properties): Output also the property modifier_comb
Oops, this produces a build failure. Fixed by this patch:
2024-09-13 Bruno Haible
uninorm/composition: Fix mistake in last commit (regression yesterday).
* modules/uninorm/composition (Files): Add
lib/uninorm/composition-table-bounds.h.
diff --git a/modules/uninorm/co
