Mrthfx

Combinations of multiple lists

What reasons are there for a Capitalist to oppose a 100% inheritance tax?

Today is the Center

Why does Arabsat 6A need a Falcon Heavy to launch

Assassin's bullet with mercury

prove that the matrix A is diagonalizable

A reference to a well-known characterization of scattered compact spaces

How can I tell someone that I want to be his or her friend?

What exploit are these user agents trying to use?

Twin primes whose sum is a cube

How to prevent "they're falling in love" trope

Blender 2.8 I can't see vertices, edges or faces in edit mode

Why can't we play rap on piano?

Forgetting the musical notes while performing in concert

Is it unprofessional to ask if a job posting on GlassDoor is real?

Can I use a neutral wire from another outlet to repair a broken neutral?

What is the word for reserving something for yourself before others do?

SSH "lag" in LAN on some machines, mixed distros

Is "remove commented out code" correct English?

Is it inappropriate for a student to attend their mentor's dissertation defense?

In a Spin are Both Wings Stalled?

Python: return float 1.0 as int 1 but float 1.5 as float 1.5

What's the point of deactivating Num Lock on login screens?

If human space travel is limited by the G force vulnerability, is there a way to counter G forces?

Conversion of page Geometry to Typearea with scrbook Koma Script

Change layout or borders of my document without package {geometry}Underfull vbox and typearea warnings with Koma-Script and a5paperKOMA-Script footer marginsIncreasing left margins when using scrbook with geometryKOMA-Script scrbook: How to remove period after partKoma-Script (scrbook): twocolumn formatting and wide equation problemDefine page layout in geometry similar to Koma Script with DIV 12Koma-Script areaset and footlinesKOMA-Script: Why does “DIV=calc” destroy the initial geometry?Difference between DIV=calc and default DIV for Koma Script class scrbookWhat KOMA-Script article (scrartcl) has that KOMA-Script book (scrbook) does not?

3

I've read that I shouldn't use the geometry package with KOMA-Script. So, I would like to convert my page layout to something similar using Koma-Scripts built in typearea features.

documentclass[american,headings=openany]{scrbook}

usepackage{scrlayer-scrpage} %input{headersfooters}

usepackage{microtype}  

usepackage{setspace} onehalfspacing

usepackage[utf8]{inputenc}

usepackage[T1]{fontenc}

%

% % % these font packages require a full install %

renewcommand{ttdefault}{lmtt} % monospace font %

usepackage{libris}             % san serif font %

usepackage{tgschola}           % roman font     %

%

%

usepackage[paperwidth=5.06in,paperheight=7.81in]{geometry}

   geometry{verbose,tmargin=0.75in,bmargin=0.75in,%

     lmargin=0.7in,rmargin=0.4in,headheight=0.25in,%

     headsep=0.2in,footskip=0.4in}%

%

begin{document}



% input{mybook} % I will input many chapters %



Hello World, this will be my book.



end{document}

Can anyone provide me the typearea code that would replace geometry with similar results? It does not have to be exact. I want to learn which typearea options I will need, and what adjustments I need to tinker with. I've read through the scrguien.pdf but it's not sinking in very well (I'm still confused). But so far I've read about the BCOR= and DIV= options, the possible values for DIV, especially the numeric values, the last value, the areaset value. And the typearea command. But I have no idea what to do with them.

geometry scrbook typearea

share|improve this question

edited Sep 28 '16 at 2:18

user12711

asked Sep 27 '16 at 21:52

user12711user12711

1,4911228

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please provide something people can compile which doesn't rely on files only you have.
  
  – cfr
  Sep 27 '16 at 23:58
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Done. I it should compile now. But the book will be tiny.
  
  – user12711
  Sep 28 '16 at 2:19
  

  
  
  
  

add a comment | 

3

I've read that I shouldn't use the geometry package with KOMA-Script. So, I would like to convert my page layout to something similar using Koma-Scripts built in typearea features.

documentclass[american,headings=openany]{scrbook}

usepackage{scrlayer-scrpage} %input{headersfooters}

usepackage{microtype}  

usepackage{setspace} onehalfspacing

usepackage[utf8]{inputenc}

usepackage[T1]{fontenc}

%

% % % these font packages require a full install %

renewcommand{ttdefault}{lmtt} % monospace font %

usepackage{libris}             % san serif font %

usepackage{tgschola}           % roman font     %

%

%

usepackage[paperwidth=5.06in,paperheight=7.81in]{geometry}

   geometry{verbose,tmargin=0.75in,bmargin=0.75in,%

     lmargin=0.7in,rmargin=0.4in,headheight=0.25in,%

     headsep=0.2in,footskip=0.4in}%

%

begin{document}



% input{mybook} % I will input many chapters %



Hello World, this will be my book.



end{document}

Can anyone provide me the typearea code that would replace geometry with similar results? It does not have to be exact. I want to learn which typearea options I will need, and what adjustments I need to tinker with. I've read through the scrguien.pdf but it's not sinking in very well (I'm still confused). But so far I've read about the BCOR= and DIV= options, the possible values for DIV, especially the numeric values, the last value, the areaset value. And the typearea command. But I have no idea what to do with them.

geometry scrbook typearea

share|improve this question

edited Sep 28 '16 at 2:18

user12711

asked Sep 27 '16 at 21:52

user12711user12711

1,4911228

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please provide something people can compile which doesn't rely on files only you have.
  
  – cfr
  Sep 27 '16 at 23:58
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Done. I it should compile now. But the book will be tiny.
  
  – user12711
  Sep 28 '16 at 2:19
  

  
  
  
  

add a comment | 

I've read that I shouldn't use the geometry package with KOMA-Script. So, I would like to convert my page layout to something similar using Koma-Scripts built in typearea features.

documentclass[american,headings=openany]{scrbook}

usepackage{scrlayer-scrpage} %input{headersfooters}

usepackage{microtype}  

usepackage{setspace} onehalfspacing

usepackage[utf8]{inputenc}

usepackage[T1]{fontenc}

%

% % % these font packages require a full install %

renewcommand{ttdefault}{lmtt} % monospace font %

usepackage{libris}             % san serif font %

usepackage{tgschola}           % roman font     %

%

%

usepackage[paperwidth=5.06in,paperheight=7.81in]{geometry}

   geometry{verbose,tmargin=0.75in,bmargin=0.75in,%

     lmargin=0.7in,rmargin=0.4in,headheight=0.25in,%

     headsep=0.2in,footskip=0.4in}%

%

begin{document}



% input{mybook} % I will input many chapters %



Hello World, this will be my book.



end{document}

Can anyone provide me the typearea code that would replace geometry with similar results? It does not have to be exact. I want to learn which typearea options I will need, and what adjustments I need to tinker with. I've read through the scrguien.pdf but it's not sinking in very well (I'm still confused). But so far I've read about the BCOR= and DIV= options, the possible values for DIV, especially the numeric values, the last value, the areaset value. And the typearea command. But I have no idea what to do with them.

geometry scrbook typearea

share|improve this question

edited Sep 28 '16 at 2:18

user12711

asked Sep 27 '16 at 21:52

user12711user12711

1,4911228

documentclass[american,headings=openany]{scrbook}

usepackage{scrlayer-scrpage} %input{headersfooters}

usepackage{microtype}  

usepackage{setspace} onehalfspacing

usepackage[utf8]{inputenc}

usepackage[T1]{fontenc}

%

% % % these font packages require a full install %

renewcommand{ttdefault}{lmtt} % monospace font %

usepackage{libris}             % san serif font %

usepackage{tgschola}           % roman font     %

%

%

usepackage[paperwidth=5.06in,paperheight=7.81in]{geometry}

   geometry{verbose,tmargin=0.75in,bmargin=0.75in,%

     lmargin=0.7in,rmargin=0.4in,headheight=0.25in,%

     headsep=0.2in,footskip=0.4in}%

%

begin{document}



% input{mybook} % I will input many chapters %



Hello World, this will be my book.



end{document}

share|improve this question

edited Sep 28 '16 at 2:18

user12711

asked Sep 27 '16 at 21:52

user12711user12711

1,4911228

share|improve this question

edited Sep 28 '16 at 2:18

user12711

asked Sep 27 '16 at 21:52

user12711user12711

1,4911228

asked Sep 27 '16 at 21:52

user12711user12711

1,4911228

asked Sep 27 '16 at 21:52

user12711user12711

1,4911228

1 Answer
1

active

oldest

votes

4

Well, at last you can read the definition of the page layout with typearea in the documentation of KOMA-Script, page 24, chapter Construction of the Page Layout with typearea (you can open it with texdoc komascript.

You can also use package layout or package layouts to check the resulting values for different parameters for typearea (documentation: texdoc layout or texdoc layouts).

The main difference between geometry and typearea is, that typearea calculates an optimal typing area depending on the used fontsize but geometry "only" uses the given values for margins etc to create a typing area. With geometry there is no algorithm to calculate an typing area depending on the fontsize.

So if you want a good looking typography for the page (and you do not know what is a good typography) use typearea to calculate a good looking page. If you have to follow rules given by your university for margins etc. then it is easier to use geometry to fullfill the rules.

share|improve this answer

edited 6 hours ago

answered Sep 27 '16 at 23:30

KurtKurt

40.7k850164

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi, I don't really know what a "good looking" typography is. Typearea sounds like a good option for me. I do have a couple of rules: there needs to be at minimum 0.25" margin. (The pages will be printed on a larger stock and trimmed, and the result is that there's a plus/minus 0.25" cutting error, so everything could get shifted one way or the other by up to 0.25" Anything closer to edge could get cropped out.) They advise 0.5" margins or greater so nothing will be on the edge. Also I have several pagesize inch options to pick from 5x8.25 8.5x5.5 or 5.06x7.81. (How do I use areaset?)
  
  – user12711
  Sep 28 '16 at 2:39
  
  
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Perhaps you would find this useful A Few Notes on Book Design by myself. Available via texdoc memdesign
  
  – Peter Wilson
  Sep 28 '16 at 18:36
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @user12711 typearea uses A4 or letter as basics. Then it calculates depending on fontsize (see table 2.1 in KOMA-Script documentation) and BCOR. If you check the log file you find there in pt the used values. Package layout/s prints the used values in cm as far as I remember. So you can play with the values for KOMA-Script to get as close as possible to your needs (that could be took some time) or if you need to fullfill the rules in your comment just use geometry. That fit then better your needs ... And sorry, I'm a German, not used to calculate in inch :-(
  
  – Kurt
  Sep 28 '16 at 19:38
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @PeterWilson With MiKTeX 2.9 texdoc memdesign does not show any document ...
  
  – Kurt
  Sep 28 '16 at 19:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @PeterWilson, it's working when I type it [full texlive distribution].
  
  – user12711
  Sep 28 '16 at 21:40
  

  
  
  
  

 | 
show 1 more comment

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f331654%2fconversion-of-page-geometry-to-typearea-with-scrbook-koma-script%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

4

Well, at last you can read the definition of the page layout with typearea in the documentation of KOMA-Script, page 24, chapter Construction of the Page Layout with typearea (you can open it with texdoc komascript.

You can also use package layout or package layouts to check the resulting values for different parameters for typearea (documentation: texdoc layout or texdoc layouts).

The main difference between geometry and typearea is, that typearea calculates an optimal typing area depending on the used fontsize but geometry "only" uses the given values for margins etc to create a typing area. With geometry there is no algorithm to calculate an typing area depending on the fontsize.

So if you want a good looking typography for the page (and you do not know what is a good typography) use typearea to calculate a good looking page. If you have to follow rules given by your university for margins etc. then it is easier to use geometry to fullfill the rules.

share|improve this answer

edited 6 hours ago

answered Sep 27 '16 at 23:30

KurtKurt

40.7k850164

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi, I don't really know what a "good looking" typography is. Typearea sounds like a good option for me. I do have a couple of rules: there needs to be at minimum 0.25" margin. (The pages will be printed on a larger stock and trimmed, and the result is that there's a plus/minus 0.25" cutting error, so everything could get shifted one way or the other by up to 0.25" Anything closer to edge could get cropped out.) They advise 0.5" margins or greater so nothing will be on the edge. Also I have several pagesize inch options to pick from 5x8.25 8.5x5.5 or 5.06x7.81. (How do I use areaset?)
  
  – user12711
  Sep 28 '16 at 2:39
  
  
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Perhaps you would find this useful A Few Notes on Book Design by myself. Available via texdoc memdesign
  
  – Peter Wilson
  Sep 28 '16 at 18:36
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @user12711 typearea uses A4 or letter as basics. Then it calculates depending on fontsize (see table 2.1 in KOMA-Script documentation) and BCOR. If you check the log file you find there in pt the used values. Package layout/s prints the used values in cm as far as I remember. So you can play with the values for KOMA-Script to get as close as possible to your needs (that could be took some time) or if you need to fullfill the rules in your comment just use geometry. That fit then better your needs ... And sorry, I'm a German, not used to calculate in inch :-(
  
  – Kurt
  Sep 28 '16 at 19:38
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @PeterWilson With MiKTeX 2.9 texdoc memdesign does not show any document ...
  
  – Kurt
  Sep 28 '16 at 19:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @PeterWilson, it's working when I type it [full texlive distribution].
  
  – user12711
  Sep 28 '16 at 21:40
  

  
  
  
  

 | 
show 1 more comment

4

Well, at last you can read the definition of the page layout with typearea in the documentation of KOMA-Script, page 24, chapter Construction of the Page Layout with typearea (you can open it with texdoc komascript.

You can also use package layout or package layouts to check the resulting values for different parameters for typearea (documentation: texdoc layout or texdoc layouts).

The main difference between geometry and typearea is, that typearea calculates an optimal typing area depending on the used fontsize but geometry "only" uses the given values for margins etc to create a typing area. With geometry there is no algorithm to calculate an typing area depending on the fontsize.

So if you want a good looking typography for the page (and you do not know what is a good typography) use typearea to calculate a good looking page. If you have to follow rules given by your university for margins etc. then it is easier to use geometry to fullfill the rules.

share|improve this answer

edited 6 hours ago

answered Sep 27 '16 at 23:30

KurtKurt

40.7k850164

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi, I don't really know what a "good looking" typography is. Typearea sounds like a good option for me. I do have a couple of rules: there needs to be at minimum 0.25" margin. (The pages will be printed on a larger stock and trimmed, and the result is that there's a plus/minus 0.25" cutting error, so everything could get shifted one way or the other by up to 0.25" Anything closer to edge could get cropped out.) They advise 0.5" margins or greater so nothing will be on the edge. Also I have several pagesize inch options to pick from 5x8.25 8.5x5.5 or 5.06x7.81. (How do I use areaset?)
  
  – user12711
  Sep 28 '16 at 2:39
  
  
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  Perhaps you would find this useful A Few Notes on Book Design by myself. Available via texdoc memdesign
  
  – Peter Wilson
  Sep 28 '16 at 18:36
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @user12711 typearea uses A4 or letter as basics. Then it calculates depending on fontsize (see table 2.1 in KOMA-Script documentation) and BCOR. If you check the log file you find there in pt the used values. Package layout/s prints the used values in cm as far as I remember. So you can play with the values for KOMA-Script to get as close as possible to your needs (that could be took some time) or if you need to fullfill the rules in your comment just use geometry. That fit then better your needs ... And sorry, I'm a German, not used to calculate in inch :-(
  
  – Kurt
  Sep 28 '16 at 19:38
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @PeterWilson With MiKTeX 2.9 texdoc memdesign does not show any document ...
  
  – Kurt
  Sep 28 '16 at 19:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @PeterWilson, it's working when I type it [full texlive distribution].
  
  – user12711
  Sep 28 '16 at 21:40
  

  
  
  
  

 | 
show 1 more comment

Well, at last you can read the definition of the page layout with typearea in the documentation of KOMA-Script, page 24, chapter Construction of the Page Layout with typearea (you can open it with texdoc komascript.

You can also use package layout or package layouts to check the resulting values for different parameters for typearea (documentation: texdoc layout or texdoc layouts).

The main difference between geometry and typearea is, that typearea calculates an optimal typing area depending on the used fontsize but geometry "only" uses the given values for margins etc to create a typing area. With geometry there is no algorithm to calculate an typing area depending on the fontsize.

So if you want a good looking typography for the page (and you do not know what is a good typography) use typearea to calculate a good looking page. If you have to follow rules given by your university for margins etc. then it is easier to use geometry to fullfill the rules.

share|improve this answer

edited 6 hours ago

answered Sep 27 '16 at 23:30

KurtKurt

40.7k850164

share|improve this answer

edited 6 hours ago

answered Sep 27 '16 at 23:30

KurtKurt

40.7k850164

answered Sep 27 '16 at 23:30

KurtKurt

40.7k850164

answered Sep 27 '16 at 23:30

KurtKurt

40.7k850164