Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
etl_tools
Creator
Creator

QVX Code pages

Hello

We are curretly in process of adding support for QVX files to our ETL tools Advanced ETL Processor and Visual Importer ETL.

I am not able to find full list of Code pages supported and SDK documentation is confusing.

Can someone point me to the right direction please

Mike,

www.etl-tools.com

5 Replies
rbecher
MVP
MVP

Hi Mike,

you can read this from the XML header:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>   // Header Codepage = UTF-8

...

<QvxTableHeader>

<QvxFieldHeader>

     <FieldName>SomeField</FieldName>

     ...

     <CodePage>65001</CodePage>  // Data Codepage = UTF-8

In this case the codepage is UTF-8 (65001):

http://en.wikipedia.org/wiki/Code_page_65001

- Ralf

Astrato.io Head of R&D
etl_tools
Creator
Creator
Author

Ralph

I uderstand that but I guess QVX support several codepages so we want to find a full list of codepages supported

by QlikVIew

so 65001 is UTF8

Any More?

Mike,

www.etl-tools.com

rbecher
MVP
MVP

Yea, would be interesting to know..

I would expect that those are also working:

Windows-1252, ISO-8859-1, UTF-16

but haven't tried so far.


Astrato.io Head of R&D
etl_tools
Creator
Creator
Author

Character encoding used to write field values in the QVX

data stream. 1200/1201 implies UTF16. Byte order mark

(BOM) is not allowed. BigEndian has no effect on UTF16.

If not set then UTF8 is assumed.

Does it it mean 1200 or 1201 implies UTF16?

Mike,

www.etl-tools.com

etl_tools
Creator
Creator
Author

Still no reply ...

Meantime we added support for QVX files generation to our ETL software

http://dbsoftlab.com/online-tutorials/advanced-etl-processor/generating-qlikview-qvx-files.html

Note

All data is exported as UTF8 text using row delimiter

This our first release and we will continue working on improoving our software

Mike,

dbSL

www.etl-tools.com