Suggestion: Include in documentation what encoding files should have

serettig's picture
Forums: 

Hi,

while playing around a bit with h5p my changes suddenly stopped working. The libraries in the development folder simply weren't loaded by h5p anymore and uploading manually created .h5p-packages didn't work because there was always something wrong with one of the json-files. It took me some time to figure out that the files in a h5p library must be encoding with UTF-8 without BOM to work. I used Visual Studio to edit the files and it automatically saved them with BOM.

I think it would be useful if this bit of information was included somewhere in the documentation for beginner developers. I guess it only applies if the tools you use automatically change the encoding of a file, but it's not really obvious. Or does this restriction not exist and my problem was something else and fiddling around has solved it in another way?

Sebastian

icc's picture

Ah, that is strange I didn't think any coding editor did that, at least to JS files as it's discouraged in general: https://stackoverflow.com/a/2223926/588777

Thanks for sharing!