Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Dec 2016 20:16:31 +0000
From:      bugzilla-noreply@freebsd.org
To:        office@FreeBSD.org
Subject:   [Bug 215393] devel/boost-libs: bad encoding conversion
Message-ID:  <bug-215393-25061@https.bugs.freebsd.org/bugzilla/>

index | next in thread | raw e-mail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215393

            Bug ID: 215393
           Summary: devel/boost-libs: bad encoding conversion
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: office@FreeBSD.org
          Reporter: mp39590@gmail.com
             Flags: maintainer-feedback?(office@FreeBSD.org)
          Assignee: office@FreeBSD.org

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?

-- 
You are receiving this mail because:
You are the assignee for the bug.

help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215393-25061>