Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

import text file with å,ä,ö

Hello,

I have a problem importing a text file with Swedish characters.

Because of these characters in the "Prg Mgr" column I get a space shift in the following columns.

example2.png

How can I resolve this?

Best regards,

Jonas

1 Solution

Accepted Solutions
evan_kurowski
Specialist
Specialist

Hello Jonas,

This is unusual, none of the alternative code pages I tested seemed to fix the "spillover" of these extended characters into the next column.  In a sense, if you embedded the characters with a  deliberate methodology, you could create a text based hierarchy off of how many of these characters you inserted = equated to how many indentations you wanted to mark the hierarchy node depth.


But anyway... to address the main point of the thread.  Though I didn't incorporate using the Fix Import Wizard into the solution, there does seem to be a workaround.

Importing the entire row as a single field @1:n and then "chopping" it up in later statements into the appropriate sub-lengths allowed me to "replicate" the behavior of the 'Fix Import Wizard' field partitioning.20140813_column_spillover_of_fixed_width_import.png

View solution in original post

2 Replies
ecolomer
Master II
Master II

You can try to change charset ...you use.

evan_kurowski
Specialist
Specialist

Hello Jonas,

This is unusual, none of the alternative code pages I tested seemed to fix the "spillover" of these extended characters into the next column.  In a sense, if you embedded the characters with a  deliberate methodology, you could create a text based hierarchy off of how many of these characters you inserted = equated to how many indentations you wanted to mark the hierarchy node depth.


But anyway... to address the main point of the thread.  Though I didn't incorporate using the Fix Import Wizard into the solution, there does seem to be a workaround.

Importing the entire row as a single field @1:n and then "chopping" it up in later statements into the appropriate sub-lengths allowed me to "replicate" the behavior of the 'Fix Import Wizard' field partitioning.20140813_column_spillover_of_fixed_width_import.png