plug-ins: use g_message instead of g_printerr when there is data loss.

After discussion with Jehan we concluded that it is better to report
these data loss messages to the user using g_message.
This commit is contained in:
Jacob Boerema 2020-10-24 18:31:31 -04:00
parent 3a50e52ac7
commit f336f86f60
1 changed files with 2 additions and 2 deletions

View File

@ -1608,7 +1608,7 @@ load_contiguous (TIFF *tif,
else if (TIFFReadScanline (tif, buffer, y, 0) == -1) else if (TIFFReadScanline (tif, buffer, y, 0) == -1)
{ {
/* Error reading scanline, stop loading */ /* Error reading scanline, stop loading */
g_printerr ("Reading scanline failed. Image may be corrupt at line %d.\n", y); g_message (_("Reading scanline failed. Image may be corrupt at line %d."), y);
g_free (buffer); g_free (buffer);
g_free (bw_buffer); g_free (bw_buffer);
return; return;
@ -1783,7 +1783,7 @@ load_separate (TIFF *tif,
else if (TIFFReadScanline (tif, buffer, y, compindex) == -1) else if (TIFFReadScanline (tif, buffer, y, compindex) == -1)
{ {
/* Error reading scanline, stop loading */ /* Error reading scanline, stop loading */
g_printerr ("Reading scanline failed. Image may be corrupt at line %d.\n", y); g_message (_("Reading scanline failed. Image may be corrupt at line %d."), y);
g_free (buffer); g_free (buffer);
g_free (bw_buffer); g_free (bw_buffer);
return; return;