From: <denis.maier@unibe.ch>
To: <ntg-context@ntg.nl>
Subject: [NTG-context] Re: tiffs: autoconversion via graphicsmagick produces invalid pdfs
Date: Tue, 12 Sep 2023 15:09:19 +0000 [thread overview]
Message-ID: <ZRAP278MB0495FB7E1702490104A7C7BA83F1A@ZRAP278MB0495.CHEP278.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <ZRAP278MB0495F614D812B80B9487DAAF83F1A@ZRAP278MB0495.CHEP278.PROD.OUTLOOK.COM>
[-- Attachment #1.1: Type: text/plain, Size: 1070 bytes --]
Sorry, that was too quick...
Hi,
currently, ConTeXt can't use tiffs directly, but it uses Graphicsmagick to convert tiffs to pdf on the fly. However, as it seems, graphicsmagick is producing invalid pdfs.
For every included tiff I have something like this in the log:
luatex warning > pdfe: invalid 11 0 R object at offset 573751
luatex warning > pdfe: invalid 11 0 R object at offset 629127
The offsets are different, but it's always this <invalid 11 0 R object>.
This bug has been known for quite some time, but it apparently hasn't been fixed yet: https://sourceforge.net/p/graphicsmagick/bugs/513/
Converting the tiffs to jpeg circumvents the problem. Would it be an option to convert tiffs to jpegs instead of to pdf? (Is that already possible?)
Best,
Denis
Von: denis.maier@unibe.ch <denis.maier@unibe.ch>
Gesendet: Dienstag, 12. September 2023 17:03
An: ntg-context@ntg.nl
Betreff: [NTG-context] tiffs: autoconversion via graphicsmagick produces invalid pdfs
Hi,
currently, ConTeXt can't use tiffs directly, but it uses
[-- Attachment #1.2: Type: text/html, Size: 4470 bytes --]
[-- Attachment #2: Type: text/plain, Size: 495 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-09-12 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 15:03 [NTG-context] " denis.maier
2023-09-12 15:09 ` denis.maier [this message]
2023-09-13 11:36 ` [NTG-context] " denis.maier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZRAP278MB0495FB7E1702490104A7C7BA83F1A@ZRAP278MB0495.CHEP278.PROD.OUTLOOK.COM \
--to=denis.maier@unibe.ch \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).