-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import tool does not read UTF-8 encoded files as UTF-8 #1379
Comments
Hi @AnnikaRPS ! Could you please provide us with the file so that I can more easily reproduce the error? |
Hi @georgeDaskalakis, |
Even excel cannot read this file properly, so I would say - very low prio.. |
Let's be better than Excel then :) |
rwmcintosh
added a commit
that referenced
this issue
Feb 14, 2024
* 1886 importer unit for fraction not recognized (#1892) * changing the check * correction to get the first non empty unit * cleaning up * Fixes #1925 (#1926) @Yuri05 Merging. NEed to test in the app * Fixes #1925 (#1927) * 2566 fixed (#1932) * nunit adapter updated (#1938) * Fixes #1379 (#1948) * Fixes #1946 mobi cannot handler observed data sets with only 1 point (#1947) * Fixes #1949 data importer parsing unit should be case insensitive (#1952) * Fixes #1949 data importer parsing unit should be case insensitive * Run resharper * Remove fake to use real dimensions * Remove fake to use real dimensions * refactoring and removing further .HasUnit() calls --------- Co-authored-by: georgeDaskalakis <37107428+georgeDaskalakis@users.noreply.github.com> * preventing exception (#1957) * templates changed (#1962) --------- Co-authored-by: georgeDaskalakis <37107428+georgeDaskalakis@users.noreply.github.com> Co-authored-by: Michael Sevestre <michael@design2code.ca>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When importing data from an UTF-8 encoded data file, PK-Sim seems to read the data as another format (probably LATIN-1). This results in problems when the file contains a "µ" symbol, as this is encoded differently in UTF-8 in comparison to LATIN-1. The result looks like this:

The text was updated successfully, but these errors were encountered: