Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#4 [unaccent] unac_string: Invalid argument

closed-works-for-me
Loic Dachary
None
7
2000-12-25
2000-12-23
Rémi Perrot
No

I've just install the new 1.2.0 unac package and
when I try this
$ unaccent ISO_8859-1 été
I've got that
unac_string: Invalid argument

$ldd /usr/bin/unaccent
libunac.so.1 => /usr/lib/libunac.so.1 (0x40018000)
libc.so.6 => /lib/libc.so.6 (0x40022000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

and my libc is /lib/libc-2.1.3.so

I also try ISO-8859-1, iso_8859-1 and iso-8859-1 with
the same resule

Discussion

  • Rémi Perrot
    Rémi Perrot
    2000-12-23

    • priority: 5 --> 7
    • assigned_to: nobody --> loic
     
  • Loic Dachary
    Loic Dachary
    2000-12-25

    • status: open --> closed-works-for-me
     
  • Loic Dachary
    Loic Dachary
    2000-12-25

    Invalid argument == iconv cannot find the transition to UTF-16BE. You
    must install libiconv (see README file for pointers).

    I agree that this is unconvenient, though. I'll try to find a way to be
    more backward compatible for the next version. Ideas are wellcome.
    I guess using examinging Unicode BOM at compile time would allow
    to find out if UTF-16 is big or little endian, if UTF-16BE is available. If
    UTF-16BE is available, nothing to be done. If not available, figure out
    what is the endianess of UTF-16. If big endian, nothing to be done, use
    it. If little endian, activate (define ?) code to assume little endian instead of big endian as is the case currently.