Tag Info

Hot answers tagged

4

You get messages saying something like pdfTeX warning (ext4): destination with the same identifier (name{chapter.4 }) has been already used, duplicate ignored which shouldn't be ignored. They are caused by having chapters with the same number. You can solve it by adding \renewcommand\theHchapter{\thechapter} after doing ...


4

Here's the simple method using longtable: \documentclass{book} \usepackage{siunitx} \usepackage{booktabs} \usepackage{longtable} \begin{document} \chapter{System of Units etc} \section{International system of units} \begin{longtable}{llll} \toprule \bfseries Quantity & \bfseries Unit & \bfseries Symbol & \bfseries ...


4

I couldn't replicate the spacing issue around the SG, so this answer might not help you with that. The go.PSTpastpst issue is related to the usage of the obsolete glossaries commands \defglsdisplay and \defglsdisplayfirst in leipzig.sty. Here is what is in v1.0 of leipzig.sty: \newcommand*{\SetLeipzigDisplayStyle}[1]{% ...


3

The insertion of the glossaries and other lists cause the page numbers to change so you need to do: pdflatex makeglossaries pdflatex makeglossaries pdflatex to get them up-to-date. The first makeglossaries generates the glossaries but uses the page numbers from the first LaTeX run, so you need another LaTeX run to update the page numbers, then rerun ...


3

The displaying of glossaries is controlled by the styles. Then you need declare a new style or edit the macros that used into the styles. The defualt style is list and the part that print the entries in the glossaries is the \glossentry macro. The list style definition declares the \glossentry macro as (p. 251, glossaries-code.pdf): ...


2

The standard column specifiers are l, r, c and p{length}. You can define new column types using the array package, but I don't think that's needed in this case as you can adjust the paragraph alignment using \raggedleft. When defining a new glossary style, it helps to consider a simplified version of what that style does. At it's basic level, the style needs ...


2

The nomain package option suppresses the creation of the main (default) glossary. This means that there's only one glossary (the acronym glossary) which becomes the new default glossary, so \glsdefaulttype and \acronymtype expand to the same glossary label. Since \printglossary is equivalent to \printglossary[type=\glsdefaulttype] this means that ...


1

\newacronym has an optional argument that allows you to provide additional keys, which are internally passed to \newglossaryentry, so you can just do: \newacronym[parent=definition]{uv}{UV}{Ultraviolet}


1

Had the same problem. I resolved it by declaring the acronyms in the head instead within the document environment. See: section "Drawbacks With Defining Entries in the Document Environment" of the user manual



Only top voted, non community-wiki answers of a minimum length are eligible