Weird issue, though ...

This may be system related and not Pegasus Mail related but since it manifests itself in Pegasus Mail I thought it worth tapping this wealth of knowledge for assistance.

I have a customer service rep with a California based company who sends plain text messages using a Korean character set specified in the headers:  Content-Type: text/plain;

charset="ks_c_5601-1987".  These messages display with Korean characters when viewed by any user running the shared office installation of Pegasus Mail but the same message displays in English when viewed using both my laptop and my flash drive installs of Pegasus Mail.  FWIW, tmy flash drive install runs on the same PC as my shared office install.  The only things I know to check are the system locale (all are English(United States)), and the default MIME setting within Pegasus Mail (all are ISO-8859-1).  Please post any thoughts you may have for an explanation/fix for the Korean display.

Thanks.

[quote user="Brian Fluet"]Please post any thoughts you may have for an explanation/fix for the Korean display.[/quote]

Charsets are handled by a modified version of iconv.dll which has been specifically adjusted by me for handling some Asian charsets (KSC_5601 being one of them). Maybe the versions used by different installs vary depending on whether systems keep various versions of it on the same machine. I have seen such effects while running Pegasus Mail in my Delphi runtime environment since Delphi supplies a different version of iconv.dll for its own use. See below for the details of the version to be used by Pegasus Mail.

Michael,

I thought your post had explained things because it reminded me that I am running v4.63 at the office and v4.72 at home on the flash drive but I'm not sure that it does after looking at the iconv.dll files.

v4.63 shows iconv.dll as version 1.13.1    last modified 1/16/10   956KB

v4.72 shows iconv.dll as version 1.13.1    last modified 3/14/13   956KB

Is this expected?  Is it an option to replace the iconv.dll on the v4.63 with the newer one?

[quote user="Brian Fluet"]

Michael,

I thought your post had explained things because it reminded me that I am running v4.63 at the office and v4.72 at home on the flash drive but I'm not sure that it does after looking at the iconv.dll files.

v4.63 shows iconv.dll as version 1.13.1    last modified 1/16/10   956KB

v4.72 shows iconv.dll as version 1.13.1    last modified 3/14/13   956KB

Is this expected?  Is it an option to replace the iconv.dll on the v4.63 with the newer one?

[/quote]

Couldn't you upgrade the office installation?

[quote user="Greenman"]Couldn't you upgrade the office installation?[/quote]

I would prefer not to.  I don't need the new SSL or the improved TCP/IP functionality (Mercury in use) and the other improvements aren't a compelling reason to upgrade. 

[quote user="Brian Fluet"]Is this expected?  Is it an option to replace the iconv.dll on the v4.63 with the newer one?[/quote]

Yes, you can do that, but I doubt it would help since I'm pretty sure I didn't change anything in the code, otherwise it would provide a different version number. The dates are pretty unreliable with regard to this.

Finally found time to revisit this.  Replacing the iconv.dll from v4.63 with the one from v4.72 made no difference (as was expected).  A search for iconv.dll in the entire local drive on my Win7 desktop system had no hits so it appears that there is not a system file at play here.

I have identified only one sender for which this is an issue and the message traffic from her is low so it's easy enough to edit those .cnm files and change the character set.