Closed Sgeo closed 4 years ago
Come to think of it, VRML 2.0 files all explicitly claim to be UTF-8, so I guess that in theory it's this file's fault.
Yes this is right. UTF-8 is the standard for X3D files. Consider converting your files to UTF-8. Every modern text editor can do that for you.
Describe the bug X_ITE does not parse some files with non-Ascii characters that are encoded in Windows-1252 and compressed with gzip.
Some testing indicates that it works fine with UTF-8, and it works fine uncompressed.
To Reproduce Steps to reproduce the behavior:
Expected behavior A parsing error on line 127 regarding an improperly placed ROUTE statement. (That's this file's problem, not X_ITE's. I have some code elsewhere to allow files like this to load)
Screenshots The line with é occurs immediately before the indicated Viewpoint.
Additional context
musee3.wrl.gz has the é deleted. musee4.wrl.gz has the file re-encoded as UTF-8.