kcss-style issueshttps://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues2024-01-29T16:48:30Zhttps://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/28Broken link to dissertation publication process2024-01-29T16:48:30ZNiklas RentzBroken link to dissertation publication processFootnote 3 on page 6 of the KCSS manual links to the following page, which currently leads to a 404 error page instead of an actual document: https://macau.uni-kiel.de/content/main/publicateDiss.xmlFootnote 3 on page 6 of the KCSS manual links to the following page, which currently leads to a 404 error page instead of an actual document: https://macau.uni-kiel.de/content/main/publicateDiss.xmlhttps://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/26Add links to author rights2024-01-09T15:10:34ZSören Domrössdo@informatik.uni-kiel.deAdd links to author rights- Springer Request and it should be free for authors. Click on "reprints and permissions" on the Springer page of the article you want to get permission for. Add "reproduced with permission of Springer Nature" if appropriate. Adhere to n...- Springer Request and it should be free for authors. Click on "reprints and permissions" on the Springer page of the article you want to get permission for. Add "reproduced with permission of Springer Nature" if appropriate. Adhere to normal citation standards to reference your work.
- ACM https://authors.acm.org/author-resources/author-rights Just add the citation
- IEEE https://journals.ieeeauthorcenter.ieee.org/choose-a-publishing-agreement/avoid-infringement-upon-ieee-copyright/ Add reference under everything.
Citing from own paper should also work for figures §51 UrhG but better be safe than sorry.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/23Update the manual regarding Promotionsordnung2023-03-09T07:35:50ZSören Domrössdo@informatik.uni-kiel.deUpdate the manual regarding PromotionsordnungSince KCSS is published on MACAU it is sufficient to publish via KCSS for an electronic publication.Since KCSS is published on MACAU it is sufficient to publish via KCSS for an electronic publication.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/22Acronyms overview inconsistent indentation2022-08-18T11:39:32ZTill KurzenbergerAcronyms overview inconsistent indentationThe overview of all acronyms uses inconsistent indentation. The short form of an acronym should be left-aligned and the long form should be right-aligned.
However, for acronyms with a short form of seemingly less than 3 characters the lo...The overview of all acronyms uses inconsistent indentation. The short form of an acronym should be left-aligned and the long form should be right-aligned.
However, for acronyms with a short form of seemingly less than 3 characters the long form is left-aligned aswell. See image for reference
![grafik](/uploads/1360f6ba609382e51a34b1be3a9b5777/grafik.png)https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/17pdfjam may destroy hyperlinks2018-05-14T08:24:35ZGhost Userpdfjam may destroy hyperlinksWhen processing the document with pdfjam as described in the manual there may be several problems:
* The output may not have hyperlinks anymore.
* The output might not look as good if scaled to A4. Scaling to 90% of A4 might be more ple...When processing the document with pdfjam as described in the manual there may be several problems:
* The output may not have hyperlinks anymore.
* The output might not look as good if scaled to A4. Scaling to 90% of A4 might be more pleasant.
Check whether these points are valid and what to do about them.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/16Possibly support cleverref2018-05-07T09:58:42ZGhost UserPossibly support cleverrefcleverref is a successor to autoref and is supposed to be better. Possibly add an option to support it.cleverref is a successor to autoref and is supposed to be better. Possibly add an option to support it.https://git.informatik.uni-kiel.de/kcss/kcss-style/-/issues/5Change compactitemize to also use triangles2018-02-02T11:07:54ZGhost UserChange compactitemize to also use trianglesSomeday I wanted to use both a regular `itemize` enrivonment as well as a `compactitemize` environment for space reasons, but discovered that they are differently represented (the former uses triangles to the right, while the latter uses...Someday I wanted to use both a regular `itemize` enrivonment as well as a `compactitemize` environment for space reasons, but discovered that they are differently represented (the former uses triangles to the right, while the latter uses bullets).
For the other types of environments (`description`, `enumerate`) both the compactified and the original version use the same symbol. Are there any deeper reasons for the bullet symbol? Otherwise, I suggest to change it to the right-directed triangle for consistency.