On Fri, Dec 03, 2010 at 07:27:46PM +0100, Stefan Sperling wrote: > I spent some more time trying to understand the beast that's mbrtowc(3). >
some tweaks. jmc --- mbrtowc.3 Fri Dec 3 19:33:27 2010 +++ mbrtowc.3.new Fri Dec 3 19:45:19 2010 @@ -39,7 +39,7 @@ .Sh DESCRIPTION The .Fn mbrtowc -examines at most +function examines at most .Fa n bytes of the multibyte character byte string pointed to by .Fa s , @@ -94,7 +94,7 @@ .Fa mbs . They will be used during subsequent calls of .Fn mbrtowc -to restart the conversion suspended. +to restart the suspended conversion. .Pp In state-dependent encodings, .Fa s @@ -187,7 +187,7 @@ .Pp Because applications using .Fn mbrtowc -are shielded from specifics of the multibyte character encoding scheme, +are shielded from the specifics of the multibyte character encoding scheme, it is impossible to repair byte sequences containing encoding errors. Such byte sequences must be treated as invalid and potentially malicious input. Applications must stop processing the byte sequence pointed to by @@ -223,7 +223,7 @@ .Sh ERRORS The .Fn mbrtowc -may causes an error in the following case: +function may cause an error in the following cases: .Bl -tag -width Er .It Bq Er EILSEQ .Fa s @@ -268,10 +268,10 @@ == NULL do not make any sense. Instead of passing NULL for .Fa mbs , -.Xr mbtowc(3) +.Xr mbtowc 3 can be used. .Pp -Earlier versions of this man page were implying that calling +Earlier versions of this man page implied that calling .Fn mbrtowc with a NULL .Fa s
