diff options
| author | Ulrich Drepper <drepper@redhat.com> | 2000-09-27 06:35:29 +0000 |
|---|---|---|
| committer | Ulrich Drepper <drepper@redhat.com> | 2000-09-27 06:35:29 +0000 |
| commit | d01fe03296ce087fb20905785aeb9caaa36592d9 (patch) | |
| tree | 050407ac0b9438dbf7220ead167b031faa8cea1a /manual/charset.texi | |
| parent | 75dbc100bf903f908c4e5e90783307cf445b19db (diff) | |
Update.
* sysdeps/unix/i386/i586/clock_nanosleep.c (CLOCK_P): Remove
CLOCK_MONOTONIC.
* sysdeps/unix/i386/i586/clock_gettime.c (EXTRA_CLOCK_CASES): Likewise.
* sysdeps/unix/i386/i586/clock_getres.c (EXTRA_CLOCK_CASES): Likewise.
Diffstat (limited to 'manual/charset.texi')
| -rw-r--r-- | manual/charset.texi | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/manual/charset.texi b/manual/charset.texi index aa4c2670c3..deae7af08a 100644 --- a/manual/charset.texi +++ b/manual/charset.texi @@ -298,15 +298,15 @@ adequately are a thing of the past. One final comment about the choice of the wide character representation is necessary at this point. We have said above that the natural choice -is using Unicode or @w{ISO 10646}. This is not specified in any -standard, though. The @w{ISO C} standard does not specify anything -specific about the @code{wchar_t} type. There might be systems where -the developers decided differently. Therefore one should as much as -possible avoid making assumption about the wide character representation -although GNU systems will always work as described above. If the -programmer uses only the functions provided by the C library to handle -wide character strings there should not be any compatibility problems -with other systems. +is using Unicode or @w{ISO 10646}. This is not required, but at least +encouraged, by the @w{ISO C} standard. The standard defines at least a +macro @code{__STDC_ISO_10646__} that is only defined on systems where +the @code{wchar_t} type encodes @w{ISO 10646} characters. If this +symbol is not defined one should as much as possible avoid making +assumption about the wide character representation. If the programmer +uses only the functions provided by the C library to handle wide +character strings there should not be any compatibility problems with +other systems. @node Charset Function Overview @section Overview about Character Handling Functions |