-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Biebl schreef op 9/05/2014 23:18:
[cut] > While we are at it: In the Debian tracker package I currently use > --with-enca (or now --enable-enca) and libunistring for UTF-8 > support. > > Is that a reasonable choice or would you suggest to use libicu? I would suggest libicu for Debian as Debian probably ships with libicu in most configurations anyway. But that's something to check first. However, Alexander is I think most experienced in the differences between icu and unistring. > One of the reasons I picked libunistring over libicu was the size > of libicu (28M vs 1.2M). > > If I now would choose libicu, that means I could get rid of both > the libenca and libunistring dependency? That is correct. You can also keep libicu and libenca enabled for charset detection. In that case both will be used with a preference on libicu. The code is fairly easy to follow here: https://git.gnome.org/browse/tracker/tree/src/libtracker-extract/tracker-encoding.c > It seems like I can enable *both* libicu and libenca for > charset-detection, so I'm a bit confused. You can indeed, and then both will be used. Kind regards, Philip -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTbd/7AAoJEEP2NSGEz4aDw1EIAIjRJReHsBcZPvk++cTljfbc bl7LUgE+B1snCKZ/CvffUHl4Lc/yU1lDQiIISCyk0RBegn96crXu77amhIv6saRS MQaOUL34whIAGqe1KWZUOPP3PrgEYRSr2X/tvepN0KR05yzjh2MUewrTd4BZHOcp rCBEZQwpqsXJvQMZxzSFQZ2oiL5lFeR63FHoA0LBpWFadGt3OMQtyqULEEbXxZ6x trl4pGfXPhtFyM2aw5TzmSN1gTPwCfKOF6+bigWPwiesIW+pJgUhwQXC8zNOCJxC l+w22f/w58+YpMGR1d/WtKQ8K1tmkUw6sAYsfkS75YYW+eIM1WvFaLPytaEfmJQ= =7L7i -----END PGP SIGNATURE----- _______________________________________________ tracker-list mailing list tracker-list@gnome.org https://mail.gnome.org/mailman/listinfo/tracker-list
