Latest news 2024-03-02: Ebook sale (3rd–9th March 2024): short story cybercrime fiction Unsocial Media free; short story noir crime fiction I’ve Heard the Mermaid Sing free; crime fiction novel The Private Enemy US$1.99; illustrated children’s story The Foolish Hedgehog US$0.99. For further details, see latest blog post.

Bug Tracker RSS feed

I’m currently working on a major new version of the datatool package. This may take a while. Please be patient. (Experimental version available for testing.)

ID 16🔗
Date: 2013-01-13 02:22:36
Status Closed (Fixed)
Category glossaries
Version 3.04
Summary \pagenumbering causes an error in \printglossaries

Sign in to subscribe to notifications about this report.

Description

Hello Nicola,

since one of the last MiKTeX updates \printglossaries causes an error, when \pagenumbering{Roman} is used before.

Best regards, Stefan

MWE

Download (556B)

% ----- minimal example -----
\documentclass{scrbook}
    \usepackage[
            acronym,
            nolong,nolist,notree,
            style=super,
                ]{glossaries}
    \newacronym[
        description={dummy text (\emph{dummy:} \protect\acrshort{test})},
            ]{dummy}{dummy}{just a dummy}
    \newacronym{test}{test}{just a test}
        \makeglossaries
\begin{document}
    \gls{dummy}
\pagenumbering{Roman}   % <-- comment me and it will work
    \printglossaries
\end{document}
% ---------------------------

Evaluation

This is now fixed in version 3.05.

Comments

1 comment.

🔗Comment from Uwe Müller
Date: 2013-01-26 09:47:33

Hello Nicola,

I have the same problem as Stefan. I changed the pagenumbering to "litte" roman numbers and it works. There seems to be a problem, when using "big" roman numbers.

I posted my problem to a german LaTeX-forum and got a short analysis from Rainer. It is the second posting in the thread at http://www.mrunix.de/forums/showthread.php?t=74623. Maybe this will help you to solve the problem.

Regards,
Uwe

Replying to Comment #7:

Name (optional):

Are you human? Please confirm the bug report ID (which can be found at the top of this page) or login if you have an account.

Comment:


You can use the following markup:

Block:

[pre]Displayed verbatim[/pre]
[quote]block quote[/quote]

In line:

[tt]code[/tt]
[file]file/package/class name[/file]
[em]emphasized text[/em]
[b]bold text[/b]
[url]web address[/url] [sup]superscript[/sup]
[sub]subscript[/sub]

Ordered list:
[ol]
[li]first item[/li]
[li]second item[/li]
[/ol]

Unordered list:
[ul]
[li]first item[/li]
[li]second item[/li]
[/ul]

You can use the Preview button to review your message formatting before submitting.


Add Comment

Name (optional):

Are you human? Please confirm the bug report ID (which can be found at the top of this page) or login if you have an account.

Comment:


You can use the following markup:

Block:

[pre]Displayed verbatim[/pre]
[quote]block quote[/quote]

In line:

[tt]code[/tt]
[file]file/package/class name[/file]
[em]emphasized text[/em]
[b]bold text[/b]
[url]web address[/url] [sup]superscript[/sup]
[sub]subscript[/sub]

Ordered list:
[ol]
[li]first item[/li]
[li]second item[/li]
[/ol]

Unordered list:
[ul]
[li]first item[/li]
[li]second item[/li]
[/ul]

You can use the Preview button to review your message formatting before submitting.

Page permalink: https://www.dickimaw-books.com/bugtracker.php?key=16