From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [dev-context] type key in \setupattachment
Date: Thu, 20 Jun 2019 10:46:26 +0200 [thread overview]
Message-ID: <6e5be4fb-31fe-1464-5c18-4e9f1ac3c4ad@xs4all.nl> (raw)
In-Reply-To: <61681705-2681-46b4-9bb8-3fc4b4ab866e@gmx.es>
On 6/19/2019 9:28 PM, Pablo Rodriguez wrote:
> Hi Wolfgang,
>
> this comes from a previous message from this mailing list
> (https://mailman.ntg.nl/pipermail/dev-context/2019/003574.html), which I
> needed a long while to understand 😅.
>
> Would it be possible that the \setupattachment command has a "type" key
> to specify its MIME type? (Default should be "application/octet-stream"
> [or so it seems].)
>
> This is required to add the value to the /Subtype entry in the
> /Embeddedfile dictionary
> (https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#nameddest=G6.1942814)
>
> This is optional information in PDF-1.7, but required in PDF/A-2.
>
> Many thanks for your help,
there is a type key
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next parent reply other threads:[~2019-06-20 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <61681705-2681-46b4-9bb8-3fc4b4ab866e@gmx.es>
2019-06-20 8:46 ` Hans Hagen [this message]
2019-06-20 10:07 ` Wolfgang Schuster
2019-06-20 14:21 ` Pablo Rodriguez
2019-07-24 18:41 ` Henning Hraban Ramm
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=6e5be4fb-31fe-1464-5c18-4e9f1ac3c4ad@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).