-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possibly unicode output in platform/mission values #224
Comments
Doesn't really look like UTF-16. Are those the only two values you see it in? Also, can you say what the ST0601 Version is reported as for this file? |
I'll have to check next week, I didn't write down the file name and now I'm not sure how to replicate |
Can you (manually, if necessary) apply these changes and show a small example of the result?
(Hopefully you're familiar with the syntax. If not you add the three lines that are marked with |
@dbussert Did you have a chance to look at this? |
Unfortunately I cannot find the file that caused this in the first place. I saw it on one pared output, but I moved on and can't replicate again. I might have to reopen if I come across it again |
I found this output in some files I tested with
jmisb_example
, and I noticed because a JSON parser failed to read the valueI think it's unicode, but I'm not entirely sure what it is. The whole file parses fine otherwise.
The text was updated successfully, but these errors were encountered: