Special/Unicode Characters Not Parsing Properly #110
-
Beta Was this translation helpful? Give feedback.
Replies: 8 comments
-
Working fine on the We are currently testing and preparing the DP+ for a version 1.0 release |
Beta Was this translation helpful? Give feedback.
-
Hi @sagargg , If its still a problem, what's the encoding of the file you're uploading? DP+ normalizes non UTF8-encoded files to their "lossy" encoding - i.e. replacing invalid UTF-8 sequences with U+FFFD REPLACEMENT CHARACTER, which is the � character you're getting instead of the euro currency symbol. |
Beta Was this translation helpful? Give feedback.
-
@jqnatividad Maybe it is happening only on macOS. Even it is happening on the latest version of qsv. |
Beta Was this translation helpful? Give feedback.
-
@sagargg , do you mind uploading a sample file here? I also have macOS (M2 Pro Mac Mini) and it works without issues.
|
Beta Was this translation helpful? Give feedback.
-
BTW, I just noticed you're on a very old version of qsv - 0.92.0. You should upgrade to qsv 0.108.0 |
Beta Was this translation helpful? Give feedback.
-
@jqnatividad yeah, it worked with the file that you've shared. Here is the file i'm using. |
Beta Was this translation helpful? Give feedback.
-
The encoding of the file is not utf-8, that's why
|
Beta Was this translation helpful? Give feedback.
-
okay. Now I understood, Thank you for clarifying. |
Beta Was this translation helpful? Give feedback.
The encoding of the file is not utf-8, that's why
qsv input
did a lossy-transcoding to utf8.