Could not determine text encoding

[GoogleCodeExporter]

What steps will reproduce the problem?
1. echo test > Media/EBooks/test.txt
2. Attempt to open test.txt

What is the expected output? What do you see instead?
I'd like to see "test".  Instead, I see "Could not determine text
encoding."  I get this error with every file I try.  It happens for both
HTML and text files.  I've tried forcing it to every reasonable encoding in
the preferences and I just get "Incorrect text encoding" instead.  Is there
some issue with a change in one of the frameworks on 1.1.4 that broke books?

What version of the product are you using? On what operating system?
Books.app 1.3.7
iPhone 8GB 1.1.4

Please provide any additional information below.
I saw at least one other mention of this issue in the discussion on the
issues page, but I was unable to find an issue for it in the tracker.

Original issue reported on code.google.com by wan...@gmail.com on 9 Mar 2008 at 8:00

[GoogleCodeExporter]

I've not personally attempted 1.3.7 under firmware 1.1.4.  It might help to 
delete
your preferences file? See the wiki page [Troubleshooting113].

It would probably also be beneficial to try a newer build of Books.  
Unfortunately
our Installer source is out of date at the moment, but this file gives 
instructions
on how to upgrade:

http://iphoneebooks.googlecode.com/files/Books-1.4-NewInstallerSource.txt

I'm going to close this issue for now.  If the problem persists after deleting
preferences and going to a 1.4 build, please re-open and attach a sample file 
which
causes problems.

If you need additional help, it would be great if you could jump over to the 
Books
tech support group.  It helps the developers a lot to keep support issues 
separate
from the list of things we need to fix.

Support Google group is here:
http://groups.google.com/group/iphone-ebooks-support

Thanks,
Zac

Original comment by pendorbo...@gmail.com on 9 Mar 2008 at 8:59

• Changed state: Invalid

[GoogleCodeExporter]

Thanks.  1.4-pre03-r274 works great.  Just upgrading fixed everything.  Maybe 
the
install directions linked to from the main project page should contain the
information on setting up the new installer source just so everyone knows to 
get the
new version.

Original comment by wan...@gmail.com on 9 Mar 2008 at 5:52

[GoogleCodeExporter]

*sigh* In fact, the problem was (nearly) all my fault.  The permissions on the 
files
were wrong.  While re-installing and putting the files in the new location, I 
copied
over some stuff with more open permissions.  My original files were root:root 
600. 
How embarassing.

I say nearly all my fault because the application didn't give very good feedback
about the permissions failure.  Maybe a future enhancement could correctly 
report it
instead of claiming an encoding error. :)

Original comment by wan...@gmail.com on 9 Mar 2008 at 6:19

[GoogleCodeExporter]

Indeed, error handling could be better.  I ran into this myself last night 
debugging
something for an hour only to find it was permissions denied...  I've opened 
Issue
#112 to track the error reporting needs.

Original comment by pendorbo...@gmail.com on 9 Mar 2008 at 10:14