Bug Tracker

One or more errors has occurred:

Invalid search_category value

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	110🔗
Submitted by:	Nicola Talbot 🦜
Date:	2016-05-03 10:59:22
Status	Closed (Fixed)
Category	glossaries-extra
Version	1.04
Summary	postfootnote and long-em styles conflict

Description

The "long-em" styles introduced in v1.04 conflict with the "postfootnote" styles. The footnote can end up being emphasized by mistake.

This bug will be fixed in v1.05. The following patch can be used with v1.04:

\providecommand*{\glsfirstlongfootnotefont}[1]{\glslongfootnotefont{#1}}%
\providecommand*{\glslongfootnotefont}[1]{\glslongdefaultfont{#1}}%

\letabbreviationstyle{org-postfootnote}{short-postfootnote}
\renewabbreviationstyle{short-postfootnote}%
{%
  \GlsXtrUseAbbrStyleSetup{org-postfootnote}%
  \renewcommand*{\GlsXtrPostNewAbbreviation}{%
    \csdef{glsxtrpostlink\glscategorylabel}{%
      \glsxtrifwasfirstuse
      {%
        \glsxtrdopostpunc{\protect\footnote
        {\glsfirstlongfootnotefont{\glsentrylong{\glslabel}}}}%
      }%
      {}%
    }%
    \glshasattribute{\the\glslabeltok}{regular}%
    {%
      \glssetattribute{\the\glslabeltok}{regular}{false}%
    }%
    {}%
  }%
}%
{%
  \GlsXtrUseAbbrStyleFmts{org-postfootnote}%
}

MWE

Download (527B)

% arara: pdflatex
% arara: makeglossaries if found("aux", "@istfilename")
% arara: pdflatex if found ("log", "Rerun") || found("aux", "@istfilename")
\documentclass{article}

\usepackage{glossaries-extra}

\makeglossaries

\setabbreviationstyle[acronym]{short-postfootnote}
\newacronym{sample2}{short2}{long2}

\setabbreviationstyle{long-em-short-em}
\newabbreviation{sample1}{short1}{long1}


\begin{document}
First use: \gls{sample2}, \gls{sample1}.

Next use: \gls{sample2}, \gls{sample1}.

\printglossaries

\end{document}

Evaluation

Now fixed in v1.05.

Comments

0 comments.

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.

Confirm ID:

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=110