-
Notifications
You must be signed in to change notification settings - Fork 228
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
Issues with specifications #43
Comments
Congratulations on being the first person to spot the hidden cookie. I am afraid there is no prize.
|
Please refile this at https://github.com/KhronosGroup/KTX-Specification/issues and close this one. Sorry to ask but I have not found a way to mark an issue as filed by somebody else or ensure a particular user will receive notifications about updates to the issue. |
Moved to KhronosGroup/KTX-Specification#1 |
Thanks. |
I assume this is the right place to report issues related to documentation in https://www.khronos.org/opengles/sdk/tools/KTX/file_format_spec/
Issues in An example KTX file: section
0x0D, 0x0A, 0x1A, 0x0A. // final four bytes of Byte[12] identifier
should be0x0D, 0x0A, 0x1A, 0x0A, // final four bytes of Byte[12] identifier
0x6A, 0x6F, 0x6B, 0x65, // UTF8 v: 'gles2\0'
0x6A, 0x6F, 0x6B, 0x65 means j o k e, not g l e sSuggestions:
Byte valuePadding[3 - ((keyAndValueByteSize + 3) % 4)]
).The text was updated successfully, but these errors were encountered: