Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1796550 - Cannot use newtxtext with footnotes
Summary: Cannot use newtxtext with footnotes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: texlive
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-30 17:00 UTC by maxwellsdemon137
Modified: 2020-03-19 19:28 UTC (History)
4 users (show)

Fixed In Version: texlive-2019-19.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-19 19:28:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Minimal example (100 bytes, text/x-tex)
2020-01-30 17:00 UTC, maxwellsdemon137
no flags Details
tex file of article (87.99 KB, text/x-tex)
2020-03-19 18:39 UTC, jonathan baron
no flags Details

Description maxwellsdemon137 2020-01-30 17:00:57 UTC
Created attachment 1656539 [details]
Minimal example

Description of problem:
Using the newtxtext package in a document that contains a footnote prevents the document from successfully compiling.


Version-Release number of selected component (if applicable):
2019-15.fc31


How reproducible:
Always.


Steps to Reproduce:
- One method:
1. Download the attached minimal example (example.tex)
2. Run either pdflatex example.tex or latexmk --pdf example.tex in a terminal

- Second method
1. Download the attached minimal example (example.tex)
2. Run latex example.tex [successfully creates example.dvi]
3. Run dvips example.dvi


Actual results:
- First method:
!pdfTeX error: pdflatex (file ntxsups_t1.enc): cannot open encoding file for reading

- Second method
dvips: ! Couldn't find header file: ntxsups_t1.enc


Expected results:
A pdf or ps file should be produced without errors.


Additional info:
I successfully compiled documents using the newtxtext package and containing footnotes on Fedora 29 as recently as December 9. I'm afraid I don't have anything more specific.

Comment 1 jonathan baron 2020-02-23 00:34:01 UTC
I have a similar problem with Fedora 31. The error message is

baron@barber ~/jdm/19/190109a > dvipdf jdm190109a.dvi 
dvips: ! Couldn't find header file: ntxsups_t1.enc

The result is a blank pdf file.

The problem seems to be in newtxtext or newtxmath, probably the first.

If I replace

\usepackage{newtxtext,newtxmath} 

with

\usepackage{txfonts} 

it works, although txfonts does not handle some of the characters. (I just changed them to the old version.)

I have an old computer that that still has an older version of texlive on it. If it helps I could try
to see where ntxsups_t1.enc is on that, but it is a pain to connect to because it won't connect to the internet
and does not have a monitor. Let me know.

I don't think it is just about footnotes, although I do have them in this file.

Comment 2 maxwellsdemon137 2020-02-23 20:17:06 UTC
I don't think the problem is with upstream versions of these packages or texlive, but with with how Fedora is packaging them. I've resolved the problem completely by downloading texlive directly from tug.org, doing a local install for my user only, and giving the user-level install directory greater priority in the PATH variable. With that, the minimal example (and my actual papers) compile fine with no errors and everything rendered correctly.

Comment 3 jonathan baron 2020-03-01 17:00:24 UTC
(In reply to jonathan baron from comment #1)
> I have a similar problem with Fedora 31. The error message is
> 
> baron@barber ~/jdm/19/190109a > dvipdf jdm190109a.dvi 
> dvips: ! Couldn't find header file: ntxsups_t1.enc

I now think that the problem is somewhere else, possibly ghostscript. Either that or something has changed as a result of updating other packages.

I no longer see the problem in most files that I have. newtxtext works fine, and I do not need txfonts.

When the problem occurs now, it seems to be in graphics made by someone else. (I edit and produce a journal, so I get lots of graphics from other people in EPS format.) The problem occurs in ps2pdf apply to the graphic alone.

But most graphics work. I've asked the author for a new version of the figure. I now think that I cannot help with this bug report.
 
> The result is a blank pdf file.
> 
> The problem seems to be in newtxtext or newtxmath, probably the first.
> 
> If I replace
> 
> \usepackage{newtxtext,newtxmath} 
> 
> with
> 
> \usepackage{txfonts} 
> 
> it works, although txfonts does not handle some of the characters. (I just
> changed them to the old version.)
> 
> I have an old computer that that still has an older version of texlive on
> it. If it helps I could try
> to see where ntxsups_t1.enc is on that, but it is a pain to connect to
> because it won't connect to the internet
> and does not have a monitor. Let me know.
> 
> I don't think it is just about footnotes, although I do have them in this
> file.

Comment 4 Tom "spot" Callaway 2020-03-05 19:51:12 UTC
I think I know what this issue is. There was a naming mismatch in the CTAN tarball for newtx, it is fixed in the newer version. I will push an update to Fedora 31 that should resolve this.

Comment 5 Fedora Update System 2020-03-16 14:53:43 UTC
texlive-2019-19.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-726bbfad03

Comment 6 Fedora Update System 2020-03-18 02:22:27 UTC
texlive-2019-19.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 jonathan baron 2020-03-19 16:35:53 UTC
Problems still persist. I got exactly what was initially reported, no numbers in the footnotes. I also get a bunch of the following error messages when running dvipdf. (These are just examples. There are more.)

Warning: module writet1 of dvips (file ntxsups-Regular.pfb): glyph `nine' undefined

Warning: module writet1 of dvips (file ntxsups-Regular.pfb): glyph `eight' undefined

Warning: module writet1 of dvips (file ntxsups-Regular.pfb): glyph `seven' undefined

Warning: module writet1 of dvips (file ntxsups-Regular.pfb): glyph `six' undefined

The version of newtx I was using was texlive-newtx-9:svn 53549-19

I then downgraded to texlive-newtx-8:svn47889-27.fc31.noarch                                         1/2 

And now everything works as it should.

Comment 8 Tom "spot" Callaway 2020-03-19 18:16:28 UTC
Okay. Can you please provide me a simple reproducer case?

Comment 9 jonathan baron 2020-03-19 18:39:31 UTC
Created attachment 1671556 [details]
tex file of article

Comment 10 jonathan baron 2020-03-19 18:41:12 UTC
My comment got lost.

I don't know what you mean by "simple". I commented out the figures. This is real. And it works for any one of the 12 articles in the March issue (except one, the shortest, which has no footnotes).

Comment 11 Tom "spot" Callaway 2020-03-19 19:14:31 UTC
I believe your concern is real, I just need to be able to reproduce it locally so that I can debug the issue and attempt to identify a fix. Thank you for your tex file.

Please try this (after updating texlive-newtx)

sudo updmap-sys --syncwithtrees --force
sudo updmap-sys

If you are still getting errors with pdflatex, please let me know. After updating the fontmaps (and installing hevea), I was able to run pdflatex jdm181221.tex without error.

Comment 12 jonathan baron 2020-03-19 19:27:46 UTC
This works! Thanks. It is all fixed now.

I had tried updmap-sys before, but not with --syncwithtrees --force

I'm sorry about hevea. I should have deleted those lines too. (I'm in a rush to get the journal done. I produce it myself.)

Comment 13 Tom "spot" Callaway 2020-03-19 19:28:47 UTC
No worries friend, I'm glad this got it working for you.


Note You need to log in before you can comment on or make changes to this bug.