You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The taxon data is not exported as UTF-8, despite the fileEncoding = "UTF-8" argument in the write.csv statement
E.g. in line 188 from the taxon dataset, the special character č in the scientificNamePastinaca sativa L. subsp. urens (Req. ex Godr.) čelak is reversed to c.
I suspect this problem is somehow due to a printing bug in R, despite the fact that the data it is correctly read and stored. Apparently, the print() method on data.frame tries to round-trip characters through the active encoding, which is lossy when converting UTF-8 encoded characters. (see this GitHub issue) . However, this is just an idea, I have tried several other options, without result.
@qgroom do you have any idea what the problem is here?
The text was updated successfully, but these errors were encountered:
There seems to be a problem with the data encoding when importing from and exporting to the taxon dataset to a .csv file.
With respect to the importing:
A warning message emerges:
This warning message only occurs in Windows and can be changed after applying
see this table of locales and the following GitHub issue
I already adapted this in the script
With respect to the exporting:
The taxon data is not exported as UTF-8, despite the
fileEncoding = "UTF-8"
argument in thewrite.csv
statementE.g. in line 188 from the taxon dataset, the special character č in the
scientificName
Pastinaca sativa L. subsp. urens (Req. ex Godr.) čelak
is reversed to c.I suspect this problem is somehow due to a printing bug in R, despite the fact that the data it is correctly read and stored. Apparently, the
print()
method on data.frame tries to round-trip characters through the active encoding, which is lossy when converting UTF-8 encoded characters. (see this GitHub issue) . However, this is just an idea, I have tried several other options, without result.@qgroom do you have any idea what the problem is here?
The text was updated successfully, but these errors were encountered: