Gary, There's a difference between 'file type' (like audio/mpeg or text/html - which is what should normally be used for index.html) and 'character encoding' such as iso-8859-1, UTF-8 or UTF-16. The second email you posted to the group made it clear that the /data/ in your file was text characters encoded in 16-bit (probably UTF-16) encoding; that's why there are NUL (^@) bytes between each character. Whatever wrote the file wrote it as UTF-16 when what you almost certainly meant was either UTF-8 or ISO-8859-1. Check the settings for the program that wrote the file; there is where your dragons surely be.
And thanks for the kind words about the blog; it's nice to know I'm not just shouting into the wilderness. :-) Regards, Jeff -- Jeff Dickey http://archlever.blogspot.com/ Email: [email protected] Phone/SMS: +65 8333 4403 Skype: jeff_dickey LinkedIn: jdickey Yahoo! IM: jeff_dickey MSN IM: [email protected] (for IM only, please) ICQ: 8053918 QQ: 30302349 GnuPG key: Fingerprint D367 FB97 4E59 BEC0 8EBC D8E3 3BD4 7D4C DFE0 6488 Valid from 01 July 2009 to 31 December 2009 Download from http://tr.im/qqQa On 17/7/09 01:10 , "gsw" <[email protected]> wrote: > > Jeff, > > Thanks for the response! Great blog, btw. > > Apparently on the CentOS server, the "corrupted" file's character > encoding is "audio/mpeg": > $ file -bi index.html > audio/mpeg > > One of the files that was not corrupted in CentOS had the encoding > "text/plain; charset=us-ascii": > $ file -bi index.html > text/plain; charset=us-ascii > > In OS X 10.5 under the directory that is "fused" to CentOS, the > following is the encoding for both files: > $file -bi index.html > regular file > > I don't know what encoding the Simon application is using when writing > the file, but I think it strange that it is basically using the same > process each time (afaik) to write report HTML files and some > consistently are "corrupted" and some aren't. If I knew that the Simon > application should be designating an encoding type and it isn't, I > could ask that they change that, but I'm wondering whether there is > something I need to configure with MacFUSE such that it will properly > report file encoding instead of "regular file", unless that is the > normal way it should be designated. > > I'm not sure if the filesystem matters, but the CentOS server volume > is using ext3 (according to "df -T" on the server), the local fuse > volume where files are being written to is fusefs (according to "df -T > fusefs" on the OS X 10.5 box which is using MacFUSE 2.0.3,2). > > Gary > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
