<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">
<p class="p1"><span class="s1" style="background-color: rgba(255, 255, 255, 0);">A 32 bit character type is supported by FreeBSD.</span></p>
<p class="p1"><span class="s1" style="background-color: rgba(255, 255, 255, 0);">Unicode 2012 says utf32 must be a 32 bit signed integer. Unicode only defines the Codepoint character attribute.</span></p>
<p class="p1"><span class="s1" style="background-color: rgba(255, 255, 255, 0);">RTEMS now uses libBSD and newlib. Need kernel to support the Codepoint range of values. Applications can then use additional user-defined character attributes.</span></p>
<p class="p1"><span class="s1" style="background-color: rgba(255, 255, 255, 0);">— John</span></p></div><div dir="ltr">P.S.: UTF32 exists for Unicode in 2012 after consolidation from ISO 10646-2012. The two standards merged.</div><div dir="ltr"><br>On Mar 19, 2024, at 6:20 AM, Frank Kühndel <<a href="mailto:frank.kuehndel@embedded-brains.de">frank.kuehndel@embedded-brains.de</a>> wrote:<br><br></div><div dir="ltr"><span>Hello John,</span><br><span></span><br><span>just a side node:</span><br><span></span><br><span>Strictly speaking UTF32 does not exist [1]. The correct name is UCS-4 (i.e store each character in four bytes). "Current plans are that there will never be characters assigned outside the 21-bit code space from 0x000000 to 0x10FFFF" [2].</span><br><span></span><br><span>References:</span><br><span></span><br><span>[1] Section "Unicode encodings" in <a href="https://tldp.org/HOWTO/Unicode-HOWTO-1.html#ss1.2">https://tldp.org/HOWTO/Unicode-HOWTO-1.html#ss1.2</a></span><br><span></span><br><span>[2] Section "What are UCS and ISO 10646?" in <a href="https://www.cl.cam.ac.uk/~mgk25/unicode.html">https://www.cl.cam.ac.uk/~mgk25/unicode.html</a></span><br><span></span><br><span>Greetings,</span><br><span>fk</span><br><span></span><br><span>On 3/18/24 19:02, Gedare Bloom wrote:</span><br><blockquote type="cite"><span>I think it would be wchar_t support in newlib.</span><br></blockquote><blockquote type="cite"><span>On Mon, Mar 18, 2024 at 11:56 AM Joel Sherrill<<a href="mailto:joel@rtems.org">joel@rtems.org</a>> wrote:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>What does support for UTF-32 entail? Do you have an idea what software functions you are looking for?</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I see the International Components for Unicode (ICU) has a converter (<a href="https://icu.unicode.org/download">https://icu.unicode.org/download</a>) which looks it might be part of a solution.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Multibyte character methods defined by POSIX would be in newlib.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I'm not well versed in this area so have questions but I think it basically comes down to what software libraries an application needs and porting those to RTEMS -- assuming the license is ok.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>--joel</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>On Mon, Mar 18, 2024 at 12:15 PM John Howard<<a href="mailto:echosoft.llc@gmail.com">echosoft.llc@gmail.com</a>> wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>I want to add utf32 support.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Where do I start?</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>— John</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>_______________________________________________</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>devel mailing list</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span><a href="mailto:devel@rtems.org">devel@rtems.org</a></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span><a href="http://lists.rtems.org/mailman/listinfo/devel">http://lists.rtems.org/mailman/listinfo/devel</a></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>_______________________________________________</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>devel mailing list</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="mailto:devel@rtems.org">devel@rtems.org</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="http://lists.rtems.org/mailman/listinfo/devel">http://lists.rtems.org/mailman/listinfo/devel</a></span><br></blockquote></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>devel mailing list</span><br></blockquote><blockquote type="cite"><span><a href="mailto:devel@rtems.org">devel@rtems.org</a></span><br></blockquote><blockquote type="cite"><span><a href="http://lists.rtems.org/mailman/listinfo/devel">http://lists.rtems.org/mailman/listinfo/devel</a></span><br></blockquote><span></span><br><span>-- </span><br><span>embedded brains GmbH & Co. KG</span><br><span>Herr Frank KÜHNDEL</span><br><span>Dornierstr. 4</span><br><span>82178 Puchheim</span><br><span>Germany</span><br><span>email: <a href="mailto:frank.kuehndel@embedded-brains.de">frank.kuehndel@embedded-brains.de</a></span><br><span>phone: +49-89-18 94 741 - 23</span><br><span>mobile: +49-176-15 22 06 - 11</span><br><span></span><br><span>Registergericht: Amtsgericht München</span><br><span>Registernummer: HRA 117265</span><br><span>Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler</span><br><span>Unsere Datenschutzerklärung finden Sie hier:</span><br><span><a href="https://embedded-brains.de/datenschutzerklaerung/">https://embedded-brains.de/datenschutzerklaerung/</a></span><br></div></body></html>