iconv: Xft UTF-8 rendering

Charles Wilson cygwin@cwilson.fastmail.fm
Fri May 1 05:24:00 GMT 2009


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

1.7.0-40
NEW: wcstok

1.7.0-41
NEW: mbsnrtowcs, open_wmemstream, reallocf, wcsnlen,
wcsnrtombs, wcstod, wcstof, wcstoimax, wcstoumax

1.7.0-42
NEW: wprintf, fwprintf, swprintf, vwprintf, vfwprintf, vswprintf
wctomb/mbtowc improvements
wctomb bugfixes.
New setlocale implementation honors POSIX locale strings.

1.7.0-43
NEW: wscanf, fwscanf, swscanf, vwscanf, vfwscanf, vswscanf, wcscasecmp,
wcsncasecmp, wcsftime.

1.7.0-44
NEW: wcsdup.
bugfix: mbstowcs, wcsftime, swprintf/vswprintf

1.7.0-45
bugfix: mbtowc
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...

--
Chuck

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



More information about the Cygwin mailing list