KOMA-Script with standard LaTeX layout
Andreas Keil
sans-serif default for headings, labels, and so on.
Is there a documenation available, how to configure a KOMA-Script article
(scrartcl) to look exactly like a LaTeX article?
I know how to customize the sectioning fonts with
\addtokomafont{sectioning}{\rmfamily} for example, but I'd like to have a
full list of customizations needed to get a "standard article look".
Maybe the author (Markus Kohm) can help, because I didn't find any
documentation about all default font settings in KOMA-Script.
--
Andreas
For replying, remove the fruit from my address:
andrea...@apple.nurfuerspam.de
Ralf Stubner
> Maybe the author (Markus Kohm) can help, because I didn't find any
> documentation about all default font settings in KOMA-Script.
Have you had a look into the documentation for KOMA Script? It's called
scrguide (german) or scrguien (english). It has to be installed on your
system and is usually avaiable in DVI or PDF format.
cheerio
ralf
Andreas Keil
de news:lzd6dj7...@tfkp12.physik.uni-erlangen.de...
> "Andreas Keil" <andrea...@apple.nurfuerspam.de> writes:
>
> Have you had a look into the documentation for KOMA Script? It's called
> scrguide (german) or scrguien (english). It has to be installed on your
> system and is usually avaiable in DVI or PDF format.
Yes, of course I had a look: I could only find the commands to change the
font selection but no hint, what the differences are exactly (compared to
article). The german scrguide, e.g. says: "Namen und Bedeutung der einzelnen
Elemente sind in Tabelle 3.3 aufgelistet. Die Voreinstellungen sind den
jeweiligen Abschnitten zu entnehmen."
That means, I'd have to read the whole documentation, line for line, to find
out all style modifications KOMA-Script does automatically.
It would be great, if there would exist an option like "standardlayout" or
"latexlayout" for KOMA-Script. Or, at least, a table that summarizes all
style/layout modifications.
Markus Kohm
> That means, I'd have to read the whole documentation, line for line, to
> find out all style modifications KOMA-Script does automatically.
--> "Index der Elemente mit Möglichkeit zur Schriftumschaltung" in English:
"Index of Elements with Possibility of Fontswitching".
But you only need to change captionlabel and pagenumber to \normalfont,
descriptionlabel to \bfseries, and sectioning to \normalfont\bfseries. And
you need to change the page style and the typearea and the sizes at
chapter, section, subsection, ... (see the standard classes to get their
values) and you need to change the spaces before and after and at \chapter,
\section, \subsection ... The spaces before and after may be changed easily
(--> implementation of options bigheadings, normalheadings, smallheadings
at scrclass.dtx). But to change the horizontal spacing (if needed, I don't
know) you have to do more or use a package, which provides this.
> Or, at least, a table that summarizes all style/layout modifications.
Write it. But don't call it "modifications". KOMA-Script classes are no
modifications of the standard classes, they are newly designed classes
which know all commands, environments and options of the standard classes.
But the layout is different.
> It would be great, if there would exist an option like "standardlayout" or
> "latexlayout" for KOMA-Script.
I don't want to switch the typearea of KOMA-Script to the typearea of the
standard classes. So I will never implement such an option.
Markus
--
For informations about KOMA-Script (scrbook, scrreprt, scrartcl, scrlttr2,
scrpage2 ...) see the KOMA-Script manual, scrguien (English) or scrguide
(German).
Andreas Keil
news:1135311.J...@ID-107054.user.dfncis.de...
> Andreas Keil wrote:
>
> > That means, I'd have to read the whole documentation, line for line,
to
> > find out all style modifications KOMA-Script does automatically.
>
> --> "Index der Elemente mit Möglichkeit zur Schriftumschaltung" in
English:
> "Index of Elements with Possibility of Fontswitching".
As I already mentioned, I read the documentation and know about the way
to change font styles.
> But you only need to change captionlabel and pagenumber to
\normalfont,
> descriptionlabel to \bfseries, and sectioning to \normalfont\bfseries.
And
> you need to change the page style and the typearea and the sizes at
> chapter, section, subsection, ... (see the standard classes to get
their
> values) and you need to change the spaces before and after and at
\chapter,
> \section, \subsection ... The spaces before and after may be changed
easily
> (--> implementation of options bigheadings, normalheadings,
smallheadings
> at scrclass.dtx). But to change the horizontal spacing (if needed, I
don't
> know) you have to do more or use a package, which provides this.
Even your list is not complete. E.g., title has to be \mdseries and
smaller (also I didn't achieve to get a smaller title font using \small
or sth. like this). I already figured out, that it's hard to find out
all switches that have to be applied to get an "article appearance". I
thought, that maybe you already made a list of necessary adjustments to
achieve this, because more people may be interested in it. Obviously, I
was wrong.
> > Or, at least, a table that summarizes all style/layout
modifications.
>
> Write it. But don't call it "modifications". KOMA-Script classes are
no
> modifications of the standard classes, they are newly designed classes
> which know all commands, environments and options of the standard
classes.
> But the layout is different.
Sorry for the misplaced word "modifiactions". No reason to be upset. I
thought, you started from the standard article class when implementing
your class, because you provided all the commands, environments and
options of these, as you said. In fact, I like the layout of the
KOMA-Script classes and I don't have a strong requirement on getting the
article layout. But I think that more people would use KOMA-Script, if
they had the option to get "original fonts" at least. I've had the
experience that people are surprised by those "fancy sfseries headings"
when they look at my documents. Personally, I have the opinion that not
every LaTeX document needs to have the same style just because everyone
uses the standard classes. But not everyone is so "open-minded".
> > It would be great, if there would exist an option like
"standardlayout" or
> > "latexlayout" for KOMA-Script.
>
> I don't want to switch the typearea of KOMA-Script to the typearea of
the
> standard classes. So I will never implement such an option.
OK, right. So what about "standardfonts" at least? This could be easily
achieved, I think. Even a short paragraph in the documentation with a
collection of necessary font commands would suffice. No "home user" (as
I am) realizes the differences between the article and KOMA-Script
spacing. In fact, many people seem to adjust those spacings to their
needs and most of them don't like the standard classes' page margins.
But almost everyone loves the KOMA-Script typearea command or
DIV-options.
As I mentioned, I already tried to figure out the font changes needed to
get article's font styles, but I'm pretty sure, that I will miss sth. My
proposal is that I collect the necessary font changes and give them to
you. I would be happy, if you could check their completeness then. And
if you think it's useful, you could implement sth. like "rmfonts" and
"sffonts" (default) as class options or just put the commands into the
documentation. What about that?
--
Andreas
For replying, remove the fruit from my address.
Harald Harders
Why do you want to use KOMA-Script if you want the standard layout?
The standard classes are perfect in generating the standard layout.
Yours
Harald
--
Harald Harders Langer Kamp 8
Institut für Werkstoffe D-38106 Braunschweig
Technische Universität Braunschweig Germany
E-Mail: h.ha...@tu-bs.de Tel: +49 (5 31) 3 91-3062
WWW : http://www.tu-bs.de/institute/ifw/ Fax: +49 (5 31) 3 91-3058
Andreas Keil
> Why do you want to use KOMA-Script if you want the standard layout?
> The standard classes are perfect in generating the standard layout.
Because it
- has easy options to handle and calculate page margins,
- has the "pagesize" option,
- provides easy switching to unindented paragraphs (which is tedious to
achieve manually),
- has other functions for which I'd have to use many different packages.
I can't remember more right now, but I think that suffices for the
moment. And as I said, the most "disturbing thing" for "standard
article" users is the use of the sans-serif font in heading, ...
Whenever I can, I use the defaults of KOMA-Script, but sometimes you
have to arrange with others (e.g. when writing a paper together).
Markus Kohm
> And as I said, the most "disturbing thing" for "standard
> article" users is the use of the sans-serif font in heading, ...
And because of this the manual tells how to switch headings to roman. Oh,
there's a translation mistake, It must be (--> 3.6.2 Structuring the
Document, 1st example):
\setkomafont{sectioning}{\normalcolor\bfseries}
With this change it is possible to set all section levels at once
to not longer use sans serif fonts.
I'm sorry.
Andreas Keil
>
> > And as I said, the most "disturbing thing" for "standard
> > article" users is the use of the sans-serif font in heading, ...
>
> And because of this the manual tells how to switch headings to roman.
Oh,
> there's a translation mistake, It must be (--> 3.6.2 Structuring the
> Document, 1st example):
>
> \setkomafont{sectioning}{\normalcolor\bfseries}
>
> With this change it is possible to set all section levels at
once
> to not longer use sans serif fonts.
Do you think it's beautiful to let description labels in the sfseries
form then? I don't think so.
OK, forget it. I thought, KOMA-Script is not only a new style class but
also gathers some nice features for which one would normally have to
load many other packages.
As I mentioned many times now:
==> I know how to change the sectioning and other fonts! <==
and
==> I have read the documentation. <==
I only wanted to propose a kind of seperation of the font style features
(which really disturb some people) of KOMA-Script and the it's other
features. And to make it easier (because it's very easy to forget about
changing "title" to "\mdseries" or "descriptionlabel" to "\rmfamily",
e.g.), I proposed to gather this information either in an option or in
the documentation.
So, thanks for the advice but it doesn't help.
Anyways, have a nice day and thanks for the package.
Sven Utcke
> moment. And as I said, the most "disturbing thing" for "standard
> article" users is the use of the sans-serif font in heading, ...
I've read about some research project a few years back where someone
found a correlation between the layout of a proposal and the
acceptance rate, and at least from that research it seemed as if
sans-serif headings where _the_ key-feature! It's worth
considering(*)
Sven
(*) although I do agree that the one really horroble thing about KOMA
is how everything is muddled together...
--
_ __ The Cognitive Systems Group
| |/ /___ __ _ ___ University of Hamburg
| ' </ _ \/ _` (_-< phone: +49 (0)40 42883-2576 Vogt-Koelln-Strasse 30
|_|\_\___/\__, /__/ fax : +49 (0)40 42883-2572 D-22527 Hamburg
|___/ http://kogs-www.informatik.uni-hamburg.de/~utcke/home.html
Peter Wilson
news:blblrc$bnt$1...@news-sop.inria.fr...
Perhaps you would like to try the memoir class, which does start with
the "standard" layout but it can be easily changed.
Peter W.
--
The English FAQ is at: http://www.tex.ac.uk/faq
Examples of all symbols:
http://www.ctan.org/tex-archive/info/symbols/comprehensive
PostScript fonts:
http://www.ctan.org/tex-archive/info/Type1fonts/fontinstallationguide.pdf
Graphics & floats: http://www.ctan.org/tex-archive/info/epslatex.pdf
Andreas Keil
> Perhaps you would like to try the memoir class, which does start
with
> the "standard" layout but it can be easily changed.
Yep, I was thinking about that anyways. The thing is: I like
KOMA-Script. I know that memoir has many good features, too. The only
pitty is that those two are mutually exclusive due to their construction
as classes.
Andreas Keil
> I've read about some research project a few years back where someone
> found a correlation between the layout of a proposal and the
> acceptance rate, and at least from that research it seemed as if
> sans-serif headings where _the_ key-feature! It's worth
> considering(*)
I stick to the sans-serif defaults whenever I'm able to, because they
make the headings more distinguishable from Definitions, e.g.
But unfortunately, one has to adapt oneself to others sometimes. And
then it would be more convenient to set a few commands to get the
standard fonts instead of switching back to 'article'.
> (*) although I do agree that the one really horroble thing about KOMA
> is how everything is muddled together...
For me it was always good enough. But you're right: A more clear
separation of the different aspects of style (spacing, fonts, page
margins) would dramatically enhance acceptance and usability of
KOMA-Script (I think).
Andreas Keil
> The only pitty is that those two are mutually exclusive due to
> their construction as classes.
Uups, I think that wasn't really English. "Disadvantage" would have been
better instead of "pity" (which was also misspelled).
Rowland McDonnell
[snip]
> That means, I'd have to read the whole documentation, line for line, to find
> out all style modifications KOMA-Script does automatically.
That's the wrong way of looking at KOMA-Script: they're not modified
versions of standard classes, but new classes written from the ground up
to give you something better than the standard classes. Why try to
modify bad typography when you can just sit down and create good
typography?
(in my case, I chose the `modify bad typography' route because, erm, I'm
*very* lazy and not a great typographer; but rather than using the nice
clean KOMA-Script classes, I use a mess of bolt-on bodges which is slow,
tricky to remember, and not very elegant - so much for being lazy, eh?)
If you want to know about the differences between KOMA-Script and the
standard classes, of *course* you've got to read the source code of both
- they're entirely independent of each other.
> It would be great, if there would exist an option like "standardlayout" or
> "latexlayout" for KOMA-Script. Or, at least, a table that summarizes all
> style/layout modifications.
If you want the same printing region as the standard classes, the
easiest thing to do is to use the standard classes. Otherwise, write
the modifications yourself and put 'em in a new class file or something.
What you want hasn't got anything to do with what the author of
KOMA-Script wants (as he's said here), so there's no chance he'll
implement it for you.
Rowland.
--
Remove the animal for email address: rowland....@dog.physics.org
PGP pub key 0x62DCCA78 Sorry - the spam got to me
http://www.mag-uk.org
UK biker? Join MAG and help keep bureaucracy at bay
Jon
to look at ...."
Everyone sit down, Rowland is about to lead forth with his ENORMOUS
knowledge and intellect.
Silence for Rowland please..
Jon
"Rowland McDonnell" <real-addr...@flur.bltigibbet> wrote in message
news:1g23jsd.13i1wikv1jugwN%real-addr...@flur.bltigibbet...