Edit - TeX - LaTeX Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Does this change e.g. the title font size to 17bp? (To be precise, it's 17.28pt/bp, cf. egreg's comment to the question.)
– doncherry
Commented Nov 8, 2011 at 9:04
3

@doncherry: It changes all font commands (and several lengths), e.g., \huge, \LARGE, \Large relative to 12bp/10bp. Example: At 10pt (predefined font size at article) \LARGE is \@xviipt, that is 17.28pt. With scrextend and fontsize=12bp it will be 17.28pt*12bp/10pt = 17,28*1,2bp=20.736bp=20.8137pt (try \LARGE\csname f@size\endcsname to see this). Alternative: You may define your own font size file scrsize12bp.clo. In this case this file will be used instead of calculated sizes by scrextend. Use scrsize12pt.clo as template and simply change all lengths from pt to bp.
– Schweinebacke
Commented Nov 8, 2011 at 9:14
@Schweinebacke I'm a little bit confused there. I always used KOMA-Script with pt. I tried using fontsize=12bp and got less pages than with fontsize=12pt. Should't it be opposite according to @Werner's answer?
– Thorsten
Commented Nov 8, 2011 at 12:57
2

@Thorsten: 1in = 72bp = 72,27pt. So a pt is smaller than a bp, but: With a4paper there's a DIV default for 12pt but not for 12bp. So DIV=calc will be used with 12bp. If I try a document with DIV=9 and \lipsum[1-100] almost nothing changes if I use fontsize=12bp instead of fontsize=12pt. Additionally remember: There's a file scrsize12pt.clo with optimized (not only horizontal) lengths. KOMA-Script may use an optimized scrsize12bp.clo too, but it does not provide it.
– Schweinebacke
Commented Nov 8, 2011 at 13:06
@Schweinebacke Ah, that's a good point. I didn't think of DIV. Thank you for pointing this out.
– Thorsten
Commented Nov 8, 2011 at 13:24

| Show 2 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »