Oklab captialization

[mysteryDate]

In tremendous nit news: In the spec, the "Oklab" color space is capitalized as "OKLab"

https://csswg.sesse.net/css-color-4/#specifying-oklab-oklch

In Ottosson blog that the spec references, the color space is always capitalized as "Oklab":

https://bottosson.github.io/posts/oklab/

Where should we be consistent about capitalization if not in spec documents?

[svgeesus]

You are right.

[svgeesus]

Now we need a consistent capitalization for OKLCH, where Björn Ottosson
does not give any guidance. I guess Oklch?

[svgeesus]

In the absence of other opinions, going for Oklch.

[LeaVerou]

"Oklch" looks really wrong. Could we please reconsider, especially since this was something we only went with in the absence of other opinions?

• There is no precedent for referring to LCH as lch. LCH is typically capitalized, or only the h is lowercase: https://en.wikipedia.org/wiki/HCL_color_space
• LCH being an initialism would point towards uppercase, while it's ok to lowercase the "ab" in "Lab" since that’s what they are actually called.
• "OKLCH" seems far more widespread

No opinion about OKLCH vs OKLCh vs OkLCH, but strong -1 on Oklch.

[svgeesus]

Björn uses OKLCh in passing, while defining Okhsv and Okhsl. Note that his OKLCh uses L_r rather than L, too.

[LeaVerou]

I’m fine with OKLCh. @astearns I wonder if we could get an async resolution on this?

[astearns]

@LeaVerou I am assuming this is just for the specification. The functions and keywords are case-insensitive in code, correct?

[svgeesus]

Yes it is just a spec consistency issue with no impact on implementations

[astearns]

OK, then I think there is no resolution required. This can be just at the editor’s discretion.

[Crissov]

So, now it’s “OKLCh” but still “Oklab”, not “OKLab”!?

[svgeesus]

So, now it’s “OKLCh” but still “Oklab”, not “OKLab”!?

Correct. Both using the original author preferred spelling.