Bug? Nordic (æøå) characters garbled using $INCLUDE and UTF-8 encoded .qvs
[Qlivkiew 11.20 SR3, using -prj folders]
My source files contain field names using Norwegian characters.
I am moving scripts out of the QVWs and into QVS for improved version control (Git), and encountered the following issue:
When using Norwegian/Nordic characters in a QVS that is stored with UTF-8 encoding, I get garbage letters back when executing the script. It runs fine when the same text sits in the QVW.
I have a partially successful workaround by saving the QVS as Windows-1252 instead, so this seems to be encoding-related. But, this is not a solution as it confuses my version control, and, UTF is after all the new standard and this should frankly load without issues.
Screenshot from attatched example QVW, where the same data is loaded twice, with different results:
The two .qvs files contain inline tables with identical data (different table/fieldname to separate on load), but have been saved with the respective encodings in an external text editor (Sublime Text 2):
LOAD * INLINE [
LOAD * INLINE [
The QVW load script has these lines:
My questions are:
- Is there a way to specify which encoding should be used when $INCLUDE-ing (similar to when you LOAD/STORE)?
- Anyone else is able to reproduce this?
- Could it be a bug in Qlikview? And if so, how can I report it to Qliktech? I can not find any "submit case" section in my Customer Portal.
Re: Bug? Nordic (æøå) characters garbled using $INCLUDE and UTF-8 encoded .qvs
I can confirm that the issue is still present in Qlikview 11.20 SR6. It does not matter if you use the prj-folder or not, I have the issue without it at least.
Vadim's solution works for me too, saving the qvs as UTF-8 with BOM ensures that nordic characters are loaded properly. I've had this problem in other programs (Visual Studio/C#) as well, so this might actually be a Windows-issue, not Qlik-issue. Still it should be handled, though.