T24 FILE IS GETTING CORRUPTED

[ramesh d]

---------- Forwarded message ----------
From: ramesh d <ramesh...@gmail.com>
Date: Oct 31, 2009 5:51 PM
Subject: File is getting corupted
To: jB...@googlegroups.com

Hi,

 

We are facing problem with Arabic characters when we migrate the data from R07 to R09.

we are extracting the Customer data from R07 and copying into R09.Using DM tool we are uploading.But after upload the arabic characters are not getting displayed properly.please let me know the solution

 

T24 Vesion:R09

Jbase:TAFC

in .profile Code page is UTF-8

 

Thanks in advacne,

 

Thanks

Ramesh.

[Jim Idle]

It means that somewhere along the way, the character set that your Arabic characters were originally encoded in is not converting to UTF-8 correctly. I presume that in R07, you are not using UTF-8 and so you need to tell the DM tool what the incoming encoding is. It should then happily convert the Arabic character set from R07 into the UTF-8 that is used in R09.

 

Another possibility is that the encoding is perfectly fine, but your output device does not want UTF-8 but some other encoding. In that case you need to tell jBASE what the output character encoding should be. You set environment variables to do this. Basically everything is stored as UTF-8 in the database and in the program and is converted on the fly at input and output time, should the input device or output device not work with UTF-8 encodings and/or Unicode code points.

 

Jim

[ramesh d]

Hi ,

Thanks for  yor reply.can u look at my problem once again.

 

In R07
Character Set used is IS08859-1 (I am not sure) there is no code page defined in .profile

Example of character set is :
For a Customer Inputted, the value of Arabic fields contain characters as follows. in database level
182 Ô ÍÓä ÇáÇ äæÑ
ÇáÓíÏÉ ÒíäÈ - ÇáÞÇåÑÉ
åÇáÉ ÚÈÏ ÇáãäÚã ãÍãÏ ÚÈÏ ÇáÎÇáÞ

In R09
Character Set used is UTF-8 (code page set to UTF-8 in .profile)
For a Customer Inputted, the value of Arabic fields contain characters as follows.
¶ØµØ«Ø¶ØµØ« سييس سيسيس
سيسيسي صثضصثضص ضصثص

But When we convert file (taken from R07) using jutf8 we get a different character set.

jutf8 <directory name>   

سيبقيبلبمنمببمنيÃ
This is the data that is finally written to the DataBase which is not correct.

After upload of this records, we are unable to see arabic in Browser.It is showing above  characters only

 

Can u help me in this

 

Thanks
 

[Jim Idle]

The incoming code page/character set will definitely NOT be ISO8859-1 (IANA) as this does not encode any Arabic charactersJ http://en.wikipedia.org/wiki/ISO/IEC_8859-1 .

 

So, this will be our problem as unless you tell jutf8 what the incoming character set actually is. You do not say what the base operating system is (please take a moment to read the posting guidelines inked at the bottom of this message), so I can’t give you more than a few ideas about what the incoming code page is, but likely candidates are:

 

ISO:

 

ISO-8859-6 (Arabic)

 

 

Windows 1256 – Arabic

 

IBM:

• Arabic - Personal Computer (00864)
• Arabic 8-Bit ISO/ASCII (01008)
• Arabic Bilingual (00420)
• Arabic Code Page, Data Storage & Interchange (01089)
• Arabic Extended (01029)
• Arabic Extended (01046)
• Arabic (XCOM2) (01007)
• Arabic/French - Personal Computer (01127)
• Arabic/Latin for OS/390 Open Edition (00425)

 

 

I suspect 8859-6 is the one to start with, so specify this to jutf8, with an output of utf8. Then of course you must make sure that the web page you are displaying is flagged as being in UTF-8.

[John Watson]

Hi,

Although not an answer to the posed question...

I guess there must be a reason you are *migrating* from R07 to R09 but
it would appear more logical to *upgrade* using the standard tools -
this way the files remain largely untouched.

Perhaps if you explained the reasons forcing the migration then there
may be advice that would help.

Regards,

John.

[Jim Idle]

Seems like good advice. If your R07 install is working with Arabic, then would it not be that your R09 install is not correctly configured as the data must already be properly encoded? Perhaps it is just the way you are looking at the UTF-8 in the data files (see prior post about i18n) and you need to tell jBASE that your output device expects 8859-6?

Jim

> -----Original Message-----
> From: jb...@googlegroups.com [mailto:jb...@googlegroups.com] On Behalf
> Of John Watson
> Sent: Tuesday, November 03, 2009 1:18 AM
> To: jBASE
> Subject: Re: T24 FILE IS GETTING CORRUPTED
>
>

[ramesh d]

Hi JIM,

 

Thanks

 

It is working fine

 

Im using jutf8 -c windows-1256 <filename>

 

Thank u very much.

:

Regards,

Ramesh

[Jim Idle]

Ahlan Wa Sahlan ;-)

 

From: jb...@googlegroups.com [mailto:jb...@googlegroups.com] On Behalf Of ramesh d
Sent: Tuesday, November 03, 2009 8:48 AM
To: jb...@googlegroups.com
Subject: Re: T24 FILE IS GETTING CORRUPTED

 

Hi JIM,

 

Thanks

 

 

 

It is working fine

 

Im using jutf8 -c windows-1256 <filename>

 

Thank u very much.

:

Regards,

Ramesh

 

--