This is the mail archive of the
mailing list for the Cygwin project.
Re: iconv: Xft UTF-8 rendering
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Fri, 01 May 2009 01:23:39 -0400
- Subject: Re: iconv: Xft UTF-8 rendering
- References: <49FA6EE6.firstname.lastname@example.org>
Yaakov (Cygwin/X) wrote:
> Right now, I want to figure out if the problem is with Cygwin, iconv,
> libXft, or these packages (although I doubt the latter). Any assistance
> you can provide would be appreciated.
I wouldn't be surprised if the issue is libiconv. The current version
for 1.7 was built against cygwin-1.7.0-37, which was long before
NEW: mbsnrtowcs, open_wmemstream, reallocf, wcsnlen,
wcsnrtombs, wcstod, wcstof, wcstoimax, wcstoumax
NEW: wprintf, fwprintf, swprintf, vwprintf, vfwprintf, vswprintf
New setlocale implementation honors POSIX locale strings.
NEW: wscanf, fwscanf, swscanf, vwscanf, vfwscanf, vswscanf, wcscasecmp,
bugfix: mbstowcs, wcsftime, swprintf/vswprintf
massive new codepage/charset support via LC_* and setlocale
So, I'm thinking maybe rebuilding libiconv against 1.7.0-46 might help,
since the one released back in November wouldn't have seen any of that
stuff during ./configure, and may have disabled "something".
Also, I was planning to update our dist to the newly-released
libiconv-1.13 anyway -- which might help, too. But, before I did that,
I wanted to finish the last few of my packages that need "initial"
updating to 1.7/latest. The remaining ones: cvs, rxvt-unicode, checkx,
and xerces-c, so I'm *almost* there. It's only taken six months...
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html