Chris Lilley

We probably should (and add required handling for unknown unit specifiers). In addition that section really needs a worked example, like: 72dpi 72 ÷ 25.4 × 1,000 = 2,834.64566929 =...

Related: - https://github.com/w3c/PNG-spec/issues/97

Those changes come from - https://github.com/w3c/PNG-spec/pull/93

Related: - https://github.com/w3c/csswg-drafts/issues/6252 - https://github.com/w3c/csswg-drafts/issues/6038 - https://github.com/w3c/csswg-drafts/issues/5837 If this does get added to the PNG spec, we should also describe the interaction and conflict handling when the image and the...

Since this proposal has no backwards-incompatible issues, I feel we as a group should discuss it sometime and at least get agreement (or not) on the overall direction. It could...

An interesting and useful suggestion, though I would want to engage with the medical imaging community first to establish their precise needs._

I was unaware - so this is more an alignment of the specification with current practice, rather than an enhancement

By the way the PNG specification doesn't even call this checksum by name, Adler-32. It just [says, in Compression method 0](https://www.w3.org/TR/png-3/#10CompressionCM0): > Check value | 4 bytes and > The...

> To be clear: it sounds like the current spec text as well as the "street spec" is that encoders must write valid checksums, while decoders may ignore the checksums....

> glyph on the right I assume that "later glyph in the text direction" or something like that is meant (it would be the glyph to the left in RTL,...