Bug 886158 - makeindex doesn't understand \index{"|-@$\vdash$}
Summary: makeindex doesn't understand \index{"|-@$\vdash$}
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: texlive
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Radek Vokál
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-11 16:16 UTC by Jerry James
Modified: 2018-05-29 12:05 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:05:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github https://github.com/ho-tex hyperref issues 24 0 None None None 2016-11-04 15:57:54 UTC

Description Jerry James 2012-12-11 16:16:11 UTC
Description of problem:
The pvs-sbcl user guide contains an instance of \index{"|-@$\vdash$}, to index the "entails" symbol in an order that makes sense to the PVS developers.  In Fedora 17 and earlier, this resulted in the following entry in user-guide.ind (the last entry in the section for symbols):

  \item $\vdash$, \hyperpage{52}

With TeXLive 2012 in Fedora 18 and Rawhide, this entry is generated instead:

  \item $\vdash$}, 52

The missing \hyperpage is annoying but not fatal.  The lone right curly brace, however, is fatal.  I'm hacking up the PVS user guide for now to work around this problem, but a fix would be greatly appreciated.

Version-Release number of selected component (if applicable):
texlive-makeindex-bin-2012-0.svn26509.10.20121205_r28449.fc19.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Get the pvs-sbcl package sources
2. cd doc/user-guide
3. pdflatex user-guide
4. makeindex -o user-guide.ind user-guide.idx
5. pdflatex user-guide
  
Actual results:
! Extra }, or forgotten \endgroup.
l.35   \item $\vdash$}
                      , 52
? 
! Emergency stop.
l.35   \item $\vdash$}
                      , 52
!  ==> Fatal error occurred, no output PDF file produced!

Expected results:
A correct index entry.

Additional info:

Comment 1 Jindrich Novy 2013-04-02 14:55:00 UTC
Could you please try again with:

https://admin.fedoraproject.org/updates/FEDORA-2013-4523/texlive-2012-20.20130321_r29448.fc18

?

In my case it outputs:
! LaTeX Error: File `sum-tccs.tex' not found.

This source doesn't seem to be a part of neither texlive nor pvs-sbcl

Comment 2 Fedora End Of Life 2013-04-03 15:21:36 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 4 Jerry James 2013-07-16 21:16:28 UTC
Sorry for ignoring this bug for so long.  Yes, the reproduction steps I gave are flawed, as the file sum-tccs.tex is generated during the PVS build.  Instead, put this into test.tex:

\documentclass{article}
\usepackage[bookmarks=true,hyperindex=true]{hyperref}

\makeindex
\begin{document}
This \index{document} has an \index{index}.

Let's try to place the entails \index{"|-@$\vdash$} symbol in the index.
\end{document}



Now run:
- pdflatex test
- makeindex test

And take a look in test.ind:

\begin{theindex}

  \item $\vdash$}, 1

  \indexspace

  \item document, \hyperpage{1}

  \indexspace

  \item index, \hyperpage{1}

\end{theindex}

As with the PVS document, the index for the entails sign is mangled, with a stray '}' and a missing '\hyperpage' around the page number.  This is on a freshly updated Rawhide machine with texlive-2013-0.2.20130608_r30832.fc20.x86_64.

Comment 5 Jerry James 2014-06-20 19:39:02 UTC
Reviving this once more...  After the initial run of pdflatex, I see this in user-guide.idx:

\indexentry{"|hyperindexformat{\-@$\vdash$}}{52}

where what I really want it to be is:

\indexentry{"|-@$\vdash$|hyperpage}{52}

Apparently hyperref decided that the dash just might possibly represent a page number range and wrapped it with hyperindexformat, which causes makeindex to generate the broken output described in comment 4.

This *almost* works:

\index{\nohyperpage{"|-@$\vdash$}}

Then we get this entry in user-guide.idx:

\indexentry{\nohyperpage{"|-@$\vdash$}|hyperpage}{52}

But, alas, makeindex gets confused somehow and emits an extra right curly brace, as before:

\item $\vdash$}, \hyperpage{52}

If *that* could be fixed, I'd have a solution to this problem.

Comment 7 Jan Kurik 2015-07-15 14:55:24 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 8 Jerry James 2016-07-15 14:51:11 UTC
This bug still exists in Rawhide, with texlive-2015-26.20150728_r37987.fc25.  Comment 4 and comment 5 both still apply.

Comment 9 Jan Kurik 2016-07-26 05:03:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 10 Jerry James 2016-11-04 14:44:46 UTC
This bug still exists in Rawhide, with texlive-2016-17.20160520.fc26.  Comment 4 and comment 5 both still apply.

Comment 11 Tom "spot" Callaway 2016-11-04 14:51:12 UTC
Wow. Speaking of bugs not even on my radar. :) I'll look into this.

Comment 12 Tom "spot" Callaway 2016-11-04 15:06:22 UTC
Upstream for hyperref appears to be here:

https://github.com/ho-tex/hyperref

I think you probably want to open this issue with them. Trying to debug hyperref is a bit above my skillset.

Comment 13 Jerry James 2016-11-04 15:38:01 UTC
Yeah, me too, or I would have tried to debug it years ago. :-)  Okay, I'll try to find some upstream or other that can figure out what is going on.

Comment 14 Fedora End Of Life 2017-02-28 09:32:55 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 15 Fedora End Of Life 2018-05-03 08:57:37 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 16 Fedora End Of Life 2018-05-29 12:05:50 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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