From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: Multistandard PDF
Date: Fri, 28 Feb 2020 19:01:05 +0100 [thread overview]
Message-ID: <c2e4ac85-42ab-b1e6-49e1-945f1f6320f9@gmx.es> (raw)
In-Reply-To: <4b8b7aea-d8c3-b997-c42c-6e66de26fa3a@robinschwab.ch>
On 2/27/20 3:19 PM, Robin Schwab wrote:
> [...]
> Why should I have to choose whether my PDF is accessible to search
> engines, the disabled or the print-shop? Shouldn't everybody be able to
> access my document?
Hi Robin,
I may be missing your point, but consider the following: you are setting
a format or a format version.
AfaIk, documents that contain file format information inside only allow
one format. They may be compilant with other formats (or versions of the
same format), but this is something else.
With PDF versions and standards, this goes the same way. You might have
a PDF-1.7 document that only uses features already defined in PDF-1.4.
Also you might have a PDF/A document with features already available in
PDF/UA and PDF/X.
But in any case, you only have one field for document version (or standard).
Just in case it helps,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-02-28 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 14:19 Robin Schwab
2020-02-27 16:01 ` Hans Hagen
2020-02-28 18:01 ` Pablo Rodriguez [this message]
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=c2e4ac85-42ab-b1e6-49e1-945f1f6320f9@gmx.es \
--to=oinos@gmx.es \
--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).