diff options
author | Michael Kerrisk <mtk.manpages@gmail.com> | 2006-08-03 13:57:30 +0000 |
---|---|---|
committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2006-08-03 13:57:30 +0000 |
commit | 68e1685c25cab6c29e4250f592c39f47996776af (patch) | |
tree | 7d83ff852ff8dd6c7ca2fcaa610ab933590eba72 /man3/wprintf.3 | |
parent | 97c1eac86f435d7feeef158417941751e7bd7a15 (diff) |
Updated CONFORMING TO section
Diffstat (limited to 'man3/wprintf.3')
-rw-r--r-- | man3/wprintf.3 | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/man3/wprintf.3 b/man3/wprintf.3 index cc06b464..2d5434cc 100644 --- a/man3/wprintf.3 +++ b/man3/wprintf.3 @@ -118,7 +118,7 @@ The functions return the number of wide characters written, excluding the terminating null wide character in case of the functions \fBswprintf\fP() and \fBvswprintf\fP(). They return \-1 when an error occurs. .SH "CONFORMING TO" -ISO/ANSI C, UNIX98 +C99. .SH "SEE ALSO" .BR fprintf (3), .BR fputwc (3), @@ -137,7 +137,8 @@ compile time. This is because the .I wchar_t representation is platform and locale dependent. (The GNU libc represents wide characters using their Unicode (ISO-10646) code point, but other -platforms don't do this. Also, the use of ISO C99 universal character names +platforms don't do this. +Also, the use of C99 universal character names of the form \\unnnn does not solve this problem.) Therefore, in internationalized programs, the \fIformat\fP string should consist of ASCII wide characters only, or should be constructed at run time in an |