Re: UTF-8 capable fmt(1)

[Kamil Rytarowski <n54%gmx.com@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09.01.2016 02:46, Thomas Klausner wrote:
> On Sat, Jan 09, 2016 at 02:36:07AM +0100, Kamil Rytarowski wrote:
>> 1. I have an impression that it's basically moving the focus
>> from ASCII to narrowed-down UTF-8, while there are plenty of
>> other locales and character systems.
> 
> It uses standard headers like locale.h, wchar.h and wctype.h, and
> uses mbtowc(). What is the problem with these functions?
> 

Here is a short explanation by libunistring developers:

http://www.gnu.org/software/libunistring/manual/libunistring.html#The-wc
har_005ft-mess

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWkRHGAAoJEEuzCOmwLnZsKlAP+gLGQ2BDbC3+GmmbQRIia+8X
aoKb9moAwoUQVTJFAXQHicC9RHu1f5op5pXYj7IqFnZBJg83YPTKg8ZiTyEncwda
Go7eXE0eT5MBw/DRNk87AXv07KDAInic7FV4A5c1NiI9Ol/Azow1rqatnFgMtcoJ
GYO0NqcHh+ojr2o/K9W6lgz2t8HoAYCRwInZhbmoRy4caCxW22x6dDI2yipaLjR+
tEfUMO8nAM1pMoGfgkzlVd+3KHtq8tujNbUCuQZ2E7OffozG64aKENWR3GmM01G8
05LJrtxQizndPT16wnVTjkJ/96vZnY9KXTEek+Qg492H2no53uw7IldYBlKUxIMN
EvfIlH+FMyt3p98MgXt+O9axNBzOa5K22d2weewP/1JvsyAwWogOP0BSIyygq0UX
J6/GLIUVz6i0Sa4G7dPb2851zN8h+zKsx6b7/qWf4dpyTdmOyQKtoGWvFbIEN68q
MSl3PV3KmiFSaQWHkKbpupG4MoXhT3xttQxLLvsD55iBi3HHs1MVBXMBFRCnf/K/
jVCpPv4s2/GuDfywfjpdpjDK8cl+6DiPPztMANssHZMtMtZw/m00StIBQ5BSpnMw
i9xCvzVFQBOxSiGA26BSC5mNGzEN6dUN1x8nBCkZJ2+FmpvBv+PTaZ6hGGgjIVq5
gPJ4lhjsaxgrqFevpl5e
=HTT4
-----END PGP SIGNATURE-----