Is there a graphite-info.tex to find out what the feature names are in a
Graphite font?
I've haven't been able to find it and it would be useful. Or, is there
some other way to display all the Graphite features in a font.
My actual problem is that I have a font where the feature name is "Long
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 dr
Howdy,
Sorry for the top post.
Try \usepackage{hyperref} without the option. The hyperref package detects use
of XeTeX and therefore the xdvipdfmx back end.
Good Luck,
Herb Schulz
> On Jun 15, 2016, at 3:56 PM, maxwell wrote:
>
> We've downloaded and installed the new 2016 TeXLive distribu
On 2016-06-15 17:03, Herb Schulz wrote:
Try \usepackage{hyperref} without the option. The hyperref package
detects use of XeTeX and therefore the xdvipdfmx back end.
Thanks, but that's what I tried first, and it gives the same error. I
thought maybe explicitly telling it that I was using the
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:
>
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/hyp
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/texl
> 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. this year we moved support to github and ma
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.
To be sure, I have just reprocessed my old document after the fresh update
of TL 2016. I ise hyperref without the driver option and it works.
Zdeněk Wagner
http://ttsm.icpf.cas.cz/team/wagner.shtml
http://icebearsoft.euweb.cz
2016-06-15 23:55 GMT+02:00 David Carlisle :
> > But surely there are l
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 suppo
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
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
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
Howdy,
Again, sorry for the top post.
Does
kpsewhich hyperref.cfg
really return a file in the .../doc/... branch?
Good Luck,
Herb Schulz
> On Jun 15, 2016, at 5:56 PM, David Carlisle wrote:
>
>> On 15 June 2016 at 23:46, maxwell wrote:
>> With the help of David Carlisle and Herbert Schulz
Lorna,
are you using version 2.8 of Padauk?
If so the feature id is "ulon"
Andrew
On 16 June 2016 at 05:38, Lorna Evans wrote:
> Is there a graphite-info.tex to find out what the feature names are in a
> Graphite font?
>
> I've haven't been able to find it and it would be useful. Or, is there
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
$TE
Hi Mike, David, Herb,
On Jun 16, 2016, at 8:46 AM, maxwell
mailto:maxw...@umiacs.umd.edu>> 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/texm
On 15/6/16 20:38, Lorna Evans wrote:
Is there a graphite-info.tex to find out what the feature names are in a
Graphite font?
I've haven't been able to find it and it would be useful. Or, is there
some other way to display all the Graphite features in a font.
If I remember aright, the graphite
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:
>
On Jun 16, 2016, at 9:45 AM, David Carlisle
mailto:d.p.carli...@gmail.com>> 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 .
Thank you both. I learned something today!
On Jun 15, 2016 6:34 PM, "Jonathan Kew" wrote:
> On 15/6/16 20:38, Lorna Evans wrote:
>
>> Is there a graphite-info.tex to find out what the feature names are in a
>> Graphite font?
>>
>> I've haven't been able to find it and it would be useful. Or, is t
22 matches
Mail list logo