Néstor wrote: > Jim, > > both machine are linux one in 32bit rhel3 and the new one is 64 bit rhel5. > They are a tar of our web directories.
Ahh, I misunderstood. I thought I saw w2k mentioned in an earlier message. > > This link shows a similar problem but I do not see the solution and I am not > using python: > http://www.movingtofreedom.org/2008/02/23/tomboy-bulk-import-files-with-the-dbus-interface-and-python/ It's not clear that that is the same as your problem, although it may be related. So: is this right: You have a web server working as expected, no problems in clients You tar-up the website files for backup (via a server cron job) You copy the tarballs to 2 other machines, rhel3[32bit], rhel5[64bit] You expand the tarballs on rhel3 and rhel5 You view the files by running firefox on each of rhel3 and rhel5 [I believe you did say you were using firefox] (If the above is not right, the following questions may not make sense.) Questions: --------- 1) how are you accessing the file(s) causing the trouble? are you: browsing the filesystem (file:///...) on rhel3 and rhel5 or are you: running webservers on rhel3 and rhel5? http://localhost/... 2) can you look at the page info on each browser, and report what that dialog says for encoding and meta-tag content-info (if any) 3) on each browser, can you go to view > character encoding, and post what shows (there should be a dot, maybe next to "Unicode (UTF8)", and also reort whether the display gets "fixed" if you change the encoding to "Western (..)" (any of 3 such names) Regards, ..jim: -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
