Hi, Bruno Haible <[EMAIL PROTECTED]> writes:
> Yes, it is clear what you mean. But adding a new API for a thing that > mem_cd_iconveh should be able to do, just because there is a portability > problem, is against gnulib's general approach. In gnulib we solve this > by fixing the portability problem, not by adding new API. > > I'm adding a module 'iconv_open-utf' that enhances iconv_open() so that > it supports conversion between UTF-8 and UTF-{16,32}{BE,LE}. Except on > platform where iconv is entirely absent or unusable (such as OSF/1 4.0), > this module allows you to use the mem_iconveh() function for doing conversion > from an arbitrary encoding to UTF-{16,32}{BE,LE} or vice versa. Thanks, this solves the problem elegantly! However, Glibc's manual does not appear to mention the encoding names. Thanks, Ludovic.