[Bug 642208] Review Request: mingw-win-iconv - iconv implementation using Win32 API

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=642208

--- Comment #13 from Erik van Pienbroek <erik-fedora at vanpienbroek.nl> 2011-06-03 09:01:16 EDT ---
The big difference between GNU libiconv and win-iconv is that GNU libiconv has
implemented all the character set conversion in its own code while win-iconv
uses the Win32 API to achieve the exact same goal. Win-iconv is meant to be a
drop-in replacement for GNU libiconv as it has the same API interface and all
it's functions should behave the same as GNU libiconv. Projects like Glib/GTK
have also been using win-iconv for some time now in their Win32 releases so
this gives me the confidence that it's good to replace GNU libiconv with
win-iconv (as it's much smaller than GNU libiconv). I've also been testing
win-iconv in the mingw-w64 testing repo (where all packages have been rebuilt)
and haven't stumbled across any regressions yet.

This proposed change was also announced to the fedora-mingw mailing list
recently (see comment 4) and nobody objected to it, so we decided to continue
with the review process.

It looks like the 0.0.3 version was released less than 48 hours ago. I've
updated the package to use this new version:

Spec URL: http://ftd4linux.nl/contrib/mingw-win-iconv.spec
SRPM URL: http://ftd4linux.nl/contrib/mingw-win-iconv-0.0.3-1.fc15.src.rpm

* Fri Jun  3 2011 Erik van Pienbroek <epienbro at fedoraproject.org> - 0.0.3-1
- Update to 0.0.3

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.