Since files are encoded in UTF-8, it can be written normally:
- "µm/m/a"
Not sure yet whether it may cause bugs in future. The string is displayed correctly on the front-end for now, I suppose JS YAML deserializer handles these entities.
I ran the script allowing for unicode characters and tested the dataset using Paneron, and everything is working correctly. Pushed the data to the gr-registry and updated the dump script.
In this file, there’s this line:
Since files are encoded in UTF-8, it can be written normally:
Not sure yet whether it may cause bugs in future. The string is displayed correctly on the front-end for now, I suppose JS YAML deserializer handles these entities.