RTEMS | Update utf8proc (#5306)

Amar Takhar (@amar) gitlab at rtems.org
Fri Jul 18 16:04:00 UTC 2025



Amar Takhar created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5306

Assignee: Amar Takhar

## Summary

<!--Please provide as much information as possible such as error messages or attaching logs-->

When moving code to /contrib/ I saw that we are on utf8proc `1.1.5`   Last updated in 2013.  There is a project for it now bu the import starts a`1.1.6`

*  https://github.com/JuliaStrings/utf8proc

Is there any reason we can't update to the latest?  Should 1.1.6 be imported to start with a lower incremental update?  What are the considerations if any when updating this.

UTF-8 has made an incredible amount of changes in the last 11 years I don't see why updating would be a bad thing.

It also comes with its own test suite now which we could get running within RTEMS as part of our test suite as well.

## Steps to reproduce

### Pre-set options

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5306
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250718/9205adff/attachment.htm>


More information about the bugs mailing list