noorienraza
New Member
DBCODEPAGE- iso8859-1
CPSTREAM CPTERM-ibm850
CPINTERNAL CHARSET - iso8859-1
Progress Ver 11.1 on unix .
When copying a file in utf format to longchar variable and converting to iso8859-1, special dutch characters are being converterd to junk characters. (e.g. umlaut).
COPY-LOB FROM FILE (ip-xml-tx) TO OBJECT lv-long CONVERT TARGET CODEPAGE "iso8859-1".
CREATE X-DOCUMENT lv-doc-hd.
lv-doc-hd:LOAD("longchar", lv-long, FALSE) .
lv-doc-hd is then used to populate a dataset and validate/update the database.
I tried giving SOURCE CODEPAGE "utf-8" and it seems to work. But the real issue i have is that this xml file is received from Sonic ESB in utf and there seems to be only one function "getLongTextCP" that allows code page conversion to a target codepage and cannot specify source codepage any where. So on using this function "getLongTextCP" and then reading the data in the dataset, the dataset contains junk characters.
Thanks
CPSTREAM CPTERM-ibm850
CPINTERNAL CHARSET - iso8859-1
Progress Ver 11.1 on unix .
When copying a file in utf format to longchar variable and converting to iso8859-1, special dutch characters are being converterd to junk characters. (e.g. umlaut).
COPY-LOB FROM FILE (ip-xml-tx) TO OBJECT lv-long CONVERT TARGET CODEPAGE "iso8859-1".
CREATE X-DOCUMENT lv-doc-hd.
lv-doc-hd:LOAD("longchar", lv-long, FALSE) .
lv-doc-hd is then used to populate a dataset and validate/update the database.
I tried giving SOURCE CODEPAGE "utf-8" and it seems to work. But the real issue i have is that this xml file is received from Sonic ESB in utf and there seems to be only one function "getLongTextCP" that allows code page conversion to a target codepage and cannot specify source codepage any where. So on using this function "getLongTextCP" and then reading the data in the dataset, the dataset contains junk characters.
Thanks