From: Radhakrishnan CV <cvr@river-valley.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: PDF docs from Org-mode: not valid PDF?
Date: Sat, 15 Dec 2012 07:29:49 +0530 [thread overview]
Message-ID: <CA+uu9n8Md4aGYSnEOsxfMVR4Ro1qXOkgc4JsCXRwLyp7m_MgUA@mail.gmail.com> (raw)
In-Reply-To: <87k3sko3l6.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]
On Sat, Dec 15, 2012 at 12:37 AM, Achim Gratz <Stromeko@nexgo.de> wrote:
> Michael Hannon writes:
> > To proceed with this, I need to generate a series of PDF documents and
> have
> > the boss's admin assistant try to print them. Unfortunately, I've been
> > swamped with some other stuff this week and haven't had a chance to work
> on
> > this.
>
> Would it be possible that you first check what that error really is?
> The one thing that comes to mind is that your PDF maybe references fonts
> that are not available and the easiest solution would be to either
> change to standard fonts or embed them in the PDF (if the license is
> permitting that).
>
As far as I know, PDF/A-1a is not meant for universal printing, instead it
is meant for accessibility. The current stock versions of pdfTeX
distributed are not capable of producing accessible PDF as per PDF/A-1a
specs. Main problem is that TeX does not use a space character and as such
finding word boundary becomes difficult in pdf's created by pdfTeX; read
aloud applications will fail to voice render PDF's by pdfTeX.
However, if the OP is happy with a PDF as per PDF/A-1b, of course, pdfx.sty
distributed with TeXLive (and available at CTAN also) is capable of
creating. This is for web reading and archival purposes.
If universal printing is what is wanted, then the spec to follow is
PDF/X-1a. Again, pdfx.sty does help to generate this too. I think, it is
not a big deal to extend pdfx package to generate pdf's compliant to later
specs like PDF/X-2, 3, ... (all for printing purpose). Later specs have
some advantages too like inclusion of icc color profile is not mandatory,
instead url will do.
I think, orgmode can even help to create a small XMP meta file (for Dublin
Core metadata compliance) needed by pdfx package while creating standards
compliant PDF's which at the moment is created by pdfTeX in an
unsatisfactory fashion.
Best regards
--
Radhakrishnan
[-- Attachment #2: Type: text/html, Size: 2301 bytes --]
next prev parent reply other threads:[~2012-12-15 1:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 21:16 PDF docs from Org-mode: not valid PDF? Michael Hannon
2012-12-08 21:30 ` Karl Voit
2012-12-13 15:24 ` Bastien
2012-12-13 23:38 ` Michael Hannon
2012-12-14 19:07 ` Achim Gratz
2012-12-15 1:59 ` Radhakrishnan CV [this message]
2012-12-15 8:25 ` Bastien
2012-12-17 10:50 ` Radhakrishnan CV
2012-12-24 0:37 ` Bastien
2012-12-14 13:48 ` Jambunathan K
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+uu9n8Md4aGYSnEOsxfMVR4Ro1qXOkgc4JsCXRwLyp7m_MgUA@mail.gmail.com \
--to=cvr@river-valley.org \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).