帮忙翻译下！

wide char support
-----------------
1) The only multibyte encoding currently supported is UTF-8. The various
ISO-8859-* encodings are (optionally) supported. The internal
representation of wchar's is assumed to be 31 bit unicode values in
native endian representation. Also, the underlying char encoding is
assumed to match ASCII in the range 0-0x7f.

宽的零碎工作支援 -----------------1) 支援的现在改为暗码的唯一多位元组是 UTF-8.各种不同的国际标准组织 -8859-* 入码被支援（可选择地）。wchar 的内在表现被假定是 31 一点点 unicode 本国的 endian 表现的价值。同时, ，改为暗码的在下面的零碎工作被假定在范围 0-0 x7f 中相配美国信息交换标准代码。
2) In the next iteration of locale support, I plan to add support for
(at least some) other multibyte encodings.
locale support
--------------

2) 在现场支持的下一个重复中，我计划增加对其他多位元组入码的支持 （至少一些）。现场支持
1) The target for support is SUSv3 locale functionality. While nl_langinfo
has been extended, similar to glibc, it only returns values for related
locale entries.
2) Currently, all SUSv3 libc locale functionality should be implemented
except for wcsftime and collating item support in regex.

stdio
-----

1）支持的目标是 SUSv3 现场功能性。nl_langinfo 已经类似 glibc，只延长它为相关的现场进入归还价值。
2) 现在，所有 SUSv3 libc 现场功能性应该被除了 wcsftime 以外实现而且在 regex 中对照项目支持。stdio
1) Conversion of large magnitude floating-point values by printf suffers a loss
of precision due to the algorithm used.
2) uClibc's printf is much stricter than glibcs, especially regarding positional
args. The entire format string is parsed first and an error is returned if
a problem is detected. In locales other than C, the format string is checked
to be a valid multibyte sequence as well. Also, currently at most 10 positional
args are allowed (although this is configurable).
3) BUFSIZ is configurable, but no attempt is made at automatic tuning of internal
buffer sizes for stdio streams. In fact, the stdio code in general sacrifices
sophistication/performace for minimal size.
4) uClibc allows glibc-like custom printf functions. However, while not
currently checked, the specifier must be <= 0x7f.
5) uClibc allows glibc-like custom streams. However, no in-buffer seeking is
done.
6) The functions fcloseall() and __fpending() can behave differently than their
glibc counterparts.
7) uClibc's setvbuf is more restrictive about when it can be called than glibc's
is. The standards specify that setvbuf must occur before any other operations
take place on the stream.
8) Right now, %m is not handled properly by printf when the format uses positional
args.
9) The FILEs created by glibc's fmemopen(), open_memstream(), and fopencookie()
are not capable of wide orientation. The corresponding uClibc routines do
not have this limitation.
10) For scanf, the C99 standard states "The fscanf function returns the value of
the macro EOF if an input failure occurs before any conversion." But glibc's
scanf does not respect conversions for which assignment was surpressed, even
though the standard states that the value is converted but not stored.

printf 的大大小浮点价值的转变由于被用的运算法则遭受一个精密的损失。
uClibc 的 printf 比 glibcs 严厉许多，尤其是关于位置的 args 。整个的格式线被剖析第一而且如果一个问题被发现，一个错误被退还。在现场中，除了 C 之外，格式线被检查也是有效的多位元组序列。同时, ，最多现在， 10 位置的 args 被允许。（虽然这结构）
BUFSIZ 结构，但是没有尝试为 stdio 水流在内在缓冲大小的自动调音被做。事实上， stdio 密码大体上牺牲为最小的大小诡辩／performace。
uClibc 允许像 glibc 一样的习惯 printf 功能。然而，当不现在检查的时候，这叙述一定是＜=0 x7f。
uClibc 允许像 glibc 一样的订制水流。然而，没有在－寻求的缓冲被做。
功能 fcloseall（) 和＿＿fpending（) 能不同地跟他们的 glibc 对方比起来举止。
uClibc 的 setvbuf 关于它何时能超过 glibc 被呼叫更限制是。标准叙述在任何其他的操作在水流身上发生之前， setvbuf 一定发生。
立刻， %当格式使用时， m 不适当地被 printf 所处理位置的
args。文件产生广泛定方位藉着 glibc 的 fmemopen（) 、 open_memstream（) 和 fopencookie（) 不有能力。对应的 uClibc 常式没有这限制。
对于 scanf ， C99 标准说 " 如果一个输入失败在任何转变之前发生， fscanf 功能归还句集 EOF 的价值 "． 但是 glibc scanf 不尊敬转变为哪一个任务是 surpressed，即使标准的州价值被转换但是不储存。

温馨提示：答案为网友推荐，仅供参考

当前网址：https://verywind.cn/ee/vjjyjvr7x.html