Open jakubklimek opened 7 years ago
It seems to be consistent now:
_:node1df0cpihix2 <file://Bankovní\u0020spojení-input.xlsx.csv#Bankovn%C3%AD+spojen%C3%AD>
"Česká národní banka";
<file://Bankovní\u0020spojení-input.xlsx.csv#K%C3%B3dbanky> "0710" .`
We are using URLEncoder.encode(part, "UTF-8")
for encoding, so we would need to find/create another function that would keep UTF-8.
That is still not consistent - why is the space in the filename part encoded like \u0020
, which is the unicode encoding used in Turtle, and not percent endocing %20
as it would be in the fragment part?
Property IRIs are escaped inconsistently. In the filename part, they are not escaped at all, resulting in invalid IRIs (containing spaces) and in the path part, they are escaped as URIs (including UTF-8 characters) which is unnecessary with IRIs - Czech characters do not need to be escaped anymore.
It would be best if 1) Escaping would be consistent 2) UTF-8 characters were not escaped e.g.