maintainer-feedback requested: [Bug 215393] devel/boost-libs: bad encoding conversion
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Dec 18 20:16:32 UTC 2016
mp39590 at gmail.com has reassigned Bugzilla Automation <bugzilla at FreeBSD.org>'s
request for maintainer-feedback to office at FreeBSD.org:
Bug 215393: devel/boost-libs: bad encoding conversion
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215393
--- Description ---
Created attachment 178070
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=178070&action=edit
test case
By default boost-libs is compiled with ICONV and ICU support. In my tests such
configuration gives bad results for encoding from utf8 to arbitrary codepage
comparing to other OS'es.
I've attached screenshots and test program which I use. Test program uses
pre-defined utf8 string and python script to convert it from utf8 into Latin-5
and TIS620.2533-0 (thai) codepages, then it uses boost to do the same. To
compile it simply type 'make' (or 'bmake' on Linux), boost lib and python2 are
requirements.
I've run this program on OpenBSD current, Debian stable and FreeBSD 11,
screenshots are attached.
If I compile boost-libs with ICU *only* I have better results - they're the
same as on other two OS'es, except for TIS620.2533-0 codepage - it rises an
exception about unknown encoding.
Does such inconsistency between FreeBSD's boost-lib's locale and other OS'es
should be expected?
More information about the freebsd-office
mailing list