Take the 2-minute tour ×
TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. It's 100% free, no registration required.

Triggered by the question why should I not use the koma script classes results practically necessarily a consequence question: What packages are incompatible with KOMA-Script?

KOMA-Script offers scrhack to fix certain well-known problems with the packages:

  • hyperref,
  • float,
  • floatrow, and
  • listings.

In the question incompatibilities between babelfrench and koma script classes? special problems of \usepackage[french][babel] are reported.

Which packages do you know having problems with KOMA-Script?

share|improve this question
2  
geometry resets the from typepage calculated margins if you don't use the option pass (for showframe). –  Qrrbrbirlbel Sep 19 '12 at 18:49
add comment

1 Answer

up vote 14 down vote accepted

Marcus Kohm, the author of KOMA-Script (see his initials), utters about this frequently, but unluckily for TeX.SE usually in German.

Also I would prefer to say, some packages are not fully compatible instead of they are incompatible, because in most cases they work partially and often there’s a workaround.

  • Every package, that makes a redefinition of titling and heading, is potentially not fully compatible. A well-known example is titlesec, where here on TeX.SE we have already a related question: Incompatibilities between KOMA-Script and titlesec.

  • Also packages with a heavy redefinition of footnote related stuff are potentially not fully compatible. I myself noticed, that footnotebackref only works with an active symbol (the footnote number is not turned into an active link, confer package manual).
    By the way: This works fine:

    \usepackage[symbol=${}^{\scriptscriptstyle\uparrow}$]{footnotebackref}% needs "hyperref"
    
  • The caption package is according to its package documentation not fully compatible. But actually this was quite more serious in older versions both of caption and KOMA-Script (see also comment below of caption author Axel Sommerfeldt).


As scrpage2 is part of KOMA-Script (but is a package and can be used with other classes!):

  • Package xwatermark relies on fancyhdr, so with scrpage2 you will get error messages.
share|improve this answer
9  
Regarding my caption package: The optional argument of \setcapwidth (offered by KOMA-Script) is the only thing I'm aware of which is not supported when loading the caption package. Especially everything (commands & options) the caption package offers IS compatible with the KOMA-Script document classes, and I'm trying hard to keep the caption package as compatible with KOMA-Script as possible. So in fact the caption package supports the KOMA-Script classes. –  Axel Sommerfeldt Sep 20 '12 at 5:44
    
@AxelSommerfeldt: Yes, you wrote about that in the manual, and because of that I referred to it. –  Speravir Sep 20 '12 at 16:23
4  
I for my part would say “to be expected” instead of “not fully compatible”. When I load a package like titlesec and use it to redefine \chapter, say, I cannot expect that KOMA's definition still holds... the same is true for footnotes. –  cgnieder Sep 20 '12 at 17:25
    
@cgnieder: What? :-) It’s a different point of view, I guess, but feel free to rephrase my writing. (My English is not the best on earth.) –  Speravir Sep 20 '12 at 17:34
    
No, that's not what I meant. Your point of view is a valid one! I just wanted to say that (and why) I see it differently. –  cgnieder Sep 20 '12 at 17:42
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.