Qlik Community

Ask a Question

QlikView App Dev

Discussion Board for collaboration related to QlikView App Development.

Announcements
Support Cases coming to Qlik Community Oct. 4! Start chats, open cases, explore resources: READ DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
gidon500
Creator II
Creator II

Export to Xml FILE

Hi  guy

I am using the following macro to export

SUB ExportXml

set Table = ActiveDocument.GetSheetObject("TB02")
Table.ExportXml "C:\Users\user\Documents\SOS\TEXT.XML"

this is the default  setting

<?xml version="1.0" encoding="UTF-8" standalone="true"?>

I want to change the encoding from UTF-8 to WINDOWS-1255

how can I dot it  ,

thanks

gidon

4 Replies
gidon500
Creator II
Creator II
Author

this is how the xml file looks  which is not good

<?xml version="1.0" encoding="UTF-8" standalone="true"?>

<TableBox><_empty_>

<_empty_><_x05D0__x05D0_>

<_x05D0__x05D0_>1

</_x05D0__x05D0_>

<BB>3

</BB><CC>

שלוםHELLO</CC>

<AA>1

</AA></_empty_>

<_empty_>

<_empty_><_x05D0__x05D0_>

<_x05D0__x05D0_>2

</_x05D0__x05D0_>

<BB>4

</BB><CC>

bibi</CC>

<AA>2

</AA></_empty_>

<_empty_>

<_empty_><_x05D0__x05D0_>

<_x05D0__x05D0_>2

</_x05D0__x05D0_>

<BB>5

</BB><CC>

ביבי</CC>

<AA>2

</AA></_empty_>

<_empty_>

<_empty_><_x05D0__x05D0_>

<_x05D0__x05D0_>3

</_x05D0__x05D0_>

<BB>6

</BB><CC>

אמנון</CC>

<AA>3

</AA></_empty_>

<_empty_>

<_empty_><_x05D0__x05D0_>

<_x05D0__x05D0_>99

</_x05D0__x05D0_>

<BB>66

</BB><CC>

Israelישראל</CC>

<AA>99

</AA></_empty_>

</TableBox>

marcus_sommer
MVP & Luminary
MVP & Luminary

You could try to change the default-charset within the user-properties in tab export but beside utf8 there is only unicode and ansi available and I doubt that this will be useful in your case.

If you really need windows-1255 as charset you will need to convert the qlik-export with any third-party tool (some editors like notepad++ and their plugins are quite powerful to convert data and it may be also posible to automate such tasks).

But I think this approach will be quite expensive so I would look if there could be changed anything else in your process to use the native qlik-output.

- Marcus

gidon500
Creator II
Creator II
Author

hi marcus

I did change to Unicode

it remains the same in the header for the file

here it is :

<?xml version="1.0" encoding="UTF-8" standalone="true"?>

gidon

marcus_sommer
MVP & Luminary
MVP & Luminary

You could try to specify your codepage within the second parameter of the export-statement whereby I'm not sure if Qlik will use any other than 0, 1200 or 65001 and which requirements it might need. I think the codepage must be available on your machine and also region-settings within the OS might have an impact.

- Marcus