-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loading hyperref incorrectly overrides PDF Producer #91
Comments
So it does, we could presumably detect harftex and change this, but given that luatex populates the /Producer field anyway it's not clear that hyperref over-writing it by default really helps. It's perhaps a bit different for the original latex/dvips/distiller|ps2pdf route where it is changing the default value. Specifically I suspect this could be removed from
|
Well that's certainly part of the "review pdf resources projekt". Looking at the default output and the one forced by hyperref, I would say that hyperref should at most change the producer for dvips and xetex. All other changes are either unneeded or worse than the default. Perhaps it would be even the best to remove all the settings and leave it to the user, if he wants to change something. /Producer(GPL Ghostscript 9.26) -> /Producer(dvips + GPL Ghostscript 9.26) |
On the specific question: we should drop fiddling with There's a general question here, which I've logged as latex3/latex3#567. |
IMHO, hyperref (or any other package) shouldn’t be changing PDF metadata unless it has to or was explicitly asked to do so. |
@khaledhosny Well |
Yes, that would be reasonable for LaTeX code to do, not so much for individual packages. |
remove them all I would say. Only the dvips one is at all useful and it
would be simpler to be consistent and not do any I think. @joseph Wright
(CHE) <joseph.wright@morningstar2.co.uk> ?
…On Fri, 26 Apr 2019 at 20:20, Ulrike Fischer ***@***.***> wrote:
Well that's certainly part of the "review pdf resources projekt". Looking
at the default output and the one forced by hyperref, I would say that
hyperref should at most change the producer for dvips and xetex. All other
changes are either unneeded or worse than the default. Perhaps it would be
even the best to remove all the settings and leave it to the user, if he
wants to change something.
@davidcarlisle <https://github.com/davidcarlisle> ?
/Producer(GPL Ghostscript 9.26) -> /Producer(dvips + GPL Ghostscript 9.26)
/Producer (pdfTeX-1.40.20) -> /Producer(pdfTeX-1.40.20)
/Producer (LuaTeX-1.10.0) ->Producer(LuaTeX-1.10.0)
/Producer (MiKTeX pdfTeX-1.40.20) -> Producer(pdfTeX-1.40.20)
/Producer(xdvipdfmx (20190225)) -> /Producer(XeTeX 0.999991) ,
/Producer(dvipdfm)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#91 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAJVYAXVUU2TPIZYAEICILLPSNIXRANCNFSM4HIYUXFQ>
.
|
I removed the setting of the producer field from the drivers. The next hyperref version will give |
Merely loading hyperref with no other changes, and processing the document with HarfTeX changes the PDF producer from
HarfTeX-0.1.1
toLuaTeX-1.10.1
.Without
hyperef
:With
hyperref
:The text was updated successfully, but these errors were encountered: