From: "N. Raghavendra" <nyraghu27132@gmail.com>
To: ntg-context@ntg.nl
Subject: Reproducible PDF output not working
Date: Tue, 24 Apr 2018 02:00:54 +0530 [thread overview]
Message-ID: <87604hacn5.fsf@gmail.com> (raw)
Sometime ago, I asked here about reproducible PDF output, and was told
about the --nodates option of context. It worked then, but doesn't seem
to be working now, with a recent version of context.
----------------------------------------------------------------------
$ cat foo.tex
\starttext
Hello, world!
\stoptext
$ ( rm -f a b foo.log foo.pdf foo.tuc && \
context --nodates foo.tex && cp foo.pdf a && \
sleep 1 && \
context --nodates foo.tex && cp foo.pdf b ) > /dev/null && \
md5sum a b
bdd1911005623a519f5ecb3dbcb8bc7b a
06157e2840c0758ca46d5e7f0be239ef b
$ context --version
[elided]
mtx-context | current version: 2018.04.19 15:53
----------------------------------------------------------------------
File `a' has the words "<pdfx:ID>foo.2018-04-24T01:49:47-19:00</pdfx:ID>",
and file `b' has "<pdfx:ID>foo.2018-04-24T01:49:49-19:00</pdfx:ID>" at
the corresponding position.
Please tell me how to ensure that the PDF output depends only on the
source, and not on the time the output is generated.
Thanks,
Raghu.
--
N. Raghavendra <raghu@hri.res.in>, http://www.retrotexts.net/
Harish-Chandra Research Institute, http://www.hri.res.in/
___________________________________________________________________________________
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 reply other threads:[~2018-04-23 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 20:30 N. Raghavendra [this message]
2018-04-23 21:49 ` Arthur Reutenauer
2018-04-24 4:28 ` N. Raghavendra
2018-04-24 7:44 ` Hans Hagen
2018-04-24 8:37 ` N. Raghavendra
2018-04-24 8:03 ` Arthur Reutenauer
2018-04-24 8:40 ` N. Raghavendra
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=87604hacn5.fsf@gmail.com \
--to=nyraghu27132@gmail.com \
--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).