Updating line endings when generating JSON schemas

The previous translation used the native line endings (which is Windows for me), but the JSON specs are stored in git with Unix line endings. Hence every time they are recreated it looks like the whole file has changed. The translation tool now explicitly uses Unix line endings when writing out the files.

Edited by Mark Canterbury

Merge request reports

Loading
+147 −147

File changed.

Contains only whitespace changes.

+163 −163

File changed.

Contains only whitespace changes.

+605 −605

File changed.

Contains only whitespace changes.

+231 −231

File changed.

Contains only whitespace changes.

+147 −147

File changed.

Contains only whitespace changes.

Loading
Loading