FTP ing Arabic data and PAGE CODE

[Kiran_27]

Hi All,

When I am transferring Arabic data from a machine to HP UX machines (B.11.11 U 9000/800 ) , certain fields are getting swapped. I am not sure why it is happening. On contacting the source ( from where the FTP started ) they told me it is the problem of HP PAGE CODE. Could any one tell me the following

1) What is HP PAGE CODE ?
2) What is the effect of PAGE CODE in FTP transfer?
3) Will there be any way that the fields get swapped because of PAGE CODE error ??


Regards
Kiran

[Michael Schulte zur Sur]

Hi,

are they using binary mode for transfer?

greetings,

Michael

[Mark Greene_1]

see the man page for "locale" and "lang":

man 1 local

man 5 lang

for all the details on language support as installed on your system.

mark

[Kiran_27]

I am transfering the data in Binary mode.
Certain Arabic fields are getting swapped during transfer. I just want to know what is this page code , what this has to do with FTP Transfer and what is the Page code for HP UX.
Regards
Kiran

[Steven E. Protter]

Perhaps you could be so kind as to provide an example.

Certain fields are being swapped?

The Arabic itself, I can't read, but ftp doesn't change data.

If the data is ascii and you are transferring it binary, or vice versa, characters can be added to the last line of data.

Since I can't read the Arabic, I'd recommend you try the transfer ascii and see if that helps.

SEP

[Kiran_27]

Here the fields are separted by pipes For example the data is like this
|1234 | test | شس٠ب | HP|
Here after transfering the fields are get exchanged...... like |1234 |test| HP | شس٠ب |

I am not sure what exactly is happening ....... The people how transferred the data told me that it is because of the PAGE CODE .....So I just want to know what is this Page code all about.

[Yogeeraj_1]

hi,

can you try compressing the file before FTPing and check what what happens?

regards
Yogeeraj

[Kiran_27]

Can any one tell me what is this PAGE CODE........ Is there anything like that ???

[Cheryl Griffin]

It is not clear what they are referring to. I've checked several resources and can't find anything. Have a look at google, google newsgroups, www.docs.hp.com, etc. and you'll find the same results.

Are you receiving an error during the ftp?
If not, can you ask the source to ellaborate on page code. It's likely to be called something else.

Possibly you don't have Arabic language support on the HP machine? See http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x4f075f938a10d6118ff40090279cd0f9,00.html

[Michael Schulte zur Sur]

Kiran,

how do you see that something is switched?

greetings,

Michael

[Mark Greene_1]

PAGE CODE is a Windows term. There is single item counterpart in HP, you have to read the man pages I referenced above to see if you have full support for Arabic on your system.

mark

[Bill Hassell]

PAGE CODE is probably CODEPAGE and is a Windows-only concept with no meaning for ftp since ftp is platform neutral. Now some platforms (Windows, mainframes, etc) may have additional features like file types, but basic HP-UX has no file types and has no concept of fields. There are only two transfer methods: BINARY which is an exact copy of what was sent, and ASCII where the data is assumed to be in ASCII on the source, transferred in a format-neutral method and the destination will format the data stream as required for the local machine.

In Windows, ASCII files have CR+LF characters at the end of every line while in Unix, the end of a line is just LF. ASCII handles this conversion, while BINARY copies exactly what was sent.

The transfer you are seeing on HP-UX is WYSIWYG (exactly what the PC sent). On the PC side, you may need to display the file locally with a dumb editor like Notepad. That way you can see exactly what is in the records. I know of no standard data transfer program that understands fields at all. As far as I know, Windows CODEPAGE is only for character set conversion (see http://www.microsoft.com/globaldev/reference/WinCP.mspx)

[Bill Hassell]

The link is http://www.microsoft.com/globaldev/reference/WinCP.mspx

There is a trailing ) in the previous posting that became part of the URL link.