kberry

Results 39 issues of kberry

(import from https://puszcza.gnu.org.ua/bugs/?272) or Mupdf, so there are to my knowledge no PDF viewers left in Linux, which could work on them. Fortunately, the word processor of Libreoffice 5.1.0 seems...

(reposted from https://puszcza.gnu.org.ua/bugs/index.php?193, author Kristian Debrabant ) I recently discovered the following strange behaviour when hyperref is combined with an ams class: The following code: %%%%%%%%%%%%%%%%%%%%%%%%%%%%% \documentclass{amsart} \usepackage{hyperref} \newtheorem{example}{Example} \begin{document}...

Wishlist: no idea if it's feasible, but it would be nice if hyperref supported \url|...|, since the original url.sty does. Right now it takes the first | as the argument,...

Evidently lualatex.fmt cannot be shared between 32-bit and 64-bit systems. All other fmts, including xelatex.fmt, pdflatex.fmt, and the plain luahbtex.fmt, are sharable. Of course the fmts are created by the...

stale

When typesetting an accented character that does not exist in the current font: ``` \documentclass{article} \begin{document} \nullfont \^e \end{document} ``` LaTeX reports: ``` Missing character: There is no e (U+0065)...

enhancement / extension
category base (latex)
to analyse further
long-term

Without \askforoverwritefalse, docstrip asks about overwriting even when nothing will get overwritten: ``` \input docstrip.tex \generate{% \file{story.tex}{\from{try.dtx}{foo}}% } ``` gives: ``` File story.tex already exists somewhere on the system. Overwrite...

enhancement
category base (latex)
long-term

In the warning ``` Package biblatex Warning: Using fall-back BibTeX(8) backend: ``` Is the (8) a Unix man page reference? Sorry, I can't imagine what else it would refer to....

fixedindev

**Where** File::Glob **Description** I suggested documenting that negated character classes must be specified with `[!...]`, and `[^...]` does not work. Perhaps simply by adding a line: ``` [!...] negated character...

Needs Triage
documentation

According to the "By file name" section in the documentation, and historical practice since the invention of .fontspec files, giving explicit extensions on font variants is supposed to be equivalent...

Is there a specification (however informal) of what a LaTeX graphics backend needs to implement? So Martin Ruckert knows what he has to implement for the viewers in his HINT...

enhancement
category graphics
bug (documentation)
stale