topic Re: Read text file in Operating System - HP-UX

Read text file

heaman1 — Tue, 14 Apr 2009 06:02:04 GMT

I have a text file and I tried to read it in different servers , A server ( which the server generate the file ) can vi and cat it , but others can't vi it but can cat it , can advise what is problem in my server ? thx

Re: Read text file

Vibhor Kumar Agarwal — Tue, 14 Apr 2009 06:04:48 GMT

How are you trying to read the file on other servers.

If you aren't FTP'ing the file, probably there is a file permission issue.

Re: Read text file

Steven Schweda — Tue, 14 Apr 2009 06:08:42 GMT

> [...] can't vi it [...]

What does this mean? Do you get some error
message, or what?

What, exactly, did you do?
What, exactly, happened when you did it?

> [...] A server [...]
> [...] my server [...]

What are these servers? "uname -a"?

Where is the file? "ls -l"?

Re: Read text file

heaman1 — Tue, 14 Apr 2009 06:41:31 GMT

thx replies,

This is not permission problem , when read it , it pops below , can advise what is wrong ? thx

ï£¸?^@?^@x^@m^@l^@ ^@v^@e^@r^@s^@i^@o^@n^@=^@"^@1^@.^@0^@"^@ ^@e^@n^@c^@o^@d^@i^$
^@<^@D^@o^@c^@u^@m^@e^@n^@t^@E^@l^@e^@m^@e^@n^@t^@>^@
^@ ^@ ^@<^@R^@e^@g^@D^@a^@t^@a^@>^@
^@ ^@ ^@ ^@ ^@<^@W^@a^@r^@r^@a^@n^@t^@y^@C^@a^@r^@d^@>^@0^@<^@/^@W^@a^@r^@r^@a^$
^@ ^@ ^@ ^@ ^@<^@B^@r^@a^@n^@d^@>^@K^@E^@F^@<^@/^@B^@r^@a^@n^@d^@>^@

Re: Read text file

Steven Schweda — Tue, 14 Apr 2009 06:57:16 GMT

> can advise what is wrong ?

No.

Do you ever _answer_ questions, or do you
only ask more?

Re: Read text file

Vibhor Kumar Agarwal — Tue, 14 Apr 2009 06:57:35 GMT

Post the output of below:

file

On system where working/non-working (both):
which vi
alias vi

Re: Read text file

heaman1 — Tue, 14 Apr 2009 07:24:39 GMT

file test.txt
test.txt: Little-endian UTF-16 Unicode character data

#which vi
/bin/vi
# alias vi
bash: alias: vi: not found

Re: Read text file

Dennis Handly — Tue, 14 Apr 2009 09:19:59 GMT

>file test.txt
>test.txt: Little-endian UTF-16 Unicode character data

This is NOT a HP-UX text file. Nor is it HP-UX because file(1) isn't smart enough to know anything about UTF-16.

Is one server Linux? If so, this isn't valid for HP-UX and you would have to translate it to UTF-8.

Re: Read text file

Suraj K Sankari — Tue, 14 Apr 2009 09:24:10 GMT

hi,

Did you tried like this
cat test.txt >test1.txt
then vi test1.txt

Suraj

Re: Read text file

Dennis Handly — Tue, 14 Apr 2009 09:31:45 GMT

>Suraj: Did you tried like this: cat test.txt > test1.txt

I'm not sure how this will be better, especially if "diff test.txt test1.txt" says the file are the same.

Re: Read text file

Vibhor Kumar Agarwal — Tue, 14 Apr 2009 10:23:32 GMT

Probably his working machine is UTF enabled or similar.

Re: Read text file

Suraj K Sankari — Tue, 14 Apr 2009 10:26:17 GMT

Hi Dennis,

as he saied that he can cat the file but not able to vi the file.

Suraj

Re: Read text file

Dennis Handly — Tue, 14 Apr 2009 10:54:45 GMT

>Vibhor: Probably his working machine is UTF enabled or similar.

And probably not HP-UX.

>Suraj: as he said that he can cat the file but not able to vi the file.

You are confused. He really said, that when he used vi, he got garbage. That's because vi doesn't support UTF-16, that's not a multi-byte character code sets.

If cat works, it's probably because the output is being sent back to a linux machine.

Re: Read text file

Steven Schweda — Tue, 14 Apr 2009 13:06:07 GMT

> You are confused. He really said, that when
> he used vi, he got garbage.

As _I_ recall, he said ("Apr 14, 2009
07:02:05 GMT"):

> [...] A server ( which the server generate
> the file ) can vi and cat it , but others
> can't vi it but can cat it [...]

I _asked_:

> What are these servers? "uname -a"?

with no apparent result.

Most likely, one of the "vi" programs is
smarter than the other (perhaps by being
"vim" instead of "vi"), but given the
unidirectionality of the information flow
here, we may never know.

Re: Read text file

Dennis Handly — Tue, 14 Apr 2009 23:08:51 GMT

>Steven: As _I_ recall

You have to read more replies (and minds :-), "when read it, it pops below" and "Little-endian UTF-16 Unicode".