Re: [XeTeX] xelatex, hyperref, and new TeXLive

[Zdenek Wagner]

2016-06-17 0:16 GMT+02:00 Herb Schulz :

> Howdy,
>
> I'd guess it was dumb luck? It just happened that the .../tex/ branch was
> searched before the .../doc/ branch.
>

I think that the order insuch a case depends on the inode value rather than
the path name, hence it is unpredictable.

>
> Good Luck,
> Herb Schulz
>



Zdeněk Wagner
http://ttsm.icpf.cas.cz/team/wagner.shtml
http://icebearsoft.euweb.cz



>
> > On Jun 16, 2016, at 5:10 PM, maxwell  wrote:
> >
> > I remain mystified why this problem didn't bite us with older TeXLive
> distributions (or why it suddenly surfaced with the 2016 version).
>
>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
>   http://tug.org/mailman/listinfo/xetex
>


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[Herb Schulz]

Howdy,

I'd guess it was dumb luck? It just happened that the .../tex/ branch was 
searched before the .../doc/ branch. 

Good Luck,
Herb Schulz

> On Jun 16, 2016, at 5:10 PM, maxwell  wrote:
> 
> I remain mystified why this problem didn't bite us with older TeXLive 
> distributions (or why it suddenly surfaced with the 2016 version).




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[maxwell]

On 6/16/2016 11:46 AM, Herbert Schulz wrote:

kpsewhich hyperref.cfg

really return a file in the .../doc/... branch?


Oh of course! well spotted.

So that is the error.

The file is correctly installed in the doc branch but the OP's
$TEXINPUTS is incorrectly including the
/groups/tools/texlive/2016/texmf-dist/doc tree and worse searching it
before the /groups/tools/texlive/2016/texmf-dist/tex tree.


Yeap, $TEXINPUTS was being set in order to include several directories 
of local files, so I assumed it also had to include the necessary paths 
under texlive/2016/.  The problem was that $TEXINPUTS was set to include 
*all* paths under

texlive/2016/texmf-dist/
and the documentation directories are included under "all paths."  The 
trick is to use a trailing colon in the definition of $TEXINPUTS (you 
probably knew that, but I'm recording it here for the next time I make 
this mistake :-)), rather than an explicit pointer.  The trailing colon 
selects whatever the appropriate directories under texmf-dist are, 
rather than all 27 subdirectories.


I guess the other solution would be to include links from our 
texmf-local directory to our other directories of local files.  (It 
would not be as easy to put these local files under texmf-local, because 
some of them come from other tools we use, e.g. dblatex.)


I remain mystified why this problem didn't bite us with older TeXLive 
distributions (or why it suddenly surfaced with the 2016 version).


Thanks for the help!

   Mike Maxwell


--
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[Herbert Schulz]

> On Jun 15, 2016, at 6:13 PM, David Carlisle  wrote:
> 
> On 16 June 2016 at 00:08, Herb Schulz  wrote:
>> Howdy,
>> 
>> Again, sorry for the top post.
>> 
>> Does
>> 
>> kpsewhich hyperref.cfg
>> 
>> really return a file in the .../doc/... branch?
>> 
> 
> Oh of course! well spotted.
> 
> So that is the error.
> 
> The file is correctly installed in the doc branch but the OP's
> $TEXINPUTS is incorrectly including the
> /groups/tools/texlive/2016/texmf-dist/doc tree and worse searching it
> before the /groups/tools/texlive/2016/texmf-dist/tex tree.
> 
> 
> David

Howdy,

My $TEXINPUTS, obtained via

$ kpsewhich -var-value=TEXINPUTS

is

.:{[items in my HOME directory],[items in other texmf 
trees],!!/usr/local/texlive/2016/texmf-dist}/tex/{kpsewhich,generic,}//

so I don't know why kpsewhich would look in the .../doc/... branch of 
texmf-dist (unless that last kpsewhich is returning a ../doc/...).

Good Luck,

Herb Schulz
(herbs at wideopenwest dot com)









--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[Ross Moore]

On Jun 16, 2016, at 9:45 AM, David Carlisle 
> wrote:

The result is that when you subsequently request   [dvipdfmx]  or  any other 
driver,
hyperref thinks that we are in non-dvi mode, so  *incorrectly* throws the error.

So it’s surely an omission in  hyperref.sty .

But you don’t actually need to specify a driver option,
and everything works OK anyway.

It only works with no option if you are not using a hyperref.cfg that specifies 
incompatible options:-)

OK. So [xetex] is the correct option to use, if any is needed.
Besides, the actual driver binary is   xdvipdfmx   not  dvipdfmx .




  Mike Maxwell

David


Cheers,

Ross


Dr Ross Moore

Mathematics Dept | Level 2, S2.638 AHH
Macquarie University, NSW 2109, Australia

T: +61 2 9850 8955  |  F: +61 2 9850 8114
M:+61 407 288 255  |  E: 
ross.mo...@mq.edu.au

http://www.maths.mq.edu.au


[cid:image001.png@01D030BE.D37A46F0]


CRICOS Provider Number 2J. Think before you print.
Please consider the environment before printing this email.

This message is intended for the addressee named and may
contain confidential information. If you are not the intended
recipient, please delete it and notify the sender. Views expressed
in this message are those of the individual sender, and are not
necessarily the views of Macquarie University.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[David Carlisle]

On 16 June 2016 at 00:25, Ross Moore  wrote:

> Hi Mike, David, Herb,
>
> I’m seeing the same behaviour, but for me the packages are as follows:
>
> (/usr/local/texlive/2016/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
>
> /usr/local/texlive/2016/texmf-dist/tex/latex/hyperref/hyperref.sty:4322:
> Packag
> e hyperref Error: Wrong DVI mode driver option `dvipdfmx',
> (hyperref)because XeTeX is running.
>
>
>
>


Yes that's with the file with an explicit [dvipdfmx] option, as far as I
can see
hyperref has always (or at least for some years) given that error on xetex
it insists on xetex option (which would be the default if the correct cfg
is loaded)


>
> Here is the relevant coding from  hyperref.sty  with annotations added by
> me.
>
> \newif\ifHy@DviMode
>
> This defines  \ifHy@DviMode and switches, leaves it as  \iffalse
>
> \let\Hy@DviErrMsg\ltx@empty
> \ifpdf
>   \def\Hy@DviErrMsg{pdfTeX or LuaTeX is running in PDF mode}%
> \else
>   \ifxetex
>
> This is already  \iftrue
>
> \def\Hy@DviErrMsg{XeTeX is running}%
>
> … but surely we should be setting  \Hy@DviModetrue  here !!!
>



Hmm perhaps...
 although the end result is that it just turns the error into a warning and
ignores the specified option so you'd get

Package hyperref Warning: Wrong driver `hdvipdfm.def';
(hyperref)XeTeX is running.
(hyperref)Forcing driver `hxetex.def' for XeTeX.

probably giving an error and making the user fix the document is as clear,
and certainly what it's always done.


>   \else
> \ifvtex
>   \ifvtexdvi
> \Hy@DviModetrue
>   \else
> \def\Hy@DviErrMsg{VTeX is running, but not in DVI mode}%
>   \fi
> \else
>   \Hy@DviModetrue
> \fi
>   \fi
> \fi
>
>
> The result is that when you subsequently request   [dvipdfmx]  or  any
> other driver,
> hyperref thinks that we are in non-dvi mode, so  *incorrectly* throws the
> error.
>
> So it’s surely an omission in  hyperref.sty .
>
> But you don’t actually need to specify a driver option,
> and everything works OK anyway.
>

It only works with no option if you are not using a hyperref.cfg that
specifies incompatible options:-)


>
>
>   Mike Maxwell
>
>
>
> Hope this helps,
>
> Ross
>
>
>
David


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[Ross Moore]

Hi Mike, David, Herb,

On Jun 16, 2016, at 8:46 AM, maxwell 
> wrote:

With the help of David Carlisle and Herbert Schulz, I've found part of the 
problem.  For some reason, in the (our?) 2016 version, kpsewhich points to this 
hyperref.cfg file:
  ...texlive/2016/texmf-dist/doc/latex/listings-ext/hyperref.cfg

I’m seeing the same behaviour, but for me the packages are as follows:

(/usr/local/texlive/2016/texmf-dist/tex/latex/latexconfig/hyperref.cfg)

/usr/local/texlive/2016/texmf-dist/tex/latex/hyperref/hyperref.sty:4322: Packag
e hyperref Error: Wrong DVI mode driver option `dvipdfmx',
(hyperref)because XeTeX is running.




This .cfg file contains a \hypersetup{...} command that specifies 'ps2pdf'.  
Changing that to 'xetex' fixes the problem, at least for xelatex (I'm not sure 
what would happen with other flavors of latex).  (Update: removing the line 
entirely, so it specifies neither xetex nor ps2pdf, works too, and presumably 
won't cause trouble for other latices.)

But:
1) Why does kpsewhich find that file, instead of this one:
  ...texlive/2016/texmf-dist/tex/latex/latexconfig/hyperref.cfg
  which does not have any \hypersetup{} command, and which would
  presumably not cause the same problem?
2) Why did this change from 2015 to 2016?  We did a pretty vanilla
  install, I think the only non-default choice we made was to use
  'letter' instead of 'a4'.
3) Is this a bug? (meaning should I report it?)

Here is the relevant coding from  hyperref.sty  with annotations added by me.

\newif\ifHy@DviMode
This defines  \ifHy@DviMode and switches, leaves it as  \iffalse
\let\Hy@DviErrMsg\ltx@empty
\ifpdf
  \def\Hy@DviErrMsg{pdfTeX or LuaTeX is running in PDF mode}%
\else
  \ifxetex
This is already  \iftrue
\def\Hy@DviErrMsg{XeTeX is running}%
… but surely we should be setting  \Hy@DviModetrue  here !!!
  \else
\ifvtex
  \ifvtexdvi
\Hy@DviModetrue
  \else
\def\Hy@DviErrMsg{VTeX is running, but not in DVI mode}%
  \fi
\else
  \Hy@DviModetrue
\fi
  \fi
\fi

The result is that when you subsequently request   [dvipdfmx]  or  any other 
driver,
hyperref thinks that we are in non-dvi mode, so  *incorrectly* throws the error.

So it’s surely an omission in  hyperref.sty .

But you don’t actually need to specify a driver option,
and everything works OK anyway.


  Mike Maxwell


Hope this helps,

Ross


Dr Ross Moore

Mathematics Dept | Level 2, S2.638 AHH
Macquarie University, NSW 2109, Australia

T: +61 2 9850 8955  |  F: +61 2 9850 8114
M:+61 407 288 255  |  E: 
ross.mo...@mq.edu.au

http://www.maths.mq.edu.au


[cid:image001.png@01D030BE.D37A46F0]


CRICOS Provider Number 2J. Think before you print.
Please consider the environment before printing this email.

This message is intended for the addressee named and may
contain confidential information. If you are not the intended
recipient, please delete it and notify the sender. Views expressed
in this message are those of the individual sender, and are not
necessarily the views of Macquarie University.



--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[David Carlisle]

On 16 June 2016 at 00:08, Herb Schulz  wrote:
> Howdy,
>
> Again, sorry for the top post.
>
> Does
>
> kpsewhich hyperref.cfg
>
> really return a file in the .../doc/... branch?
>

Oh of course! well spotted.

So that is the error.

The file is correctly installed in the doc branch but the OP's
$TEXINPUTS is incorrectly including the
/groups/tools/texlive/2016/texmf-dist/doc tree and worse searching it
before the /groups/tools/texlive/2016/texmf-dist/tex tree.


David


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[David Carlisle]

On 15 June 2016 at 23:46, maxwell  wrote:
> With the help of David Carlisle and Herbert Schulz, I've found part of the
> problem.  For some reason, in the (our?) 2016 version, kpsewhich points to
> this hyperref.cfg file:
>...texlive/2016/texmf-dist/doc/latex/listings-ext/hyperref.cfg

looking at the listings-ext distribution on ctan that is intended to
be a local configuration for producing the package documentation, it
is not intended to be in the general tex input path (and is not in the
input path of my texlive 2015 or 2016 installations which have only
listings-ext.sty in the latex/listings-ext directory.


> This .cfg file contains a \hypersetup{...} command that specifies 'ps2pdf'.
> Changing that to 'xetex' fixes the problem, at least for xelatex (I'm not
> sure what would happen with other flavors of latex).  (Update: removing the
> line entirely, so it specifies neither xetex nor ps2pdf, works too, and
> presumably won't cause trouble for other latices.)

I think you should remove the file.

>
> But:
> 1) Why does kpsewhich find that file, instead of this one:
>...texlive/2016/texmf-dist/tex/latex/latexconfig/hyperref.cfg
>which does not have any \hypersetup{} command, and which would
>presumably not cause the same problem?

it finds it because it is there:-) if you have two files of the same
name in the same input tree then kpsearch will find one of them but
it's not a very stable setup.

> 2) Why did this change from 2015 to 2016?  We did a pretty vanilla
>install, I think the only non-default choice we made was to use
>'letter' instead of 'a4'.

I'm not sure. How come the listings-ext hyperref config got installed
on your system
It isn't in the texlive install I have (which installs everything,
including listings-ext)
it installs into the doc tree and is just used for the listings-ext package doc

/usr/local/texlive/2016/texmf-dist/doc/latex/listings-ext/hyperref.cfg



> 3) Is this a bug? (meaning should I report it?)

If texlive installed that cfg file then that would seem to be a bug in
tlmgr, but I can't reproduce it here.

>
>Mike Maxwell


David


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[maxwell]

With the help of David Carlisle and Herbert Schulz, I've found part of 
the problem.  For some reason, in the (our?) 2016 version, kpsewhich 
points to this hyperref.cfg file:

   ...texlive/2016/texmf-dist/doc/latex/listings-ext/hyperref.cfg
This .cfg file contains a \hypersetup{...} command that specifies 
'ps2pdf'.  Changing that to 'xetex' fixes the problem, at least for 
xelatex (I'm not sure what would happen with other flavors of latex).  
(Update: removing the line entirely, so it specifies neither xetex nor 
ps2pdf, works too, and presumably won't cause trouble for other 
latices.)


But:
1) Why does kpsewhich find that file, instead of this one:
   ...texlive/2016/texmf-dist/tex/latex/latexconfig/hyperref.cfg
   which does not have any \hypersetup{} command, and which would
   presumably not cause the same problem?
2) Why did this change from 2015 to 2016?  We did a pretty vanilla
   install, I think the only non-default choice we made was to use
   'letter' instead of 'a4'.
3) Is this a bug? (meaning should I report it?)

   Mike Maxwell


--
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[Juan Acevedo]

In case it helps:
I ran into a similar problem the first time I compiled a file with TL 2016.
Just before I started moaning (well, almost), I thought of erasing all the 
auxiliary files of the document.
I did so, compiled again and no problem since. 

I must add that I had run updmap straight after the installation, though I am 
not sure that has anything to do.

Good luck,
Juan


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[Herbert Schulz]

Howdy,

A perfect reason to suspect a file is interfering with operations. 

Good Luck,
Herb Schulz


> On Jun 15, 2016, at 4:50 PM, maxwell  wrote:
> 
>> On 2016-06-15 17:36, David Carlisle wrote:
>> I get the same error with texlive 2015 so I don't think there is any
>> recent change (since support for hyperref moved to github) that has
>> changed this, with texlive 2015:
>> (/usr/local/texlive/2015/texmf-dist/tex/latex/hyperref/pd1enc.def)
>> (/usr/local/texlive/2015/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
>> ! Package hyperref Error: Wrong DVI mode driver option `dvipdfmx',
>> (hyperref)because XeTeX is running.
> 
> Mysteriouser and mysteriouser.  2015 worked fine for us, it was only when we 
> updated to 2016 that we encountered a problem.
> 
> But surely there are lots of people out there happily using xelatex and 
> hyperref without any problem, right?  Why is this only showing up now?
> 
>   Mike Maxwell
> 
> 
> 
> --
> Subscriptions, Archive, and List information, etc.:
> http://tug.org/mailman/listinfo/xetex




--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[maxwell]

On 2016-06-15 17:55, David Carlisle wrote:
But surely there are lots of people out there happily using xelatex 
and hyperref without any problem, right?


yes but most will use no driver option or specify xetex which works,
the explicit dvipdfm option doesn't but I'm not sure when that
stopped.


We had previously been using the [xetex] option, but that has stopped 
working as well--i.e. I just tried my file with

\usepackage[xetex]{hyperref}
and it fails with the same error msg as no parameter, or as with 
[dvipdfmx].



this year we moved support to github and made some emergency
updates for luatex changes but as far as I can see nothing's changed
in the xetex code path for hyperref.


Right, an hour ago I did a diff between the 2015 and 2016 copies of 
hyperref.sty, and came up with only a couple diffs, which looked 
innocent to my inexperienced eye totally.  But since then, at Herbert 
Schultz's off-line suggestion, I did a "tlmgr --update", and now I get 
quite a few other diffs (looks like some of them were to accommodate 
Italian section names, but there are a few other diffs).  The error msg 
remains.



Why is this only showing up now?


No idea, can you send me the full log off list and I'll see if I can 
debug


Will do, thanks!

   Mike Maxwell



--
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[maxwell]

On 2016-06-15 17:36, David Carlisle wrote:

I get the same error with texlive 2015 so I don't think there is any
recent change (since support for hyperref moved to github) that has
changed this, with texlive 2015:

(/usr/local/texlive/2015/texmf-dist/tex/latex/hyperref/pd1enc.def)
(/usr/local/texlive/2015/texmf-dist/tex/latex/latexconfig/hyperref.cfg)

! Package hyperref Error: Wrong DVI mode driver option `dvipdfmx',
(hyperref)because XeTeX is running.


Mysteriouser and mysteriouser.  2015 worked fine for us, it was only 
when we updated to 2016 that we encountered a problem.


But surely there are lots of people out there happily using xelatex and 
hyperref without any problem, right?  Why is this only showing up now?


   Mike Maxwell



--
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[David Carlisle]

I get the same error with texlive 2015 so I don't think there is any
recent change (since support for hyperref moved to github) that has
changed this, with texlive 2015:

(/usr/local/texlive/2015/texmf-dist/tex/latex/hyperref/pd1enc.def)
(/usr/local/texlive/2015/texmf-dist/tex/latex/latexconfig/hyperref.cfg)

! Package hyperref Error: Wrong DVI mode driver option `dvipdfmx',
(hyperref)because XeTeX is running.

David


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex

Re: [XeTeX] xelatex, hyperref, and new TeXLive

[David Carlisle]

On 15 June 2016 at 21:56, maxwell  wrote:
> We've downloaded and installed the new 2016 TeXLive distribution.  I was all
> set to be happy...but.  There seems to be an incompatibility between the new
> xelatex and the new hyperref package.  No matter what I do, I get the error
> msg:
> 
> ! Package hyperref Error: Wrong DVI mode driver option `ps2pdf',
> (hyperref)because XeTeX is running.
> 
>
> We did not of course get this error with the TeXLive 2015 distribution.
>
> Here's the minimal file to trigger this error (ok, I could take out the word
> "test", but it's pretty minimal :-)):
> 
> \documentclass{article}
> \usepackage[dvipdfmx]{hyperref}
> \begin{document}
> test
> \end{document}
> 
>
> I've tried telling hyperref
>[driverfallback=dvipdfm]
> instead, and I've tried telling xelatex
> --output-driver=xdvipdfmx
> and a bunch of other things, with no effect.
>
> What do I yet lack?
>
>Mike Maxwell
>University of Maryland



odd: I didn't think anything had changed here, I'll test with tl2015
later, meanwhile your test file works for me with with texlive 2016
xelatex and

\usepackage{hyperref}

or equivalently with


\usepackage[xetex]{hyperref}


David

>
>
>
> --
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex



-- 
http://dpcarlisle.blogspot.com/


--
Subscriptions, Archive, and List information, etc.:
  http://tug.org/mailman/listinfo/xetex