kcss-style issueshttps://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues2023-11-01T14:03:13Zhttps://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/27units package breaks with TeXLive 20232023-11-01T14:03:13ZSören Domrössdo@informatik.uni-kiel.deunits package breaks with TeXLive 2023Aus dem Email-Verkehr:
Ich habe letztens mein TeXLive auf die Version von 2023 aktualisiert und bekomme nun Probleme mit dem Package "siunitx", das in der neuen Version nicht mehr mit dem Package "units" kompatibel ist und zu einem Abbr...Aus dem Email-Verkehr:
Ich habe letztens mein TeXLive auf die Version von 2023 aktualisiert und bekomme nun Probleme mit dem Package "siunitx", das in der neuen Version nicht mehr mit dem Package "units" kompatibel ist und zu einem Abbruch des LaTeX-Laufs führt. Letzteres Package wird aber vom KCSS-Stil importiert. Gibt es hierfür einen besonderen Grund (abgesehen von Abwärtskompatibilität)? Ich habe es bei mir lokal auskommentiert und bekomme zumindest keine Probleme, aber vielleicht nutze ich auch nicht die relevanten Features. Ansonsten schlage ich vor, das Package aus dem Stil zu entfernen. Laut dem Autor von siunitx ist das Package units veraltet (die letzte Version ist meines Wissens von 1998), weswegen er die Kompatibilität aufgegeben hat.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/18Compilation fails with current package versions2023-09-20T12:27:14ZNis Boerge Wechselbergnbw@informatik.uni-kiel.deCompilation fails with current package versionsWith MikTEx or TexLive on Windows, using up-to-date packages, the compilation of the template fails with:
```
! LaTeX Error: Command \comment already defined.
Or name \end... illegal, see p.192 of the manual.
See the LaTe...With MikTEx or TexLive on Windows, using up-to-date packages, the compilation of the template fails with:
```
! LaTeX Error: Command \comment already defined.
Or name \end... illegal, see p.192 of the manual.
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
...
l.791 }
```
It looks like the `changes` package has introduced a `\comment` command in November (see https://gitlab.com/ekleinod/changes/blob/master/changelog.md#300-2018-11-04) which now collides with another comment command already present somewhere else.
A quick workaround is adding `\let\comment\relax` before the `\RequirePackage{changes}` in ifiseries.sty.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/25Plural s for acronyms is not formatted in smaller style when using acro package2023-09-20T12:23:36ZAlexander Schulz-RosengartenPlural s for acronyms is not formatted in smaller style when using acro packageWhen using the `acro` package for acronyms (`\usepackage[acronymPackage=acro]{ifiseries}`) the plural s of the short form is not formatted in the smaller font, which is typographically incorrect.
![image](/uploads/fdc1357337c3ebda99a1c1...When using the `acro` package for acronyms (`\usepackage[acronymPackage=acro]{ifiseries}`) the plural s of the short form is not formatted in the smaller font, which is typographically incorrect.
![image](/uploads/fdc1357337c3ebda99a1c162220b68f6/image.png)
Setting the option `format-include-endings` to `true` in `acsetup` will fix this. See: https://tex.stackexchange.com/questions/410140/acro-long-format-for-plural-acronymsSören Domrössdo@informatik.uni-kiel.deSören Domrössdo@informatik.uni-kiel.dehttps://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/21Acro Package support is broken2023-09-20T12:16:52ZDaniel MäckelmannAcro Package support is brokenThe support for the acronym package `acro` was added 5 years ago in 1cd0b81a and wasn't changed from then on. But it is mentioned in the manual.
In version 3 of `acro` (released in 2020), the styling commands changed completely. So the ...The support for the acronym package `acro` was added 5 years ago in 1cd0b81a and wasn't changed from then on. But it is mentioned in the manual.
In version 3 of `acro` (released in 2020), the styling commands changed completely. So the ones currently in use in `ifiseries.sty` don't work anymore. So if I try to use this style together with ``acro`` and a somewhat recent tex distribution, my document won't compile anymore.
I think the easiest fix is to force the use of `acro` version 2 by changing line 280 in `ifiseries.sty` to `\RequirePackage{acro}[=v2]%`.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/19Sentence Case-Option für Bibliographie2023-09-20T12:06:11ZGhost UserSentence Case-Option für BibliographieAktuell wird in der Bibliographie alles klein geschrieben bis auf den Anfangsbuchstaben des ersten Wortes. Es wäre wünschenswert, eine Option einzufügen, die erlaubt, diese Case-Anpassung abzuschalten und direkt die Groß-/Kleinschreibung...Aktuell wird in der Bibliographie alles klein geschrieben bis auf den Anfangsbuchstaben des ersten Wortes. Es wäre wünschenswert, eine Option einzufügen, die erlaubt, diese Case-Anpassung abzuschalten und direkt die Groß-/Kleinschreibung wie im bib-Eintrag zu verwenden. Laut einer Mail zum Thema ist Zeile 180 in `ifiseries.sty` involviert.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/24Add Institut für Informatik new Logo2023-03-28T15:12:38ZSören Domrössdo@informatik.uni-kiel.deAdd Institut für Informatik new Logohttps://www.tf.uni-kiel.de/de/das-dekanat/betriebliche-ablaeufe/tf-logo%2C%20Version%202022https://www.tf.uni-kiel.de/de/das-dekanat/betriebliche-ablaeufe/tf-logo%2C%20Version%202022https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/20Triple quotation marks in bibliography in german style2023-03-09T08:25:25ZSören Domrössdo@informatik.uni-kiel.deTriple quotation marks in bibliography in german style![image](/uploads/cdc316f72fbd29e17543c7da8122567d/image.png)![image](/uploads/cdc316f72fbd29e17543c7da8122567d/image.png)Sören Domrössdo@informatik.uni-kiel.deSören Domrössdo@informatik.uni-kiel.dehttps://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/15Expand description of PhD process2019-08-14T12:42:07ZGhost UserExpand description of PhD processExpand the documentation of the publishing process or add a new document that describes how the KCSS process fits into the overall process of submitting one's dissertation. Cmot has provided helpful remarks in an e-mail (January 10, 2018...Expand the documentation of the publishing process or add a new document that describes how the KCSS process fits into the overall process of submitting one's dissertation. Cmot has provided helpful remarks in an e-mail (January 10, 2018) that I won't reproduce here.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/6Bibliography style problem2019-08-14T12:37:20ZGhost UserBibliography style problemWith biblatex active, citations in the bibliography can be typeset inconsistently. Examples:
* @article has its title set in quotes and regular font.
* @techrep and @misc have their title set in italics without quotes.
* @mastersth...With biblatex active, citations in the bibliography can be typeset inconsistently. Examples:
* @article has its title set in quotes and regular font.
* @techrep and @misc have their title set in italics without quotes.
* @mastersthesis has its title surrounded by three quotes!https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/8Add legal page template2019-08-14T12:30:25ZGhost UserAdd legal page templateThe dissertation version submitted to the reviewers must include a legal page. A template for that page should be offered by the KCSS style.The dissertation version submitted to the reviewers must include a legal page. A template for that page should be offered by the KCSS style.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/12Investigate DOIs2019-02-12T08:58:03ZGhost UserInvestigate DOIsAre DOIs used to reference published KCSS books? How are they obtained? Should we adapt the process and include them in the book's metadata?Are DOIs used to reference published KCSS books? How are they obtained? Should we adapt the process and include them in the book's metadata?https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/14Template for Theses should default a4paper, largepaper2018-05-02T11:15:40ZGhost UserTemplate for Theses should default a4paper, largepaperhttps://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/9Add urn:nbn information to meta data page2018-02-02T11:07:54ZGhost UserAdd urn:nbn information to meta data pageThe meta data page code needs to be updated to also include the new urn:nbn identifiers.
Be sure to update the manual accordingly.The meta data page code needs to be updated to also include the new urn:nbn identifiers.
Be sure to update the manual accordingly.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/10Add revision information to metapage macro2018-02-02T11:07:54ZGhost UserAdd revision information to metapage macroThe meta page macro should provide a consistent way to provide information about which KCSS publication is replaced by the current publication.
Be sure to update the manual accordingly.The meta page macro should provide a consistent way to provide information about which KCSS publication is replaced by the current publication.
Be sure to update the manual accordingly.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/7Compiling a document results in "No room for new ..." error2017-06-06T17:09:50ZGhost UserCompiling a document results in "No room for new ..." errorWhen compiling the manual with TeXLive 2015 on Mac, the following error message is generated:
```No room for a new \count . [...finable\flrow@foot{\newinsert\flrow@foot}]```When compiling the manual with TeXLive 2015 on Mac, the following error message is generated:
```No room for a new \count . [...finable\flrow@foot{\newinsert\flrow@foot}]```https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/13"Eidesstattliche Erklärung" umbenennen2017-06-02T16:32:45ZGhost User"Eidesstattliche Erklärung" umbenennenStudenten sollten laut Prüfungsamt keine "Eidesstattliche Erklärung" abgeben.Studenten sollten laut Prüfungsamt keine "Eidesstattliche Erklärung" abgeben.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/1Missing Palatino font for chapters.2017-04-20T16:49:28ZGhost UserMissing Palatino font for chapters.Using the KCSS-style with the Palatino font generates the warning
LaTeX Font Warning: Font shape `T1/pplx/bx/sc' undefined
(Font) using `T1/pplx/bx/n' instead on input line ...
It appears to be the font that i...Using the KCSS-style with the Palatino font generates the warning
LaTeX Font Warning: Font shape `T1/pplx/bx/sc' undefined
(Font) using `T1/pplx/bx/n' instead on input line ...
It appears to be the font that is used for the "Chapter <N>" texts.
This font can be substituted manually using
\DeclareFontShape{T1}{pplx}{bx}{sc}{<->ssub*jkp/bx/sc}{}
or a similar option.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/2Deprecated babel option.2017-04-20T16:49:28ZGhost UserDeprecated babel option.Using the default KCSS style with TeX Live 2014 generates the following warning:
Package biblatex Warning: 'babel' option is deprecated, use 'autolang' instead.
This can be solved by removing the option `babel=other` from the `...Using the default KCSS style with TeX Live 2014 generates the following warning:
Package biblatex Warning: 'babel' option is deprecated, use 'autolang' instead.
This can be solved by removing the option `babel=other` from the `biblatexOptions`.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/3Warning of package pgfplots2017-04-20T16:49:28ZGhost UserWarning of package pgfplotsHi, when I compile the following simple document
```latex
\documentclass{article}
\usepackage[biblatex=false]{ifiseries}
\begin{document}
Test.
\end{document}
```
using `pdflatex` I get the following warning:
```
Packag...Hi, when I compile the following simple document
```latex
\documentclass{article}
\usepackage[biblatex=false]{ifiseries}
\begin{document}
Test.
\end{document}
```
using `pdflatex` I get the following warning:
```
Package pgfplots Warning: running in backwards compatibility mode (unsuitable t
ick labels; missing features). Consider writing \pgfplotsset{compat=1.11} into
your preamble.
on input line 4.
```
A quick fix is to use to proposed command in the preamble (and this makes the warning disappear), but maybe there is an even better solution. For the record: I'm using the following version of `pdflatex`:
```
$ pdflated
This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2015/dev/Debian) (preloaded format=pdflatex)
...
```https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/4Inconsistency between bibtex example and metapage cite2017-04-20T16:49:28ZGhost UserInconsistency between bibtex example and metapage citeHi, I realized that in the example dissertation (`manual-example.tex`) the intended bibliography item proposed on the metapage and the BibTeX entry do not match entirely.
For instance, the publisher field in the entry ends with `CAU K...Hi, I realized that in the example dissertation (`manual-example.tex`) the intended bibliography item proposed on the metapage and the BibTeX entry do not match entirely.
For instance, the publisher field in the entry ends with `CAU Kiel`, which does not show in the bibliography item.
Furthermore, if I take the entry, then the generated bibliography item reads:
```
John Q. Postgraduate. My fake dissertation with a long title. Kiel Computer
Science Series 2011/99. Dissertation, Faculty of Engineering, Kiel University.
Department of Computer Science, CAU Kiel, 2011. isbn: xxx-x-xxxxx-xxx-x.
```
where the proposed item is
```
John Q. Postgraduate. My Fake Dissertation With a Long Title. Number 2011/99 in Kiel
Computer Science Series. Department of Computer Science, 2011. Dissertation, Faculty
of Engineering, Kiel University.
```
I understand that the style heavily depends on the setup of `biblatex`, but maybe some harmonization would be beneficial?