Latest news 2021-06-05: New blog post: Dickimaw Books Site Account.

# Bug Tracker

ID 92🔗 2015-07-31 08:52:24 Closed (Can Not Implement) glossaries 4.17 To early usage of \hsize

## Description

Several glossaries styles use \hsize to set length before \begin{document} but the official setup of \hsize is in \begin{document} after calculation of \columnwidth in \begin{document}. This results in wrong lengths if e.g. geometry.sty or typearea.sty is used. Sometimes the value is almost correct, so it doesn't matter, but e.g. using a6paper with geometry results in completely unusable lists.

A workaround but be to use \AtBeginDocument for the lengths settings, e.g.

\AtBeginDocument{\setlength{\glslistdottedwidth}{.5\columnwidth}}

## MWE

\listfiles
\documentclass{article}
\usepackage[a6paper]{geometry}
\usepackage[acronym, style=listdotted, toc]{glossaries}
\makeglossaries

\newacronym{SOEP}{SOEP}{Sozio-Oekonomisches Panel}
%\AtBeginDocument{\setlength{\glslistdottedwidth}{.5\columnwidth}}
\begin{document}
\printacronyms

\section{Test}
\gls{SOEP}
\end{document}


## Evaluation

Unfortunately changing the current code to use \AtBeginDocument could break existing documents that change the length in the preamble. I'll leave this open for now, but I think it's better to just consider .5\hsize as a default value that may need changing depending on the document.

Update: I've closed this as "Can not Implement" because I can't implement it in glossaries (for the above reason), but it's addressed in glossaries-extra.

🔗Comment from Markus
Date: 2015-08-01 06:42:47

You could additionally (to documentation of the problem) put

\if@twocolumn
\hsize=\dimexpr .5\textwidth-\columnsepwidth\relax
\else
\hsize=\textwidth}
\fi
before your first usage of \hsize. This shouldn't break anything, but would at least do it as long as the user does not change geometry e.g. using \geometry or \typearea or another \setlength{\textwidth}{…} after loading glossaries. So this would not be a real fix of the problem but it would decrease the probability of the event.

You could do something like:

\setlength{\glslistdottedwidth}{-\dimexpr\maxdimen-1sp\relax}
\AtBeginDocument{\ifdim\glslistdottedwidth=-\dimexpr\maxdimen-1sp\relax
\setlength{\glslistdottedwidth}{.5\columnwidth}\fi}
In real live values < 0 of \glslistdottedwidth mostly make no sense. So a very special value < 0 could be used as a marker value. Nevertheless, this would change documents, iff the user has not recognized, that the default has not been the intended choice. So maybe the other suggestion would be better.

PS: Many thanks for glossaries. It is a very useful package!

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.

🔗Comment from Nicola Talbot 🦜
Date: 2015-12-09 20:51:00

I've implemented your suggestion into glossaries-extra.sty. Since this extension to the glossaries package changes the defaults, backward-compatibility isn't an issue, so it seems the best solution. I'll close this after I upload glossaries-extra.sty to CTAN (once it has stabilized).

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.

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.