On Nov 07, 2010 at 09:43 AM -0500, Tim Gray wrote:
Ok, so clearly no one else has this problem. Let me ask this question then. How does mutt prepare the message when you hit reply? Assuming a message is in iso-8859-1 encoding. Does mutt decode that and make a new text file with UTF-8 encoding that it then passes off to your editor? Or does it make a new text file in the messages original encoding?
Answer - it uses libiconv. I finally realized this newest version of mutt had been built without libiconv support. I had previously built a new version of libiconv and installed it in /usr/local. Even using the `--with-libiconv-prefix=/usr` option to build with the system iconv, somehow the copy in /usr/local was being picked up and mutt didn't like that. Removing it from my system so only the system version in /usr/ was picked up fixed everything.
I'm guessing this has to something to do with x86_64 and i386 versions of the library. The Apple provided one has both architectures while the one I was building was only x86_64.
