Avoiding [SS…] in German bibliographies
Consider the following particular references in your bibliography file:
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
or
@inproceedings{Scott_Strachey_71,
Author = {Dana Stewart Scott and Christopher S. Strachey},
Booktitle = {Symposium on Computers and Automata},
Editor = {J. Fox},
Language = {USenglish},
Mon = aug,
Organization = {Polytechnic Institute of Brooklyn},
Pages = {19--46},
Publisher = wil,
Series = {Microwave Institute Symposia Series},
Title = {Towards a Mathematical Semantics for Computer Languages},
Volume = 21,
Year = 1971}
With RequirePackage{natbib}
, usepackage{babelbib}
, and bibliographystyle{babalpha-fl}
(but no jurabib
or cite
) the references to these entries are abbreviated as [SS17] and [SS71]. Let's assume you wish to avoid abbreviatations such as SS (since they might remind some readers of Schutzstaffel). How do you tell LaTeX+Bibtex to produce [ScSu17] and [ScSt71] (or something else) instead?
bibtex
|
show 5 more comments
Consider the following particular references in your bibliography file:
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
or
@inproceedings{Scott_Strachey_71,
Author = {Dana Stewart Scott and Christopher S. Strachey},
Booktitle = {Symposium on Computers and Automata},
Editor = {J. Fox},
Language = {USenglish},
Mon = aug,
Organization = {Polytechnic Institute of Brooklyn},
Pages = {19--46},
Publisher = wil,
Series = {Microwave Institute Symposia Series},
Title = {Towards a Mathematical Semantics for Computer Languages},
Volume = 21,
Year = 1971}
With RequirePackage{natbib}
, usepackage{babelbib}
, and bibliographystyle{babalpha-fl}
(but no jurabib
or cite
) the references to these entries are abbreviated as [SS17] and [SS71]. Let's assume you wish to avoid abbreviatations such as SS (since they might remind some readers of Schutzstaffel). How do you tell LaTeX+Bibtex to produce [ScSu17] and [ScSt71] (or something else) instead?
bibtex
3
Do you avoid double sums and integrals too?
– st.vit
Jul 16 '18 at 15:39
1
@st.vir I doubt that anyone in their right mind would really object to double integrals and sums. Still, there are lots of envious folks around trying to make your life hard by pinpointing to an abbreviation such as [SS]. So, let's not feed the bears.
– user0
Jul 16 '18 at 18:34
I would think of "Sommersemester", when reading, SS.... In fact, WS , SS followed by year are very common German shorthands for winter and summer semester in the accademic field.
– AlexG
Feb 1 at 21:57
@AlexG But only in certain federal states of Germany. In certain other federal states, they use SoSe instead of SS for Sommersemester.
– user0
Feb 1 at 22:07
Never seen SoSe. Maybe I am too old.
– AlexG
Feb 1 at 22:25
|
show 5 more comments
Consider the following particular references in your bibliography file:
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
or
@inproceedings{Scott_Strachey_71,
Author = {Dana Stewart Scott and Christopher S. Strachey},
Booktitle = {Symposium on Computers and Automata},
Editor = {J. Fox},
Language = {USenglish},
Mon = aug,
Organization = {Polytechnic Institute of Brooklyn},
Pages = {19--46},
Publisher = wil,
Series = {Microwave Institute Symposia Series},
Title = {Towards a Mathematical Semantics for Computer Languages},
Volume = 21,
Year = 1971}
With RequirePackage{natbib}
, usepackage{babelbib}
, and bibliographystyle{babalpha-fl}
(but no jurabib
or cite
) the references to these entries are abbreviated as [SS17] and [SS71]. Let's assume you wish to avoid abbreviatations such as SS (since they might remind some readers of Schutzstaffel). How do you tell LaTeX+Bibtex to produce [ScSu17] and [ScSt71] (or something else) instead?
bibtex
Consider the following particular references in your bibliography file:
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
or
@inproceedings{Scott_Strachey_71,
Author = {Dana Stewart Scott and Christopher S. Strachey},
Booktitle = {Symposium on Computers and Automata},
Editor = {J. Fox},
Language = {USenglish},
Mon = aug,
Organization = {Polytechnic Institute of Brooklyn},
Pages = {19--46},
Publisher = wil,
Series = {Microwave Institute Symposia Series},
Title = {Towards a Mathematical Semantics for Computer Languages},
Volume = 21,
Year = 1971}
With RequirePackage{natbib}
, usepackage{babelbib}
, and bibliographystyle{babalpha-fl}
(but no jurabib
or cite
) the references to these entries are abbreviated as [SS17] and [SS71]. Let's assume you wish to avoid abbreviatations such as SS (since they might remind some readers of Schutzstaffel). How do you tell LaTeX+Bibtex to produce [ScSu17] and [ScSt71] (or something else) instead?
bibtex
bibtex
edited Jul 16 '18 at 13:09
user0
asked Jul 16 '18 at 13:01
user0user0
53421
53421
3
Do you avoid double sums and integrals too?
– st.vit
Jul 16 '18 at 15:39
1
@st.vir I doubt that anyone in their right mind would really object to double integrals and sums. Still, there are lots of envious folks around trying to make your life hard by pinpointing to an abbreviation such as [SS]. So, let's not feed the bears.
– user0
Jul 16 '18 at 18:34
I would think of "Sommersemester", when reading, SS.... In fact, WS , SS followed by year are very common German shorthands for winter and summer semester in the accademic field.
– AlexG
Feb 1 at 21:57
@AlexG But only in certain federal states of Germany. In certain other federal states, they use SoSe instead of SS for Sommersemester.
– user0
Feb 1 at 22:07
Never seen SoSe. Maybe I am too old.
– AlexG
Feb 1 at 22:25
|
show 5 more comments
3
Do you avoid double sums and integrals too?
– st.vit
Jul 16 '18 at 15:39
1
@st.vir I doubt that anyone in their right mind would really object to double integrals and sums. Still, there are lots of envious folks around trying to make your life hard by pinpointing to an abbreviation such as [SS]. So, let's not feed the bears.
– user0
Jul 16 '18 at 18:34
I would think of "Sommersemester", when reading, SS.... In fact, WS , SS followed by year are very common German shorthands for winter and summer semester in the accademic field.
– AlexG
Feb 1 at 21:57
@AlexG But only in certain federal states of Germany. In certain other federal states, they use SoSe instead of SS for Sommersemester.
– user0
Feb 1 at 22:07
Never seen SoSe. Maybe I am too old.
– AlexG
Feb 1 at 22:25
3
3
Do you avoid double sums and integrals too?
– st.vit
Jul 16 '18 at 15:39
Do you avoid double sums and integrals too?
– st.vit
Jul 16 '18 at 15:39
1
1
@st.vir I doubt that anyone in their right mind would really object to double integrals and sums. Still, there are lots of envious folks around trying to make your life hard by pinpointing to an abbreviation such as [SS]. So, let's not feed the bears.
– user0
Jul 16 '18 at 18:34
@st.vir I doubt that anyone in their right mind would really object to double integrals and sums. Still, there are lots of envious folks around trying to make your life hard by pinpointing to an abbreviation such as [SS]. So, let's not feed the bears.
– user0
Jul 16 '18 at 18:34
I would think of "Sommersemester", when reading, SS.... In fact, WS , SS followed by year are very common German shorthands for winter and summer semester in the accademic field.
– AlexG
Feb 1 at 21:57
I would think of "Sommersemester", when reading, SS.... In fact, WS , SS followed by year are very common German shorthands for winter and summer semester in the accademic field.
– AlexG
Feb 1 at 21:57
@AlexG But only in certain federal states of Germany. In certain other federal states, they use SoSe instead of SS for Sommersemester.
– user0
Feb 1 at 22:07
@AlexG But only in certain federal states of Germany. In certain other federal states, they use SoSe instead of SS for Sommersemester.
– user0
Feb 1 at 22:07
Never seen SoSe. Maybe I am too old.
– AlexG
Feb 1 at 22:25
Never seen SoSe. Maybe I am too old.
– AlexG
Feb 1 at 22:25
|
show 5 more comments
2 Answers
2
active
oldest
votes
The easiest way is not using an “alpha” bib style. They used to be handy in the olden times when you didn't know the order of bibliographic items in typewritten manuscripts.
But there's a way. I added also two fake entries in order to show the collation order is correct.
begin{filecontents*}{jobname.bib}
@article{a,
author={Sa, X.},
title={Title},
journal={Journal},
year=2017,
}
@article{b,
author={St, X.},
title={Title},
journal={Journal},
year=2017,
}
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
@misc{SchwaberSutherland-DerScrumGuide-bis,
author = {Ken {relax Sc}hwaber and Jeff {relax Su}therland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
end{filecontents*}
documentclass{article}
usepackage[ngerman,english]{babel}
usepackage{url}
usepackage{babelbib}
bibliographystyle{babalpha-fl}
begin{document}
cite{SchwaberSutherland-DerScrumGuide}
cite{SchwaberSutherland-DerScrumGuide-bis}
cite{a,b}
bibliography{jobname}
end{document}
The filecontents*
environment is just to make the example self-contained. I doubt that loading natbib
along with babelbib
makes sense.
Thank you. Usingbabalpha-fl
is legacy LaTeX code. Still, I'll look into the possibilities of replacing it. (So, suggestions ofbiber
styles producing output as similar to babalpha-fl as possible are welcome.) As far as natbib+babelbib is concerned, the former is for scientific formatting (and is the choice of publisher, which is difficult to override by something else unless the output is exactly the same), while the latter is to allow for multiple languages in the bibliography (which improves typesetting in the presence ofmicrotype
and hyphenation in the presence ofbabel
).
– user0
Jul 16 '18 at 15:20
What do you think of @moewe 's suggestion?
– user0
Jul 16 '18 at 15:21
@user49915 Nice, but difficult to maintain. I still think that alpha styles are a thing of the past.
– egreg
Jul 16 '18 at 15:33
add a comment |
With a bit of work babalpha-fl.bst
can be taught to detect historically problematic abbreviations in labels and try to work around it.
I'm working under the assumption that only certain two letter abbreviations are problematic (the example has "SS" and "SA" hard-coded, but you can add "HH", "HJ", "NSDAP", you name it, I have not added anything to ban entries from 1988 and 2018, though) and that using two letters of each author name instead can mitigate the problem.
As mentioned above, you will have to modify the .bst
file. To do that proceed as follows
- Locate
babalpha-fl.bst
on your machine for example by typingkpsewhich babalpha-fl.bst
. - Copy the file to a place where LaTeX can find it (https://texfaq.org/FAQ-inst-wlcf), the directory of your document will do just fine, and rename it to
babalpha-fl-gs.bst
, say. Note that the license ofbabalpha-fl.bst
requires you to change the name of the file if you modify it. - Open
babalpha-fl-gs.bst
and insert a header with the new file name and the current date
Find
FUNCTION {format.lab.names}
and insert
% new function, essentially a copy of format.lab.names
% that produces two-letter labels from each name
FUNCTION {format.lab.names.safe}
{ 's :=
s num.names$ 'numnames :=
numnames #1 >
{ numnames #4 >
{ #3 'namesleft := }
{ numnames 'namesleft := }
if$
#1 'nameptr :=
""
{ namesleft #0 > }
{ nameptr numnames =
{ s nameptr "{ff }{vv }{ll}{ jj}" format.name$ "others" =
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
{ s nameptr "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s nameptr "{ll}" format.name$ #2 text.prefix$ }
'skip$
if$
*
}
if$
}
{ s nameptr "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s nameptr "{ll}" format.name$ #2 text.prefix$ }
'skip$
if$
*
}
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
numnames #4 >
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
'skip$
if$
}
{ s #1 "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s #1 "{ll}" format.name$ #3 text.prefix$ }
'skip$
if$
}
if$
}
before it.
Replace
FUNCTION {format.lab.names}
with
% slightly modified from original to detect problematic abbreviations
FUNCTION {format.lab.names}
{ 's :=
s num.names$ 'numnames :=
numnames #1 >
{ numnames #4 >
{ #3 'namesleft := }
{ numnames 'namesleft := }
if$
#1 'nameptr :=
""
{ namesleft #0 > }
{ nameptr numnames =
{ s nameptr "{ff }{vv }{ll}{ jj}" format.name$ "others" =
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
{ s nameptr "{v{}}{l{}}" format.name$ * }
if$
}
{ s nameptr "{v{}}{l{}}" format.name$ * }
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
numnames #4 >
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
'skip$
if$
% this block is new
duplicate$ "SS" =
{ pop$
s format.lab.names.safe }
{ duplicate$ "SA" =
{ pop$
s format.lab.names.safe }
'skip$
if$
}
if$
}
{ s #1 "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s #1 "{ll}" format.name$ #3 text.prefix$ }
'skip$
if$
}
if$
}
Use
bibliographystyle{babalpha-fl-gs}
instead ofbibliographystyle{babalpha-fl}
in your document
Alternatively you can get babalpha-fl-gs.bst
from https://gist.github.com/moewew/158481168f4a2135764f96fc608a1998
documentclass[ngerman]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage{babelbib}
usepackage{hyperref}
bibliographystyle{babalpha-fl-gs}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide},
}
end{filecontents}
begin{document}
cite{SchwaberSutherland-DerScrumGuide}
bibliography{jobname}
end{document}
Works like a charm, thank you! Regarding the maturity of your code, would you suggest that it is used in a production environment, or would you suggest that additional testing be done?
– user0
Jul 16 '18 at 15:22
What do you think of @egreg 's suggestion?
– user0
Jul 16 '18 at 15:26
@user49915 It's a bit boring, isn't it? ;-) It has the huge advantage of not requiring changes to.bst
files which can be a plus if you are not into this sort of thing (and might be a plus when you have to share your work with others or submit it to a publisher - though publishers usually want the.bbl
file in which case a modified.bst
file does not really matter). I must say that I mainly answered because I liked the challenge, not because I thought this would be particularly useful. ...
– moewe
Jul 16 '18 at 15:35
... But of course my solution is not supposed to require manual intervention which is nice in case you want to re-use the.bib
file for something else. It was a similar situation here.
– moewe
Jul 16 '18 at 15:35
@user49915 I only just saw your comment about code maturity. I'm quite confident that the code as posted works as intended. But of course I can't guarantee that everything works as desired so a bit of caution is always advised.
– moewe
Jul 16 '18 at 15:43
|
show 12 more comments
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
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f441864%2favoiding-ss-in-german-bibliographies%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The easiest way is not using an “alpha” bib style. They used to be handy in the olden times when you didn't know the order of bibliographic items in typewritten manuscripts.
But there's a way. I added also two fake entries in order to show the collation order is correct.
begin{filecontents*}{jobname.bib}
@article{a,
author={Sa, X.},
title={Title},
journal={Journal},
year=2017,
}
@article{b,
author={St, X.},
title={Title},
journal={Journal},
year=2017,
}
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
@misc{SchwaberSutherland-DerScrumGuide-bis,
author = {Ken {relax Sc}hwaber and Jeff {relax Su}therland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
end{filecontents*}
documentclass{article}
usepackage[ngerman,english]{babel}
usepackage{url}
usepackage{babelbib}
bibliographystyle{babalpha-fl}
begin{document}
cite{SchwaberSutherland-DerScrumGuide}
cite{SchwaberSutherland-DerScrumGuide-bis}
cite{a,b}
bibliography{jobname}
end{document}
The filecontents*
environment is just to make the example self-contained. I doubt that loading natbib
along with babelbib
makes sense.
Thank you. Usingbabalpha-fl
is legacy LaTeX code. Still, I'll look into the possibilities of replacing it. (So, suggestions ofbiber
styles producing output as similar to babalpha-fl as possible are welcome.) As far as natbib+babelbib is concerned, the former is for scientific formatting (and is the choice of publisher, which is difficult to override by something else unless the output is exactly the same), while the latter is to allow for multiple languages in the bibliography (which improves typesetting in the presence ofmicrotype
and hyphenation in the presence ofbabel
).
– user0
Jul 16 '18 at 15:20
What do you think of @moewe 's suggestion?
– user0
Jul 16 '18 at 15:21
@user49915 Nice, but difficult to maintain. I still think that alpha styles are a thing of the past.
– egreg
Jul 16 '18 at 15:33
add a comment |
The easiest way is not using an “alpha” bib style. They used to be handy in the olden times when you didn't know the order of bibliographic items in typewritten manuscripts.
But there's a way. I added also two fake entries in order to show the collation order is correct.
begin{filecontents*}{jobname.bib}
@article{a,
author={Sa, X.},
title={Title},
journal={Journal},
year=2017,
}
@article{b,
author={St, X.},
title={Title},
journal={Journal},
year=2017,
}
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
@misc{SchwaberSutherland-DerScrumGuide-bis,
author = {Ken {relax Sc}hwaber and Jeff {relax Su}therland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
end{filecontents*}
documentclass{article}
usepackage[ngerman,english]{babel}
usepackage{url}
usepackage{babelbib}
bibliographystyle{babalpha-fl}
begin{document}
cite{SchwaberSutherland-DerScrumGuide}
cite{SchwaberSutherland-DerScrumGuide-bis}
cite{a,b}
bibliography{jobname}
end{document}
The filecontents*
environment is just to make the example self-contained. I doubt that loading natbib
along with babelbib
makes sense.
Thank you. Usingbabalpha-fl
is legacy LaTeX code. Still, I'll look into the possibilities of replacing it. (So, suggestions ofbiber
styles producing output as similar to babalpha-fl as possible are welcome.) As far as natbib+babelbib is concerned, the former is for scientific formatting (and is the choice of publisher, which is difficult to override by something else unless the output is exactly the same), while the latter is to allow for multiple languages in the bibliography (which improves typesetting in the presence ofmicrotype
and hyphenation in the presence ofbabel
).
– user0
Jul 16 '18 at 15:20
What do you think of @moewe 's suggestion?
– user0
Jul 16 '18 at 15:21
@user49915 Nice, but difficult to maintain. I still think that alpha styles are a thing of the past.
– egreg
Jul 16 '18 at 15:33
add a comment |
The easiest way is not using an “alpha” bib style. They used to be handy in the olden times when you didn't know the order of bibliographic items in typewritten manuscripts.
But there's a way. I added also two fake entries in order to show the collation order is correct.
begin{filecontents*}{jobname.bib}
@article{a,
author={Sa, X.},
title={Title},
journal={Journal},
year=2017,
}
@article{b,
author={St, X.},
title={Title},
journal={Journal},
year=2017,
}
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
@misc{SchwaberSutherland-DerScrumGuide-bis,
author = {Ken {relax Sc}hwaber and Jeff {relax Su}therland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
end{filecontents*}
documentclass{article}
usepackage[ngerman,english]{babel}
usepackage{url}
usepackage{babelbib}
bibliographystyle{babalpha-fl}
begin{document}
cite{SchwaberSutherland-DerScrumGuide}
cite{SchwaberSutherland-DerScrumGuide-bis}
cite{a,b}
bibliography{jobname}
end{document}
The filecontents*
environment is just to make the example self-contained. I doubt that loading natbib
along with babelbib
makes sense.
The easiest way is not using an “alpha” bib style. They used to be handy in the olden times when you didn't know the order of bibliographic items in typewritten manuscripts.
But there's a way. I added also two fake entries in order to show the collation order is correct.
begin{filecontents*}{jobname.bib}
@article{a,
author={Sa, X.},
title={Title},
journal={Journal},
year=2017,
}
@article{b,
author={St, X.},
title={Title},
journal={Journal},
year=2017,
}
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
@misc{SchwaberSutherland-DerScrumGuide-bis,
author = {Ken {relax Sc}hwaber and Jeff {relax Su}therland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide}
}
end{filecontents*}
documentclass{article}
usepackage[ngerman,english]{babel}
usepackage{url}
usepackage{babelbib}
bibliographystyle{babalpha-fl}
begin{document}
cite{SchwaberSutherland-DerScrumGuide}
cite{SchwaberSutherland-DerScrumGuide-bis}
cite{a,b}
bibliography{jobname}
end{document}
The filecontents*
environment is just to make the example self-contained. I doubt that loading natbib
along with babelbib
makes sense.
answered Jul 16 '18 at 14:03
egregegreg
718k8719053202
718k8719053202
Thank you. Usingbabalpha-fl
is legacy LaTeX code. Still, I'll look into the possibilities of replacing it. (So, suggestions ofbiber
styles producing output as similar to babalpha-fl as possible are welcome.) As far as natbib+babelbib is concerned, the former is for scientific formatting (and is the choice of publisher, which is difficult to override by something else unless the output is exactly the same), while the latter is to allow for multiple languages in the bibliography (which improves typesetting in the presence ofmicrotype
and hyphenation in the presence ofbabel
).
– user0
Jul 16 '18 at 15:20
What do you think of @moewe 's suggestion?
– user0
Jul 16 '18 at 15:21
@user49915 Nice, but difficult to maintain. I still think that alpha styles are a thing of the past.
– egreg
Jul 16 '18 at 15:33
add a comment |
Thank you. Usingbabalpha-fl
is legacy LaTeX code. Still, I'll look into the possibilities of replacing it. (So, suggestions ofbiber
styles producing output as similar to babalpha-fl as possible are welcome.) As far as natbib+babelbib is concerned, the former is for scientific formatting (and is the choice of publisher, which is difficult to override by something else unless the output is exactly the same), while the latter is to allow for multiple languages in the bibliography (which improves typesetting in the presence ofmicrotype
and hyphenation in the presence ofbabel
).
– user0
Jul 16 '18 at 15:20
What do you think of @moewe 's suggestion?
– user0
Jul 16 '18 at 15:21
@user49915 Nice, but difficult to maintain. I still think that alpha styles are a thing of the past.
– egreg
Jul 16 '18 at 15:33
Thank you. Using
babalpha-fl
is legacy LaTeX code. Still, I'll look into the possibilities of replacing it. (So, suggestions of biber
styles producing output as similar to babalpha-fl as possible are welcome.) As far as natbib+babelbib is concerned, the former is for scientific formatting (and is the choice of publisher, which is difficult to override by something else unless the output is exactly the same), while the latter is to allow for multiple languages in the bibliography (which improves typesetting in the presence of microtype
and hyphenation in the presence of babel
).– user0
Jul 16 '18 at 15:20
Thank you. Using
babalpha-fl
is legacy LaTeX code. Still, I'll look into the possibilities of replacing it. (So, suggestions of biber
styles producing output as similar to babalpha-fl as possible are welcome.) As far as natbib+babelbib is concerned, the former is for scientific formatting (and is the choice of publisher, which is difficult to override by something else unless the output is exactly the same), while the latter is to allow for multiple languages in the bibliography (which improves typesetting in the presence of microtype
and hyphenation in the presence of babel
).– user0
Jul 16 '18 at 15:20
What do you think of @moewe 's suggestion?
– user0
Jul 16 '18 at 15:21
What do you think of @moewe 's suggestion?
– user0
Jul 16 '18 at 15:21
@user49915 Nice, but difficult to maintain. I still think that alpha styles are a thing of the past.
– egreg
Jul 16 '18 at 15:33
@user49915 Nice, but difficult to maintain. I still think that alpha styles are a thing of the past.
– egreg
Jul 16 '18 at 15:33
add a comment |
With a bit of work babalpha-fl.bst
can be taught to detect historically problematic abbreviations in labels and try to work around it.
I'm working under the assumption that only certain two letter abbreviations are problematic (the example has "SS" and "SA" hard-coded, but you can add "HH", "HJ", "NSDAP", you name it, I have not added anything to ban entries from 1988 and 2018, though) and that using two letters of each author name instead can mitigate the problem.
As mentioned above, you will have to modify the .bst
file. To do that proceed as follows
- Locate
babalpha-fl.bst
on your machine for example by typingkpsewhich babalpha-fl.bst
. - Copy the file to a place where LaTeX can find it (https://texfaq.org/FAQ-inst-wlcf), the directory of your document will do just fine, and rename it to
babalpha-fl-gs.bst
, say. Note that the license ofbabalpha-fl.bst
requires you to change the name of the file if you modify it. - Open
babalpha-fl-gs.bst
and insert a header with the new file name and the current date
Find
FUNCTION {format.lab.names}
and insert
% new function, essentially a copy of format.lab.names
% that produces two-letter labels from each name
FUNCTION {format.lab.names.safe}
{ 's :=
s num.names$ 'numnames :=
numnames #1 >
{ numnames #4 >
{ #3 'namesleft := }
{ numnames 'namesleft := }
if$
#1 'nameptr :=
""
{ namesleft #0 > }
{ nameptr numnames =
{ s nameptr "{ff }{vv }{ll}{ jj}" format.name$ "others" =
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
{ s nameptr "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s nameptr "{ll}" format.name$ #2 text.prefix$ }
'skip$
if$
*
}
if$
}
{ s nameptr "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s nameptr "{ll}" format.name$ #2 text.prefix$ }
'skip$
if$
*
}
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
numnames #4 >
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
'skip$
if$
}
{ s #1 "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s #1 "{ll}" format.name$ #3 text.prefix$ }
'skip$
if$
}
if$
}
before it.
Replace
FUNCTION {format.lab.names}
with
% slightly modified from original to detect problematic abbreviations
FUNCTION {format.lab.names}
{ 's :=
s num.names$ 'numnames :=
numnames #1 >
{ numnames #4 >
{ #3 'namesleft := }
{ numnames 'namesleft := }
if$
#1 'nameptr :=
""
{ namesleft #0 > }
{ nameptr numnames =
{ s nameptr "{ff }{vv }{ll}{ jj}" format.name$ "others" =
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
{ s nameptr "{v{}}{l{}}" format.name$ * }
if$
}
{ s nameptr "{v{}}{l{}}" format.name$ * }
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
numnames #4 >
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
'skip$
if$
% this block is new
duplicate$ "SS" =
{ pop$
s format.lab.names.safe }
{ duplicate$ "SA" =
{ pop$
s format.lab.names.safe }
'skip$
if$
}
if$
}
{ s #1 "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s #1 "{ll}" format.name$ #3 text.prefix$ }
'skip$
if$
}
if$
}
Use
bibliographystyle{babalpha-fl-gs}
instead ofbibliographystyle{babalpha-fl}
in your document
Alternatively you can get babalpha-fl-gs.bst
from https://gist.github.com/moewew/158481168f4a2135764f96fc608a1998
documentclass[ngerman]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage{babelbib}
usepackage{hyperref}
bibliographystyle{babalpha-fl-gs}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide},
}
end{filecontents}
begin{document}
cite{SchwaberSutherland-DerScrumGuide}
bibliography{jobname}
end{document}
Works like a charm, thank you! Regarding the maturity of your code, would you suggest that it is used in a production environment, or would you suggest that additional testing be done?
– user0
Jul 16 '18 at 15:22
What do you think of @egreg 's suggestion?
– user0
Jul 16 '18 at 15:26
@user49915 It's a bit boring, isn't it? ;-) It has the huge advantage of not requiring changes to.bst
files which can be a plus if you are not into this sort of thing (and might be a plus when you have to share your work with others or submit it to a publisher - though publishers usually want the.bbl
file in which case a modified.bst
file does not really matter). I must say that I mainly answered because I liked the challenge, not because I thought this would be particularly useful. ...
– moewe
Jul 16 '18 at 15:35
... But of course my solution is not supposed to require manual intervention which is nice in case you want to re-use the.bib
file for something else. It was a similar situation here.
– moewe
Jul 16 '18 at 15:35
@user49915 I only just saw your comment about code maturity. I'm quite confident that the code as posted works as intended. But of course I can't guarantee that everything works as desired so a bit of caution is always advised.
– moewe
Jul 16 '18 at 15:43
|
show 12 more comments
With a bit of work babalpha-fl.bst
can be taught to detect historically problematic abbreviations in labels and try to work around it.
I'm working under the assumption that only certain two letter abbreviations are problematic (the example has "SS" and "SA" hard-coded, but you can add "HH", "HJ", "NSDAP", you name it, I have not added anything to ban entries from 1988 and 2018, though) and that using two letters of each author name instead can mitigate the problem.
As mentioned above, you will have to modify the .bst
file. To do that proceed as follows
- Locate
babalpha-fl.bst
on your machine for example by typingkpsewhich babalpha-fl.bst
. - Copy the file to a place where LaTeX can find it (https://texfaq.org/FAQ-inst-wlcf), the directory of your document will do just fine, and rename it to
babalpha-fl-gs.bst
, say. Note that the license ofbabalpha-fl.bst
requires you to change the name of the file if you modify it. - Open
babalpha-fl-gs.bst
and insert a header with the new file name and the current date
Find
FUNCTION {format.lab.names}
and insert
% new function, essentially a copy of format.lab.names
% that produces two-letter labels from each name
FUNCTION {format.lab.names.safe}
{ 's :=
s num.names$ 'numnames :=
numnames #1 >
{ numnames #4 >
{ #3 'namesleft := }
{ numnames 'namesleft := }
if$
#1 'nameptr :=
""
{ namesleft #0 > }
{ nameptr numnames =
{ s nameptr "{ff }{vv }{ll}{ jj}" format.name$ "others" =
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
{ s nameptr "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s nameptr "{ll}" format.name$ #2 text.prefix$ }
'skip$
if$
*
}
if$
}
{ s nameptr "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s nameptr "{ll}" format.name$ #2 text.prefix$ }
'skip$
if$
*
}
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
numnames #4 >
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
'skip$
if$
}
{ s #1 "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s #1 "{ll}" format.name$ #3 text.prefix$ }
'skip$
if$
}
if$
}
before it.
Replace
FUNCTION {format.lab.names}
with
% slightly modified from original to detect problematic abbreviations
FUNCTION {format.lab.names}
{ 's :=
s num.names$ 'numnames :=
numnames #1 >
{ numnames #4 >
{ #3 'namesleft := }
{ numnames 'namesleft := }
if$
#1 'nameptr :=
""
{ namesleft #0 > }
{ nameptr numnames =
{ s nameptr "{ff }{vv }{ll}{ jj}" format.name$ "others" =
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
{ s nameptr "{v{}}{l{}}" format.name$ * }
if$
}
{ s nameptr "{v{}}{l{}}" format.name$ * }
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
numnames #4 >
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
'skip$
if$
% this block is new
duplicate$ "SS" =
{ pop$
s format.lab.names.safe }
{ duplicate$ "SA" =
{ pop$
s format.lab.names.safe }
'skip$
if$
}
if$
}
{ s #1 "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s #1 "{ll}" format.name$ #3 text.prefix$ }
'skip$
if$
}
if$
}
Use
bibliographystyle{babalpha-fl-gs}
instead ofbibliographystyle{babalpha-fl}
in your document
Alternatively you can get babalpha-fl-gs.bst
from https://gist.github.com/moewew/158481168f4a2135764f96fc608a1998
documentclass[ngerman]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage{babelbib}
usepackage{hyperref}
bibliographystyle{babalpha-fl-gs}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide},
}
end{filecontents}
begin{document}
cite{SchwaberSutherland-DerScrumGuide}
bibliography{jobname}
end{document}
Works like a charm, thank you! Regarding the maturity of your code, would you suggest that it is used in a production environment, or would you suggest that additional testing be done?
– user0
Jul 16 '18 at 15:22
What do you think of @egreg 's suggestion?
– user0
Jul 16 '18 at 15:26
@user49915 It's a bit boring, isn't it? ;-) It has the huge advantage of not requiring changes to.bst
files which can be a plus if you are not into this sort of thing (and might be a plus when you have to share your work with others or submit it to a publisher - though publishers usually want the.bbl
file in which case a modified.bst
file does not really matter). I must say that I mainly answered because I liked the challenge, not because I thought this would be particularly useful. ...
– moewe
Jul 16 '18 at 15:35
... But of course my solution is not supposed to require manual intervention which is nice in case you want to re-use the.bib
file for something else. It was a similar situation here.
– moewe
Jul 16 '18 at 15:35
@user49915 I only just saw your comment about code maturity. I'm quite confident that the code as posted works as intended. But of course I can't guarantee that everything works as desired so a bit of caution is always advised.
– moewe
Jul 16 '18 at 15:43
|
show 12 more comments
With a bit of work babalpha-fl.bst
can be taught to detect historically problematic abbreviations in labels and try to work around it.
I'm working under the assumption that only certain two letter abbreviations are problematic (the example has "SS" and "SA" hard-coded, but you can add "HH", "HJ", "NSDAP", you name it, I have not added anything to ban entries from 1988 and 2018, though) and that using two letters of each author name instead can mitigate the problem.
As mentioned above, you will have to modify the .bst
file. To do that proceed as follows
- Locate
babalpha-fl.bst
on your machine for example by typingkpsewhich babalpha-fl.bst
. - Copy the file to a place where LaTeX can find it (https://texfaq.org/FAQ-inst-wlcf), the directory of your document will do just fine, and rename it to
babalpha-fl-gs.bst
, say. Note that the license ofbabalpha-fl.bst
requires you to change the name of the file if you modify it. - Open
babalpha-fl-gs.bst
and insert a header with the new file name and the current date
Find
FUNCTION {format.lab.names}
and insert
% new function, essentially a copy of format.lab.names
% that produces two-letter labels from each name
FUNCTION {format.lab.names.safe}
{ 's :=
s num.names$ 'numnames :=
numnames #1 >
{ numnames #4 >
{ #3 'namesleft := }
{ numnames 'namesleft := }
if$
#1 'nameptr :=
""
{ namesleft #0 > }
{ nameptr numnames =
{ s nameptr "{ff }{vv }{ll}{ jj}" format.name$ "others" =
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
{ s nameptr "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s nameptr "{ll}" format.name$ #2 text.prefix$ }
'skip$
if$
*
}
if$
}
{ s nameptr "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s nameptr "{ll}" format.name$ #2 text.prefix$ }
'skip$
if$
*
}
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
numnames #4 >
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
'skip$
if$
}
{ s #1 "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s #1 "{ll}" format.name$ #3 text.prefix$ }
'skip$
if$
}
if$
}
before it.
Replace
FUNCTION {format.lab.names}
with
% slightly modified from original to detect problematic abbreviations
FUNCTION {format.lab.names}
{ 's :=
s num.names$ 'numnames :=
numnames #1 >
{ numnames #4 >
{ #3 'namesleft := }
{ numnames 'namesleft := }
if$
#1 'nameptr :=
""
{ namesleft #0 > }
{ nameptr numnames =
{ s nameptr "{ff }{vv }{ll}{ jj}" format.name$ "others" =
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
{ s nameptr "{v{}}{l{}}" format.name$ * }
if$
}
{ s nameptr "{v{}}{l{}}" format.name$ * }
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
numnames #4 >
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
'skip$
if$
% this block is new
duplicate$ "SS" =
{ pop$
s format.lab.names.safe }
{ duplicate$ "SA" =
{ pop$
s format.lab.names.safe }
'skip$
if$
}
if$
}
{ s #1 "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s #1 "{ll}" format.name$ #3 text.prefix$ }
'skip$
if$
}
if$
}
Use
bibliographystyle{babalpha-fl-gs}
instead ofbibliographystyle{babalpha-fl}
in your document
Alternatively you can get babalpha-fl-gs.bst
from https://gist.github.com/moewew/158481168f4a2135764f96fc608a1998
documentclass[ngerman]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage{babelbib}
usepackage{hyperref}
bibliographystyle{babalpha-fl-gs}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide},
}
end{filecontents}
begin{document}
cite{SchwaberSutherland-DerScrumGuide}
bibliography{jobname}
end{document}
With a bit of work babalpha-fl.bst
can be taught to detect historically problematic abbreviations in labels and try to work around it.
I'm working under the assumption that only certain two letter abbreviations are problematic (the example has "SS" and "SA" hard-coded, but you can add "HH", "HJ", "NSDAP", you name it, I have not added anything to ban entries from 1988 and 2018, though) and that using two letters of each author name instead can mitigate the problem.
As mentioned above, you will have to modify the .bst
file. To do that proceed as follows
- Locate
babalpha-fl.bst
on your machine for example by typingkpsewhich babalpha-fl.bst
. - Copy the file to a place where LaTeX can find it (https://texfaq.org/FAQ-inst-wlcf), the directory of your document will do just fine, and rename it to
babalpha-fl-gs.bst
, say. Note that the license ofbabalpha-fl.bst
requires you to change the name of the file if you modify it. - Open
babalpha-fl-gs.bst
and insert a header with the new file name and the current date
Find
FUNCTION {format.lab.names}
and insert
% new function, essentially a copy of format.lab.names
% that produces two-letter labels from each name
FUNCTION {format.lab.names.safe}
{ 's :=
s num.names$ 'numnames :=
numnames #1 >
{ numnames #4 >
{ #3 'namesleft := }
{ numnames 'namesleft := }
if$
#1 'nameptr :=
""
{ namesleft #0 > }
{ nameptr numnames =
{ s nameptr "{ff }{vv }{ll}{ jj}" format.name$ "others" =
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
{ s nameptr "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s nameptr "{ll}" format.name$ #2 text.prefix$ }
'skip$
if$
*
}
if$
}
{ s nameptr "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s nameptr "{ll}" format.name$ #2 text.prefix$ }
'skip$
if$
*
}
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
numnames #4 >
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
'skip$
if$
}
{ s #1 "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s #1 "{ll}" format.name$ #3 text.prefix$ }
'skip$
if$
}
if$
}
before it.
Replace
FUNCTION {format.lab.names}
with
% slightly modified from original to detect problematic abbreviations
FUNCTION {format.lab.names}
{ 's :=
s num.names$ 'numnames :=
numnames #1 >
{ numnames #4 >
{ #3 'namesleft := }
{ numnames 'namesleft := }
if$
#1 'nameptr :=
""
{ namesleft #0 > }
{ nameptr numnames =
{ s nameptr "{ff }{vv }{ll}{ jj}" format.name$ "others" =
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
{ s nameptr "{v{}}{l{}}" format.name$ * }
if$
}
{ s nameptr "{v{}}{l{}}" format.name$ * }
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
numnames #4 >
{ "{etalchar{+}}" *
#1 'et.al.char.used :=
}
'skip$
if$
% this block is new
duplicate$ "SS" =
{ pop$
s format.lab.names.safe }
{ duplicate$ "SA" =
{ pop$
s format.lab.names.safe }
'skip$
if$
}
if$
}
{ s #1 "{v{}}{l{}}" format.name$
duplicate$ text.length$ #2 <
{ pop$ s #1 "{ll}" format.name$ #3 text.prefix$ }
'skip$
if$
}
if$
}
Use
bibliographystyle{babalpha-fl-gs}
instead ofbibliographystyle{babalpha-fl}
in your document
Alternatively you can get babalpha-fl-gs.bst
from https://gist.github.com/moewew/158481168f4a2135764f96fc608a1998
documentclass[ngerman]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage{babelbib}
usepackage{hyperref}
bibliographystyle{babalpha-fl-gs}
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{SchwaberSutherland-DerScrumGuide,
author = {Ken Schwaber and Jeff Sutherland},
title = {Der Scrum Guide™},
year=2017,
month=nov,
language={ngerman},
url={http://www.scrum.org/resources/scrum-guide},
}
end{filecontents}
begin{document}
cite{SchwaberSutherland-DerScrumGuide}
bibliography{jobname}
end{document}
edited Feb 1 at 21:00
answered Jul 16 '18 at 14:06
moewemoewe
89.9k10110339
89.9k10110339
Works like a charm, thank you! Regarding the maturity of your code, would you suggest that it is used in a production environment, or would you suggest that additional testing be done?
– user0
Jul 16 '18 at 15:22
What do you think of @egreg 's suggestion?
– user0
Jul 16 '18 at 15:26
@user49915 It's a bit boring, isn't it? ;-) It has the huge advantage of not requiring changes to.bst
files which can be a plus if you are not into this sort of thing (and might be a plus when you have to share your work with others or submit it to a publisher - though publishers usually want the.bbl
file in which case a modified.bst
file does not really matter). I must say that I mainly answered because I liked the challenge, not because I thought this would be particularly useful. ...
– moewe
Jul 16 '18 at 15:35
... But of course my solution is not supposed to require manual intervention which is nice in case you want to re-use the.bib
file for something else. It was a similar situation here.
– moewe
Jul 16 '18 at 15:35
@user49915 I only just saw your comment about code maturity. I'm quite confident that the code as posted works as intended. But of course I can't guarantee that everything works as desired so a bit of caution is always advised.
– moewe
Jul 16 '18 at 15:43
|
show 12 more comments
Works like a charm, thank you! Regarding the maturity of your code, would you suggest that it is used in a production environment, or would you suggest that additional testing be done?
– user0
Jul 16 '18 at 15:22
What do you think of @egreg 's suggestion?
– user0
Jul 16 '18 at 15:26
@user49915 It's a bit boring, isn't it? ;-) It has the huge advantage of not requiring changes to.bst
files which can be a plus if you are not into this sort of thing (and might be a plus when you have to share your work with others or submit it to a publisher - though publishers usually want the.bbl
file in which case a modified.bst
file does not really matter). I must say that I mainly answered because I liked the challenge, not because I thought this would be particularly useful. ...
– moewe
Jul 16 '18 at 15:35
... But of course my solution is not supposed to require manual intervention which is nice in case you want to re-use the.bib
file for something else. It was a similar situation here.
– moewe
Jul 16 '18 at 15:35
@user49915 I only just saw your comment about code maturity. I'm quite confident that the code as posted works as intended. But of course I can't guarantee that everything works as desired so a bit of caution is always advised.
– moewe
Jul 16 '18 at 15:43
Works like a charm, thank you! Regarding the maturity of your code, would you suggest that it is used in a production environment, or would you suggest that additional testing be done?
– user0
Jul 16 '18 at 15:22
Works like a charm, thank you! Regarding the maturity of your code, would you suggest that it is used in a production environment, or would you suggest that additional testing be done?
– user0
Jul 16 '18 at 15:22
What do you think of @egreg 's suggestion?
– user0
Jul 16 '18 at 15:26
What do you think of @egreg 's suggestion?
– user0
Jul 16 '18 at 15:26
@user49915 It's a bit boring, isn't it? ;-) It has the huge advantage of not requiring changes to
.bst
files which can be a plus if you are not into this sort of thing (and might be a plus when you have to share your work with others or submit it to a publisher - though publishers usually want the .bbl
file in which case a modified .bst
file does not really matter). I must say that I mainly answered because I liked the challenge, not because I thought this would be particularly useful. ...– moewe
Jul 16 '18 at 15:35
@user49915 It's a bit boring, isn't it? ;-) It has the huge advantage of not requiring changes to
.bst
files which can be a plus if you are not into this sort of thing (and might be a plus when you have to share your work with others or submit it to a publisher - though publishers usually want the .bbl
file in which case a modified .bst
file does not really matter). I must say that I mainly answered because I liked the challenge, not because I thought this would be particularly useful. ...– moewe
Jul 16 '18 at 15:35
... But of course my solution is not supposed to require manual intervention which is nice in case you want to re-use the
.bib
file for something else. It was a similar situation here.– moewe
Jul 16 '18 at 15:35
... But of course my solution is not supposed to require manual intervention which is nice in case you want to re-use the
.bib
file for something else. It was a similar situation here.– moewe
Jul 16 '18 at 15:35
@user49915 I only just saw your comment about code maturity. I'm quite confident that the code as posted works as intended. But of course I can't guarantee that everything works as desired so a bit of caution is always advised.
– moewe
Jul 16 '18 at 15:43
@user49915 I only just saw your comment about code maturity. I'm quite confident that the code as posted works as intended. But of course I can't guarantee that everything works as desired so a bit of caution is always advised.
– moewe
Jul 16 '18 at 15:43
|
show 12 more comments
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f441864%2favoiding-ss-in-german-bibliographies%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
Do you avoid double sums and integrals too?
– st.vit
Jul 16 '18 at 15:39
1
@st.vir I doubt that anyone in their right mind would really object to double integrals and sums. Still, there are lots of envious folks around trying to make your life hard by pinpointing to an abbreviation such as [SS]. So, let's not feed the bears.
– user0
Jul 16 '18 at 18:34
I would think of "Sommersemester", when reading, SS.... In fact, WS , SS followed by year are very common German shorthands for winter and summer semester in the accademic field.
– AlexG
Feb 1 at 21:57
@AlexG But only in certain federal states of Germany. In certain other federal states, they use SoSe instead of SS for Sommersemester.
– user0
Feb 1 at 22:07
Never seen SoSe. Maybe I am too old.
– AlexG
Feb 1 at 22:25