Date: Mon, 10 Apr 2017 14:59:43 +0300 From: Lev Serebryakov <lev@FreeBSD.org> To: Andrey Chernov <ache@freebsd.org>, freebsd-i18n@freebsd.org Subject: Re: citrus/BSD iconv doesn't respect ICONV_SET_DISCARD_ILSEQ flag Message-ID: <e7d085a2-9356-b518-902a-3a9f51235a52@FreeBSD.org> In-Reply-To: <fed637f0-efb1-f592-0c0d-8c5da243dc54@freebsd.org> References: <137414834.20170409140646@serebryakov.spb.ru> <53b57139-8e68-da83-8fe8-e132ea524b6d@freebsd.org> <fd3c6dc7-59a9-1644-bd7c-423aa09671ab@FreeBSD.org> <fed637f0-efb1-f592-0c0d-8c5da243dc54@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10.04.2017 14:51, Andrey Chernov wrote: >>> I need to add that our iconv also don't support anything after // >>> forcing ports using GNU iconv: >>> /* >>> * Remove anything following a //, as these are options (like >>> * //ignore, //translate, etc) and we just don't handle them. >>> * This is for compatibility with software that uses these >>> * blindly. >>> */ >>> //ignore is analogue of ICONV_SET_DISCARD_ILSEQ on. >> But later in code: >> >> handle->cv_shared->ci_discard_ilseq = strcasestr(out, "//IGNORE"); >> >> So, "//IGNORE" is "supported" (in same way as ICONV_SET_DISCARD_ILSEQ >> is "supported") >> > I isn't, it just being set/unset without affecting anything. Grep > ci_discard_ilseq through BSD iconv sources. It is why I wrote "supported" not supported :( -- // Lev Serebryakov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e7d085a2-9356-b518-902a-3a9f51235a52>