Timeline for Read JPEG dimensions properly
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 1, 2019 at 21:38 | comment | added | Neil |
The exact line in rdjpjcom.c is, "There could also be non-FF garbage between markers. The treatment of such garbage is unspecified; we choose to skip over it but emit a warning msg."
|
|
| Nov 1, 2019 at 21:24 | vote | accept | Neil | ||
| Oct 31, 2019 at 21:02 | comment | added | Neil |
Wrt 'discarding non-0xff bytes', the code in rdjpgcom.c issues a warning (in next_marker) and just keeps going until the next marker, but apparently any extra 0xFF are legal padding. For this application, I don't care about issuing a warning, but that's worth another comment.
|
|
| Oct 31, 2019 at 14:45 | history | answered | user673679 | CC BY-SA 4.0 |