From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: ntg-context@ntg.nl
Subject: Re: Reproducible PDF output not working
Date: Tue, 24 Apr 2018 10:03:16 +0200 [thread overview]
Message-ID: <20180424080316.GA3019069@phare.normalesup.org> (raw)
In-Reply-To: <87sh7l8bya.fsf@gmail.com>
> On the other hand, with the 2017.11.14 version, the identifier in the
> output of `context --nodates' is just
>
> <pdfx:ID>foo</pdfx:ID>
The longer identifier is definitely better, but it should be possible
to make it predictable over successive runs.
> PS: Incidentally, what is the "-19:00" in date in the first identifier?
> In my time zone, IST, I would have expected 2018-04-24T01:49:47+05:30.
I remember noticing something strange in the date format when files
were compiled after midnight local time while the UTC time was before
midnight. It didn’t seem enough to send a bug report at the time, but I
can look into it again.
And thanks to Hans for his speedy response, as usual :-)
Best,
Arthur
___________________________________________________________________________________
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 prev parent reply other threads:[~2018-04-24 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 20:30 N. Raghavendra
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 [this message]
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=20180424080316.GA3019069@phare.normalesup.org \
--to=arthur.reutenauer@normalesup.org \
--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).