Typo? in Table 20.6(version 1.4 of the data format spec), different with other spec.

[Oscill1]

In the data format specification version 1.4, Table 20.6 defines anchor indices for 2-subset BPTC partitions. However, I've noticed a potential discrepancy regarding Partition 35:

According to Table 20.6:

Partition 35 lists the anchor index for subset 1 as (2,0)

Whereas in the Khronos OpenGL Extension document [ARB_texture_compression_bptc] (https://registry.khronos.org/OpenGL/extensions/ARB/ARB_texture_compression_bptc.txt):

The anchor index for the second subset of partition 35 is explicitly stated to be 8.

Could the maintainers please clarify:

Which anchor index specification should be considered authoritative for Partition 35?

[fluppeteer]

Sorry for the delay. Spelunking on the authoritative answer, I'll try to be back to you soon.

[Oscill1]

Since this issue has been labeled as a bug, does it indicate that the current specification is incorrect and will be corrected in a future release?

[Oscill1]

I see Table 20.10 BPTC anchor index values for the second subset of two-subset partitioning, by partition number also mentioned anchor index, which is same as Khronos OpenGL Extension document [ARB_texture_compression_bptc] expression.
The anchor index for the second subset of partition 35 is explicitly stated to be 8.
Thus, the Table 20.6 should be wrong. Could you please check it again?

[fluppeteer]

Oops, sorry. Yes, I'll try to get a fix into 1.4.1.