From f7c3580478601e3a77dc864e5a1d91c1edad5187 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rg=20Frings-F=C3=BCrst?= Date: Wed, 7 Mar 2018 05:31:03 +0100 Subject: New upstream version 0.9.9 --- doc/unitypes.texi | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'doc/unitypes.texi') diff --git a/doc/unitypes.texi b/doc/unitypes.texi index 696ba88..68ab92f 100644 --- a/doc/unitypes.texi +++ b/doc/unitypes.texi @@ -13,3 +13,15 @@ taken from @code{}, on platforms where this include file is present. @deftp Type ucs4_t This type represents a single Unicode character, outside of an UTF-32 string. @end deftp + +The types @code{ucs4_t} and @code{uint32_t} happen to be identical. They differ +in use and intent, however: +@itemize @bullet +@item +Use @code{uint32_t *} to designate an UTF-32 string. Use @code{ucs4_t} to +designate a single Unicode character, outside of an UTF-32 string. +@item +Conversions functions that take an UTF-32 string as input will usually perform +a range-check on the @code{uint32_t} values. Whereas functions that are +declared to take @code{ucs4_t} arguments will not perform such a range-check. +@end itemize -- cgit v1.2.3