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.

The <92> is not a number but a character.

Both Linux machine report:
# locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
---------------------------

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/


Thanks,

Nestor :-)

On Thu, Jun 26, 2008 at 12:45 PM, James G. Sack (jim) <[EMAIL PROTECTED]>
wrote:

> Néstor wrote:
> > I made a mistake, on my linux's FF it displays as "World,s Largest"
> > but on W2K's FF it displays as "World?s Largest"  <-- the question mark
> is
> > actually a question mark inside a black diamond box.
> >
> > I can tell you that the tar backup was done in a 32 bit machine and I
> > untarred it in a 64 bit machine.
> >
>
> It sounds like a difference in locale settings. For example one machine
> (Lx) has latin-1 (or utf_8, or ??), the other (W2k) has utf_16 (I think).
>
> What do you mean by "host backups" -- maybe the actual files will
> suggest further ideas. What application was used to create the source
> files -- html content, I'm guessing.
>
> Are you are reading untarred html from file://localhost/... locations,
> perhaps? Can you extract a portion (of the actual file, not from the
> browser) containing the funny-stuff in binary -- or maybe hexdump, which
> you can post. Also what does locale report on your Lx system.
>
> tar (or gzip/bzip) does no file content conversions. So when reading
> content encoded 'somewhere else', you just may need to convert things.
>
> You may find
>  man iconv
> helpful.
>
> Or perhaps, a google search on
>  text encoding conversion
>
> Regards,
> ..jim
>
>
> --
> [email protected]
> http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
>

--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to