Skip to content
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

GLSL Specification 4.60.8: incorrect formatting #214

Open
kociap opened this issue Sep 11, 2023 · 2 comments
Open

GLSL Specification 4.60.8: incorrect formatting #214

kociap opened this issue Sep 11, 2023 · 2 comments
Assignees
Milestone

Comments

@kociap
Copy link

kociap commented Sep 11, 2023

In section 5.7 on page 124 of The OpenGL Shading Language, Version 4.60.8, the paragraph starting with "The arithmetic unary operators..." is incorrectly formatted resulting in missing symbols.

Preserving formatting as much as possible, what it currently looks like:

The arithmetic unary operators plus (*), negate (-), post- and pre-increment and decrement
(-- and *
+) operate on integer or floating-point values (including vectors and matrices).

What (I believe) it should look like:

The arithmetic unary operators plus (+), negate (-), post- and pre-increment and decrement
(-- and ++) operate on integer or floating-point values (including vectors and matrices).

Image of the excerpt:

image

@pdaniell-nv pdaniell-nv added this to the Needs Triage milestone Sep 27, 2023
@gnl21
Copy link
Contributor

gnl21 commented Dec 12, 2023

Thanks. The operators on that line have been partially interpreted as markup during the spec generation, making the output totally incorrect. I've fixed the spec source so this will be fixed in the next release.

alan-baker pushed a commit to alan-baker/GLSL that referenced this issue Jan 24, 2024
Some of the operators ('+' and '++') were being treated as asciidoctor
markup, so they were disappearing and some of the characters that were
supposed to be markup were appearing in their place. Fix by using the
builtin macro for '+' instead of the character.

Fixes Public GLSL issue KhronosGroup#214.
@dj2
Copy link
Contributor

dj2 commented Aug 25, 2024

Can this be closed as it appears to be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants