Re: RELEASE emelFM2 0.4

  • From: dsyates <dsyates@xxxxxxxxxxxxxx>
  • To: emelfm2@xxxxxxxxxxxxx
  • Date: Thu, 03 Apr 2008 20:16:45 -0400

dsyates wrote:
tpgww@xxxxxxxxxxx wrote:
On Wed, 02 Apr 2008 23:25:50 -0400
dsyates <dsyates@xxxxxxxxxxxxxx> wrote:

I get this when trying to view a document from the right click context menu,"View" menu item:

Conversion from ANSI_X3.4-1968 encoding failed: "Invalid byte sequence in conversion input"

This behavior hasn't been observed in previous releases. Am I overlooking something that should be obvious?
latest version (0.4.0) built from source.

ANSI_X3.4-1968 is the official name for the ASCII character set, and so should be UTF-8 compatible. I'll need to investigate further why it's being converted at all, before thinking about why it failed.

Are you able to discover what the actual encoding of the file is ?

Though there were some encoding changes in this release, I don't thing they would have led to a false categorisation as an ascii file.


Tom the file I was trying to view was the emelfm2 README file.

I do not know why, but I am unable to duplicate this error anymore.
All seems to be working fine now.

David S. Yates

Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: