>>>>Hi all,
>>>>
>>>>I posted this problem and found a solution to it by using CONFIG.FPW with the proper CODEPAGE setting in it.
>>>>
>>>>Problem: We have a program that creates an XML file output. As such, international characters have to be transformed to its equivalent in
>>
>>
>>Easy for you to say. ;)
>
>Are you sure you quoted the relevant part of the message? :)
>
>Ah, no, it was my message that got truncated.
>
>It was about the extended character set and cursortoxml() which produces unreadable xml unless the character, varchar and memo fields are marked as NoCpTrans (i.e. as binary). Binary fields are stored as Base64 strings in CDATA blocks, which then presents no problem.
>
>Now that he says they have a program which creates XML - if it writes XML by using some other technique than cursortoxml(), then this may or may not apply.

I use straight STRTRAN() and STRTOFILE() functions to build the XML - which is actually a text file as far as my program is concerned. The resulting XML file can be opened in IE without problem so I think the XML file is valid.