topic Re: french characters in load script in App Development

french characters in load script

edwin — Tue, 11 Mar 2025 13:34:00 GMT

hi,

wondering if any of you have encountered a problem where you need to use special characters in your load qvs script. im pivoting a table and it results in a field name with french characters

just the act of pivoting itself does not cause any problem, however theres a business rule i need to perform on one the fields and i need to do some calculation but the resulting field name looks like this:
[Taux de réponse],

when i run the load script it is interpreted as

The following error occurred:
Field 'Taux de rÃ©ponse' not found

how do we address this?

thanks

edwin

Re: french characters in load script

marcus_sommer — Tue, 11 Mar 2025 15:10:52 GMT

It's a conflict between the used char-sets - source vs. target. On the Qlik side it might be adjusted per the variable CollationLocale - see: System variables | QlikView Help. More background to matter provides: Search - But what shall you find? - Qlik Community - 1472194. Further some fonts aren't able to show this kind of special chars.

But the issue might be already happens before - means the replacement might be caused from the data-base / driver / connection. Often there are similar possible adjustments within these tools.

If it are just one or two fields you may to consider to reverse the char-replacement with a mapping-logic, like shown here:

Passing parameter strings that contain special cha... - Qlik Community - 1247166

Re: french characters in load script

henrikalmen — Tue, 11 Mar 2025 15:25:23 GMT

I think maybe you are saying that the problem you have is in an external script file, that gets included in the loadscript when reload is performed?

If so, it sounds like you could solve your issue by changing the locale of the qvs text file. There are tools to do such things, for example the open source software Notepad++ for Windows. Just open the script file in nbotepad++ and convert the encoding in the "Encoding" menu. You will not see any differences on screen, but save the file and try reloading your app again. I'd say it's likely that UTF-8 is what you need, but that your script file is stored in ANSI. (I could be wring, you'll have to experiment.)