transposed JBIG2 text segments with non-topleft reference corner don't render correctly

[nico]

Attach (recommended) or Link to PDF file here:

symbol-texttranspose.pdf

symbol-topright-transposed.pdf

symbol-bottomleft-transposed.pdf

symbol-bottomright-transposed.pdf

Configuration:

• Web browser and its version: Chrome 123.0.6312.59

• Operating system and its version: macOS 13.5.2

• PDF.js version: today's trunk at https://mozilla.github.io/pdf.js/web/viewer.html (I verified it has the fix for JBIG2 text segments with reference corner on the right do not render correctly #17871 already).

• Is a browser extension: No

Steps to reproduce the problem:

1. Open each of the four PDFs above

What is the expected behavior? (add screenshot)

They should all look like the first one:

What went wrong? (add screenshot)

The ones that have the reference corner not set to topleft are in various states of disarray:

ITU-T_T_88__08_2018.pdf 6.4.5 Decoding the text region has two steps for updating cur_s, once in vi) Update CURS as follows: before drawing the bitmap, and then again xi) Update CURS as follows: after drawing the bitmap. It looks like 25f6a0c mixes up these two steps with the "is transposed" check. Depending on the reference corner, this needs to happen before or after drawing for both transposed and untransposed iamges.

Like in #17871: I made these files myself while writing a JBIG2 decoder. I'm reasonably confident that the files and Chrome and jbig2dec and my decoder are correct, but it's possible the files are wrong instead.

[nico]

Oh, and this isn't purely theoretical: This slightly-more-real-world PDF looks wonky because of this.
transpose2.pdf

It's not fully real-world since it's 042_19.jb2 from https://git.ghostscript.com/?p=tests.git;a=tree;f=jbig2;h=8a7abaf842435e204c1ff1dbeed10826bf24afe6;hb=HEAD wrapped in a PDF, so it's still a bit synthetic. But it's a file made by someone else at least, which maybe gives the bug report more credence.