Hello John,
On 3/19/24 16:53, John Howard wrote:
P.S.: UTF32 exists for Unicode in 2012 after consolidation from ISO 10646-2012.
The two standards merged.
Oops. I am apparently outdated ...
Frank
--
embedded brains GmbH & Co. KG
Herr Frank KÜHNDEL
Dornierstr. 4
82178 Puchheim
Germany
email:
A 32 bit character type is supported by FreeBSD.
Unicode 2012 says utf32 must be a 32 bit signed integer. Unicode only defines
the Codepoint character attribute.
RTEMS now uses libBSD and newlib. Need kernel to support the Codepoint range of
values. Applications can then use additional user-def
Hello John,
just a side node:
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
0x00 to 0x10" [2].
References:
[1] Sectio
I think it would be wchar_t support in newlib.
On Mon, Mar 18, 2024 at 11:56 AM Joel Sherrill wrote:
>
> What does support for UTF-32 entail? Do you have an idea what software
> functions you are looking for?
>
> I see the International Components for Unicode (ICU) has a converter
> (https://ic
What does support for UTF-32 entail? Do you have an idea what software
functions you are looking for?
I see the International Components for Unicode (ICU) has a converter (
https://icu.unicode.org/download) which looks it might be part of a
solution.
Multibyte character methods defined by POSIX w
