[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Another possible gb.poppler bug?


On 12/1/25 5:11 PM, gbWilly wrote:
On Monday, December 1st, 2025 at 20:24, Lee <t.lee.davidson@xxxxxxxxx> wrote:

On 12/1/25 9:48 AM, gbWilly wrote:

The file: E16536_PRIME_B550-PLUS_UM_WEB_051420.pdf -> loads internal thumbnails
The file: F16866_TUF_GAMING_B460-PLUS_UM_V2_WEB.pdf -> does NOT load internal thumbnails


Maybe that's because "F16866_TUF_GAMING_B460-PLUS_UM_V2_WEB.pdf" does not contain any embedded thumbnails.

I uploaded that file to https://pdfcrowd.com/inspect-pdf/. There are no "Thumb" references.

"E16536_PRIME_B550-PLUS_UM_WEB_051420.pdf" wouldn't finish loading there. But, it did at https://pdfux.com/inspect-pdf/. It has
thumb references and your test project finds them.

"PRIME_PROART_TUF_GAMING_AMD_AM5_Series_BIOS_EM_WEB_EN.pdf" loaded at https://pdfcrowd.com/inspect-pdf/. It has Thumb references
and your test project finds them.



I'm trying to understand that page

Which page? https://pdfcrowd.com/inspect-pdf/ ?
Just upload the PDF, let it analyze it, and then use your browser's search function to find "Thumb".
It's a bit more complex with https://pdfux.com/inspect-pdf/.


I may have guessed wrong about there being no Thumbs in the F16866* file. To my knowledge, Okular will not display thumbnails if there are none in the document. But, it does for that file.

What may be the issue is, that file appears to be PDF version 1.4, while the other two are 1.6 or 1.7. Perhaps the thumbnails are referenced differently in the earlier version.


--
Lee

--- Gambas User List Netiquette [https://gambaswiki.org/wiki/doc/netiquette] ----
--- Gambas User List Archive [https://lists.gambas-basic.org/archive/user] ----


Follow-Ups:
Re: Another possible gb.poppler bug?gbWilly <gbWilly@xxxxxxxxxxxxxx>
References:
Another possible gb.poppler bug?gbWilly <gbWilly@xxxxxxxxxxxxxx>
Re: Another possible gb.poppler bug?Lee <t.lee.davidson@xxxxxxxxx>
Re: Another possible gb.poppler bug?gbWilly <gbWilly@xxxxxxxxxxxxxx>