Comments (21)
Could you give a minimal example of the problem?
from biblatex.
Actually, does his help? It's probably a better solution than hacking Koma macros internally
from biblatex.
In the attachment ist all needed example stuff.
from biblatex.
I can't see any attachment? Does the SE question above help?
from biblatex.
This is quite strange. Next try. I will post the file contents directly
to the mail.
pheads.tex:
\documentclass[fontsize=12pt,paper=a4]{scrreprt}
\usepackage[markuppercase]{scrpage2}
\usepackage[ngerman]{babel}
\title{Demotitel}
\author{demoauthor}
\date{}
\usepackage[backend=bibtex8]{biblatex}
\addbibresource{./simple.bib}
\KOMAoptions{numbers=noenddot}
\ihead[]{\headmark}
\chead[]{}
\ohead[\pagemark]{\pagemark}
\begin{document}
\automark[chapter]{chapter}
\pagestyle{scrheadings}
\maketitle
\tableofcontents
\chapter{Ein Kapitel\dots}
Bla
\newpage
Bli
\chapter{Noch eins.}
Tri Tra
\newpage
Trulala
\nocite{*}
\printbibliography
\newpage
Ende
\end{document}
sample.bib:
@book{ AigZieg:04,
title = "Das Buch der der Beweise",
author = {Martin Aigner and G{"u}nter M. Ziegler},
publisher = "Springer",
address = "Berlin, Heidelberg",
edition = "zweite",
year = "2004",
isbn = "3-540-40185-7",
key = "Aigner"
}
The problem is here, that the scrpage2-package from Koma-script has it's
own mechanism for typesetting uppercase headings. I haven't any
practible idea for simulating it with /defbibheading.
Greets.
from biblatex.
Since this header is formatted by a package and not the document class, \defbibheading
is probably the way to go. From scrpage2.sty
casing is done with \MakeMarkcase
. Its definition depends on the options passed to scrpage2
. Does the following you the desired result?
\defbibheading{bibliography}[\bibname]{%
\chapter*{#1}%
\markboth{\MakeMarkcase{#1}}{\MakeMarkcase{#1}}}
from biblatex.
Yes, it does. Thanks for helping. It would be nice, if this could be the
default behaviour of biblatex when scrpage2 is also loaded.
from biblatex.
Accounting for package-based formatting (versus class-based) opens up a can of worms IMO. \defbibheading
does a fine job handling this case. I'll leave it up to Philip to decide.
from biblatex.
I think this might be ok - in fact biblatex.def already does this for many Koma styles anyway. I'll have a look.
from biblatex.
Yeah, all the KOMA-Script classes are already covered. I took a quick look, but I couldn't find a tidy solution. scrpage2
can be used with any document class. So I guess you could move the existing code to \AtBeginDocument
and then condition on \@ifpackageloaded{scrpage2}
. Otherwise you can define \MakeMarkcase
provisionally and then use it throughout the existing header definitions.
from biblatex.
Additional comment:
\documentclass{scrreprt}
\usepackage[markuppercase]{scrpage2}
should rather be
\documentclass{scrreprt}
\usepackage[standardstyle]{scrpage2}
from biblatex.
Hi,
the standardstyle-option for scrpage2 is only for use with
non-KOMA-classes, with scrartcl it doesn't work in the correct way
(scrguide S.251).
from biblatex.
I don’t think so. The standardstyle
option is for emulating the page styles of the standard document classes, regardless of the document class that is actually used. On the other hand, the markuppercase
option only indicates to the scrpage2
package that the used document class capitalizes the running header. To quote the KOMA-Script guide:
Option
markuppercase
showsscrpage2
that the document class uses uppercase letters. […]; thus, unexpected effects may occur if the given option does not match the actual behaviour of the document class.
from biblatex.
Not scrpage2 or scrbook acts strange, biblatex does. It doesn't generate
any bibliography , if standardstyle is used.
Test source is sent in a former post to this issue.
The given cite belongs to non-Koma-classes, for Koma-classes it's better
to use markuppercase, but this doesn't solve the main problem.
Lieke mentioned in this thread
(https://groups.google.com/group/de.comp.text.tex/browse_thread/thread/ed224b143467c4e5/233a90b4061f01b0?hl=deéa90b4061f01b0
) the problem seems to be, that biblatex does not set bib@heading as
default for it's headings, which would make all do-it-yourself-solutions
with \defbibheading unneeded.
from biblatex.
Audrey - what do you think about this bib@heading issue?
from biblatex.
The aforementioned thread on de.comp.text.tex is not related to the scrpage2
package. It deals with the ability of biblatex to recognize the KOMA-Script class option bibliography=totoc
(and its aliases toc=bibliography
, toc=bib
). Currently, bibliography=totoc
is only taken into account by biblatex if it appears in the optional argument of \documentclass
. If it appears in the argument of \KOMAoptions
it is ignored.
from biblatex.
Thanks for clarifying. PL states this point in the manual. It seems he decided to leave bibliography header definitions at biblatex load time and base these only on the document class options.
A provisional \MakeMarkcase
would cover off scrpage2
, but this doesn't account for headers customized via other methods including \KOMAoptions
. Certainly there are better things to do than trying to support all of these cases. I think it is reasonable to ask users to cook up their own \defbibheading
any time they customize headers or sectioning after class load time.
from biblatex.
I think so, too.
from biblatex.
This seems sensible to me - what are the OP's feeling on this?
from biblatex.
Another case turned up recently on TeX.SE with \pagestyle{myheadings}
. My first comment fixes the OP's issue. We could be more explicit in the manual about the need for \defbibheading
with changes to headers after class load time. Aside from that I think this should be closed.
from biblatex.
A little late information on the subject: section
and addsec
set up the headers on their own, just section*
needs the mark mechanism. Every KOMA class loads package tocbasic
which defines MakeMarkcase
. This isn't a matter of scrpage2
(obsolete by now).
\documentclass{article}
\usepackage{tocbasic}
\begin{document}
\MakeMarkcase{Something}
\end{document}
from biblatex.
Related Issues (20)
- Rollback availability HOT 2
- Typo in the documentation HOT 1
- Typo in documentation HOT 3
- Error: Command \cite already defined. HOT 6
- Inherit data annotations with crossref (feature request) HOT 14
- Request: filter \nocite{*} like \printbibliography
- ibid mechanism with multicite commands HOT 4
- Typo in doc
- biblatex tries to patch no longer existing ifthenelse commands HOT 5
- Wrong translation in Spanish HOT 3
- `autolang=hyphen` plus `related` not working HOT 4
- Backref in color? HOT 5
- Package biblatex Warning: File 'brazilian-abnt-abnt.lbx' not found! HOT 2
- Typo in the documentation
- Italian localization: ordinal number in long date format HOT 10
- Can't compile with quantumarticle.cls HOT 5
- How to transform newcomand \bcite{ref1,ref2} to \cite{ref1:TR,ref2:TR} HOT 2
- Localised url/urlfrom ignored as field format url hardcodes \mkbibacro{url} HOT 6
- `relatedtype`: `translationas` or `translatedas`? HOT 1
- Biblatex fails to detect languages loaded with `\babelprovide` HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from biblatex.