SV: Converting from UTF16LE to Ascii

["Magne Kofoed" <ma-kofo@xxxxxxxxxxx>]

Hi,
 
I changed one stmt (the data variable) in the readlineUTF procedure:
    if pos = 0;                                   
       data += inpbuf.buf;                        
       inpbuf.pos += %len(inpbuf.buf);            
    else;                                         
       len = (pos - inpbuf.pos) + %len(EOL);      
       // data  += %subst(inpbuf.buf:inpbuf.pos:len); 
       data  = %subst(inpbuf.buf:inpbuf.pos:len); 
       inpbuf.pos += len;                         
    endif;                                        
 
Works better now, but there is still one more bug.
Seems like some data is missing in the beginning of the last data record in every buffer.
Or the first record after a new read into the buffer that is missing the data.
Have to debug more...
 
Mvh
Magne

 
________________________________

Fra: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx på vegne av Magne Kofoed
Sendt: ma 17.10.2011 18:49
Til: HTTPAPI and FTPAPI Projects
Emne: SV: Converting from UTF16LE to Ascii


 Hi Jan, 
 
thanks, yes, I found the example program and use it to write to a pf. 
Scott, thank you for this example program.
 
But I beleave there is a bug here, sometimes the variable UTFLINE has the whole buffer when the program writes to the pf. I'll try to debug and return to the list if I find out what's wrong.
 
Best regards,
Magne
  

________________________________

Fra: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx på vegne av Jan Grove Vejlstrup
Sendt: ma 17.10.2011 14:55
Til: HTTPAPI and FTPAPI Projects
Emne: Re: Converting from UTF16LE to Ascii



Hi Magne

Scott Klement wrote a little conversion-program for this.

You can find it here:

http://forums.systeminetwork.com/isnetforums/showthread.php?t=145571


Best regards

Jan
Am 14.10.2011 19:06, schrieb Scott Klement:
> Hi Magne,
>
> The file you have is UTF-16LE, but CCSID 1200 is UTF-16.  The "LE"
> stands for "little endian", whereas CCSID 1200 is "big endian."
>
> IBM does not officially support UTF-16LE (CCSID 1202) anywhere on the
> system as far as I know -- the only IBM-approved way to deal with
> UTF-16LE is by converting it from UTF-16LE to UTF-16 (CCSID 1200) with
> the QlgTransformUCSData() API.
>
> Once converted to UTF-16 (which is fully supported), you can mark it as
> CCSID 1200 and deal with it normally.
>
>
> On 10/14/2011 3:57 AM, Magne Kofoed wrote:
>>      Hi Scott,
>>
>>
>>      I got a file in Unicode (UTF16LE) and tries to import to a pf.
>>
>>      I have read a couple of your articles about this and got a few leads
>>      on how to do this, but could not find how to get from Unicode to
>>      ascii.
>>
>>
>>      1.      I store the file in IFS, it gets CCSID = 1252.  I can view the
>>      file with wrklnk and option 5, but I guess it's still Unicode since
>>      I've just stored it.
>>
>>      2.      I tried to use these commands with no success:
>>
>>      CHGATR OB(`/magnek/mms1.txt') ATR(*CCSID) VALUE(1200)
>>
>>      I can not see any characters with wrklnk and option 5. But wordpad
>>      shows the file ok.
>>
>>      CHGATR OB(`/magnek/mms1.txt') ATR(*CCSID) VALUE(819)
>>
>>      Same result as in nbr 1.
>>
>>      3.      I tried to use CPY fromccsid(1200) toccsid(819). Same result
>>      as in nbr 1.
>>
>>      4.      I tried to use CPYFRMSTMF and CPYFRMIMPF with no success.
>>
>>      How can I get this UTF16LE file from the IFS to a PF?
>>
>>
>>      Best regards,
>>
>>      Magne
>>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
>
>

<<winmail.dat>>

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------