Dear libiconvĀ Team, I've been trying to use libiconv on macOS to convert UTF-8 strings to their NFD form using libiconv'sĀ "utf-8-mac" encoding which is available on macOS. This does not always work
Hi, That's quite possible. The Apple-modified libiconv supports a "UTF-8-Mac" encoding, as a workaround to a deficiency of their HFS+ file system. The original GNU libiconv does not support this enco
Hi Bruno, 2017-10-26 18:13 GMT+02:00 Bruno Haible <address@hidden>: The libiconv on macOS is modified by Apple; they added the "utf-8-mac" encoding. [1] The original GNU libiconv does not contain thi
Hi Marcin, The libiconv on macOS is modified by Apple; they added the "utf-8-mac" encoding. [1] The original GNU libiconv does not contain this encoding. Therefore, could you please direct your (very
I'm building libiconv 1.16 from sources on OS X 10.5, 10.9 and 10.12. It looks like lack of UTF-8-Mac support in libiconv is causing other programs to fail. Also see https://marc.info/?l=git&m=158857
Hello, (cc'ing coreutils@) FWIW, In GNU coreutils we are working on a unicode normalization program (unorm) which can perform nfd/nfc/nfkd/nfkc conversions and other multibyte character processing. I
Hi, Seems I found the solution myself. The iconv utility that comes builtin with Mac OS X has support for UTF-8-MAC, which is the one I must use instead of the standard UTF-8. I do not know the diffe
Hi, This is because iconv is not the right tool for doing Unicode NFC <--> NFD conversions. The right tool for such conversions is explained in http://unix.stackexchange.com/questions/90100/convert-b