How to “delete” space between Author and semicolon in bibtex
i created my Bibliographie, but i got unwanted spaces between autor and semicolon like that:
Author1[space1];[space2]author2;[...]
And i want it like that:
Author1;[space2]author2;[...]
Here is the Code so far:
documentclass[
a4paper,
11pt,
parskip=half,
twoside,
openright,
pointlessnumbers,
headsepline,
bibtotoc,
DIV=15,
BCOR=1cm
]
{scrbook}
[...]
usepackage{hyperref}
hypersetup{
linktocpage,
colorlinks=true,
citecolor=black,
linkcolor=black,
urlcolor=black
}
[...]
bibliographystyle{alphadin}
And if it helps the Bibtex entry for [AE06]:
@article{arbinger2006designing,
title={Designing with an embedded soft-core processor},
author={Arbinger, Don and Erdmann, Jeremy},
journal={Embedded cracking the code to systems development},
year={2006}
}
So how can i "delete" this extra space ?
I hope you can help me with this issue.
spacing bibtex citing
New contributor
add a comment |
i created my Bibliographie, but i got unwanted spaces between autor and semicolon like that:
Author1[space1];[space2]author2;[...]
And i want it like that:
Author1;[space2]author2;[...]
Here is the Code so far:
documentclass[
a4paper,
11pt,
parskip=half,
twoside,
openright,
pointlessnumbers,
headsepline,
bibtotoc,
DIV=15,
BCOR=1cm
]
{scrbook}
[...]
usepackage{hyperref}
hypersetup{
linktocpage,
colorlinks=true,
citecolor=black,
linkcolor=black,
urlcolor=black
}
[...]
bibliographystyle{alphadin}
And if it helps the Bibtex entry for [AE06]:
@article{arbinger2006designing,
title={Designing with an embedded soft-core processor},
author={Arbinger, Don and Erdmann, Jeremy},
journal={Embedded cracking the code to systems development},
year={2006}
}
So how can i "delete" this extra space ?
I hope you can help me with this issue.
spacing bibtex citing
New contributor
@moewe oops thanks I deleted my comment, (If the OP had provided an example I would have tested first:-)
– David Carlisle
55 mins ago
For future questions, please consider adding a compilable example document instead of code snippets that have to be pieced together before they can be run. This is what we call an MWE (tex.meta.stackexchange.com/q/228/35864) or MWEB (tex.meta.stackexchange.com/q/4407/35864). MWEs make it much easier for people to get started helping you and they can avoid confusion by making sure that everyone is talking about the same thing. You can find examples of useful MWEs in the answers you got below.
– moewe
17 mins ago
add a comment |
i created my Bibliographie, but i got unwanted spaces between autor and semicolon like that:
Author1[space1];[space2]author2;[...]
And i want it like that:
Author1;[space2]author2;[...]
Here is the Code so far:
documentclass[
a4paper,
11pt,
parskip=half,
twoside,
openright,
pointlessnumbers,
headsepline,
bibtotoc,
DIV=15,
BCOR=1cm
]
{scrbook}
[...]
usepackage{hyperref}
hypersetup{
linktocpage,
colorlinks=true,
citecolor=black,
linkcolor=black,
urlcolor=black
}
[...]
bibliographystyle{alphadin}
And if it helps the Bibtex entry for [AE06]:
@article{arbinger2006designing,
title={Designing with an embedded soft-core processor},
author={Arbinger, Don and Erdmann, Jeremy},
journal={Embedded cracking the code to systems development},
year={2006}
}
So how can i "delete" this extra space ?
I hope you can help me with this issue.
spacing bibtex citing
New contributor
i created my Bibliographie, but i got unwanted spaces between autor and semicolon like that:
Author1[space1];[space2]author2;[...]
And i want it like that:
Author1;[space2]author2;[...]
Here is the Code so far:
documentclass[
a4paper,
11pt,
parskip=half,
twoside,
openright,
pointlessnumbers,
headsepline,
bibtotoc,
DIV=15,
BCOR=1cm
]
{scrbook}
[...]
usepackage{hyperref}
hypersetup{
linktocpage,
colorlinks=true,
citecolor=black,
linkcolor=black,
urlcolor=black
}
[...]
bibliographystyle{alphadin}
And if it helps the Bibtex entry for [AE06]:
@article{arbinger2006designing,
title={Designing with an embedded soft-core processor},
author={Arbinger, Don and Erdmann, Jeremy},
journal={Embedded cracking the code to systems development},
year={2006}
}
So how can i "delete" this extra space ?
I hope you can help me with this issue.
spacing bibtex citing
spacing bibtex citing
New contributor
New contributor
edited 1 hour ago
Bernard
166k769194
166k769194
New contributor
asked 1 hour ago
Incanus
111
111
New contributor
New contributor
@moewe oops thanks I deleted my comment, (If the OP had provided an example I would have tested first:-)
– David Carlisle
55 mins ago
For future questions, please consider adding a compilable example document instead of code snippets that have to be pieced together before they can be run. This is what we call an MWE (tex.meta.stackexchange.com/q/228/35864) or MWEB (tex.meta.stackexchange.com/q/4407/35864). MWEs make it much easier for people to get started helping you and they can avoid confusion by making sure that everyone is talking about the same thing. You can find examples of useful MWEs in the answers you got below.
– moewe
17 mins ago
add a comment |
@moewe oops thanks I deleted my comment, (If the OP had provided an example I would have tested first:-)
– David Carlisle
55 mins ago
For future questions, please consider adding a compilable example document instead of code snippets that have to be pieced together before they can be run. This is what we call an MWE (tex.meta.stackexchange.com/q/228/35864) or MWEB (tex.meta.stackexchange.com/q/4407/35864). MWEs make it much easier for people to get started helping you and they can avoid confusion by making sure that everyone is talking about the same thing. You can find examples of useful MWEs in the answers you got below.
– moewe
17 mins ago
@moewe oops thanks I deleted my comment, (If the OP had provided an example I would have tested first:-)
– David Carlisle
55 mins ago
@moewe oops thanks I deleted my comment, (If the OP had provided an example I would have tested first:-)
– David Carlisle
55 mins ago
For future questions, please consider adding a compilable example document instead of code snippets that have to be pieced together before they can be run. This is what we call an MWE (tex.meta.stackexchange.com/q/228/35864) or MWEB (tex.meta.stackexchange.com/q/4407/35864). MWEs make it much easier for people to get started helping you and they can avoid confusion by making sure that everyone is talking about the same thing. You can find examples of useful MWEs in the answers you got below.
– moewe
17 mins ago
For future questions, please consider adding a compilable example document instead of code snippets that have to be pieced together before they can be run. This is what we call an MWE (tex.meta.stackexchange.com/q/228/35864) or MWEB (tex.meta.stackexchange.com/q/4407/35864). MWEs make it much easier for people to get started helping you and they can avoid confusion by making sure that everyone is talking about the same thing. You can find examples of useful MWEs in the answers you got below.
– moewe
17 mins ago
add a comment |
2 Answers
2
active
oldest
votes
alphadin
implements the norm DIN 1505-2, which is now superseded by (the slightly less terrible) (DIN) ISO 690. DIN 1505-2 uses semicolons (as well as en-dashes and slashes) with a leading and following space. The norm does not follow German tradition, which never places a space before a semicolon, but it also does not go full French, because it does not place spaces before colons.
That behaviour is hard-coded in alphadin.bst
and has to be changed manually by modifying the file.
Locate the style you want to change on your machine. You can find the file path by typing
kpsewhich alphadin.bst
into a terminal. Failing that get the files from CTAN: https://ctan.org/tex-archive/biblio/bibtex/contrib/german/din1505Copy the file to a place where LaTeX can find it (https://texfaq.org/FAQ-inst-wlcf), the directory of your current document will do just fine, and rename it. Many LaTeX files require you to rename the file in their license conditions. But even if the license is not clear on that, it is extremely good practice to rename changed files. Let's say the new name is
alphadin-nospace.bst
Find all six
" ; "
in the file and replace them with"; "
. In my copy the relevant lines are
- 408
- 415
- 449
- 483
- 502
- 1199
Ideally you place a short notice of the changes, your name and the date at the top of the file.
Save the modified and renamed file.
Use
bibliographystyle{alphadin-nospace}
instead ofbibliographystyle{alphadin}
in your document.
RequirePackage{filecontents}
begin{filecontents}{jobname.bib}
@article{arbinger2006designing,
title = {Designing with an embedded soft-core processor},
author = {Arbinger, Don and Erdmann, Jeremy},
journal = {Embedded cracking the code to systems development},
year = {2006},
volume = {14},
pages = {76-89},
}
end{filecontents}
documentclass{article}
bibliographystyle{alphadin-nosp}
begin{document}
cite{arbinger2006designing}
bibliography{jobname}
end{document}
Since Mico gave the same answer just a minute and a half earlier, let me try to justify this answers presence with a bit of advertising for biblatex
.
As mentioned above DIN 1505-2 has been superseded by ISO 690 and so it makes little sense to continue using styles from the din1505
bundle, to which alphadin
belongs, for new documents.
A similar style can be achieved with biblatex
, which is much more flexible when it comes to small changes like this. See bibtex vs. biber and biblatex vs. natbib, What to do to switch to biblatex?, Biblatex with Biber: Configuring my editor to avoid undefined citations and Guidelines for customizing biblatex styles for more introductory posts on biblatex
.
RequirePackage{filecontents}
begin{filecontents}{jobname.bib}
@article{arbinger2006designing,
title = {Designing with an embedded soft-core processor},
author = {Arbinger, Don and Erdmann, Jeremy},
journal = {Embedded cracking the code to systems development},
year = {2006},
volume = {14},
pages = {76-89},
}
end{filecontents}
documentclass[ngerman]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage[style=alphabetic]{biblatex}
DeclareNameAlias{author}{sortname}
DeclareNameAlias{editor}{sortname}
DeclareNameAlias{translator}{sortname}
DeclareNameAlias{sortname}{family-given}
DeclareDelimFormat{multinamedelim}{addsemicolonspace}
DeclareDelimAlias{finalnamedelim}{multinamedelim}
renewcommand*{mkbibnamefamily}{textsc}
DeclareFieldFormat
[article,inbook,incollection,inproceedings,patent,thesis,unpublished]
{title}{#1isdot}
addbibresource{jobname.bib}
begin{document}
cite{arbinger2006designing}
printbibliography
end{document}
add a comment |
The presence of whitespace between an author's (or editor's) name and the semicolon appears to be a design feature rather than a bug of the alphadin
bibliography style. To wit, I was able to locate no fewer than six [6!] instances of " ; "
in the file: 2 in the function format.names
, and 1 each in the functions format.editors
, format.authors.organization
, format.editors.organization
, and format.crossref.editor
.
That said, what's definitely bizarre is that the coding string isn't given as "~; "
. Using ~
before ;
would disallow a line break immediately before the semicolon. Allowing a line break immediately before a semicolon must surely be a typographic blunder.
If you prefer not to have whitespace before the semicolons, I suggest you proceed as follows:
Locate the file
alphadin.bst
in your TeX distribution. Make a copy of this file and call the copy, say,alphadin-mod.bst
. (Do not edit an original file of the TeX distribution directly.)Open the file
alphadin-mod.bst
in a text editor. The program you use to edit your tex files will do fine.Do a global search-and-replace, changing
" ; "
to"; "
. A total of six instances should be affected.Save the file
alphadin-mod.bst
either in the directory where your main tex file is located or in a directory that's searched by BibTeX. If you choose the second option, be sure to update the filename database of your TeX distribution suitably.In the main tex file, change the instruction
bibliographystyle{alphadin}
tobibliographystyle{alphadin-mod}
and perform a full recompile cycle: LaTeX, BibTeX, and LaTeX twice more.
Happy BibTeXing!
RequirePackage{filecontents}
begin{filecontents}{mybib.bib}
@misc{ae:06,
title={Thoughts},
author={Arbinger, Don and Erdmann, Jeremy},
year={2006}
}
end{filecontents}
documentclass{scrbook}
bibliographystyle{alphadin-mod}
begin{document}
cite{ae:06}
bibliography{mybib}
end{document}
add a 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
});
}
});
Incanus is a new contributor. Be nice, and check out our Code of Conduct.
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%2f468119%2fhow-to-delete-space-between-author-and-semicolon-in-bibtex%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
alphadin
implements the norm DIN 1505-2, which is now superseded by (the slightly less terrible) (DIN) ISO 690. DIN 1505-2 uses semicolons (as well as en-dashes and slashes) with a leading and following space. The norm does not follow German tradition, which never places a space before a semicolon, but it also does not go full French, because it does not place spaces before colons.
That behaviour is hard-coded in alphadin.bst
and has to be changed manually by modifying the file.
Locate the style you want to change on your machine. You can find the file path by typing
kpsewhich alphadin.bst
into a terminal. Failing that get the files from CTAN: https://ctan.org/tex-archive/biblio/bibtex/contrib/german/din1505Copy the file to a place where LaTeX can find it (https://texfaq.org/FAQ-inst-wlcf), the directory of your current document will do just fine, and rename it. Many LaTeX files require you to rename the file in their license conditions. But even if the license is not clear on that, it is extremely good practice to rename changed files. Let's say the new name is
alphadin-nospace.bst
Find all six
" ; "
in the file and replace them with"; "
. In my copy the relevant lines are
- 408
- 415
- 449
- 483
- 502
- 1199
Ideally you place a short notice of the changes, your name and the date at the top of the file.
Save the modified and renamed file.
Use
bibliographystyle{alphadin-nospace}
instead ofbibliographystyle{alphadin}
in your document.
RequirePackage{filecontents}
begin{filecontents}{jobname.bib}
@article{arbinger2006designing,
title = {Designing with an embedded soft-core processor},
author = {Arbinger, Don and Erdmann, Jeremy},
journal = {Embedded cracking the code to systems development},
year = {2006},
volume = {14},
pages = {76-89},
}
end{filecontents}
documentclass{article}
bibliographystyle{alphadin-nosp}
begin{document}
cite{arbinger2006designing}
bibliography{jobname}
end{document}
Since Mico gave the same answer just a minute and a half earlier, let me try to justify this answers presence with a bit of advertising for biblatex
.
As mentioned above DIN 1505-2 has been superseded by ISO 690 and so it makes little sense to continue using styles from the din1505
bundle, to which alphadin
belongs, for new documents.
A similar style can be achieved with biblatex
, which is much more flexible when it comes to small changes like this. See bibtex vs. biber and biblatex vs. natbib, What to do to switch to biblatex?, Biblatex with Biber: Configuring my editor to avoid undefined citations and Guidelines for customizing biblatex styles for more introductory posts on biblatex
.
RequirePackage{filecontents}
begin{filecontents}{jobname.bib}
@article{arbinger2006designing,
title = {Designing with an embedded soft-core processor},
author = {Arbinger, Don and Erdmann, Jeremy},
journal = {Embedded cracking the code to systems development},
year = {2006},
volume = {14},
pages = {76-89},
}
end{filecontents}
documentclass[ngerman]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage[style=alphabetic]{biblatex}
DeclareNameAlias{author}{sortname}
DeclareNameAlias{editor}{sortname}
DeclareNameAlias{translator}{sortname}
DeclareNameAlias{sortname}{family-given}
DeclareDelimFormat{multinamedelim}{addsemicolonspace}
DeclareDelimAlias{finalnamedelim}{multinamedelim}
renewcommand*{mkbibnamefamily}{textsc}
DeclareFieldFormat
[article,inbook,incollection,inproceedings,patent,thesis,unpublished]
{title}{#1isdot}
addbibresource{jobname.bib}
begin{document}
cite{arbinger2006designing}
printbibliography
end{document}
add a comment |
alphadin
implements the norm DIN 1505-2, which is now superseded by (the slightly less terrible) (DIN) ISO 690. DIN 1505-2 uses semicolons (as well as en-dashes and slashes) with a leading and following space. The norm does not follow German tradition, which never places a space before a semicolon, but it also does not go full French, because it does not place spaces before colons.
That behaviour is hard-coded in alphadin.bst
and has to be changed manually by modifying the file.
Locate the style you want to change on your machine. You can find the file path by typing
kpsewhich alphadin.bst
into a terminal. Failing that get the files from CTAN: https://ctan.org/tex-archive/biblio/bibtex/contrib/german/din1505Copy the file to a place where LaTeX can find it (https://texfaq.org/FAQ-inst-wlcf), the directory of your current document will do just fine, and rename it. Many LaTeX files require you to rename the file in their license conditions. But even if the license is not clear on that, it is extremely good practice to rename changed files. Let's say the new name is
alphadin-nospace.bst
Find all six
" ; "
in the file and replace them with"; "
. In my copy the relevant lines are
- 408
- 415
- 449
- 483
- 502
- 1199
Ideally you place a short notice of the changes, your name and the date at the top of the file.
Save the modified and renamed file.
Use
bibliographystyle{alphadin-nospace}
instead ofbibliographystyle{alphadin}
in your document.
RequirePackage{filecontents}
begin{filecontents}{jobname.bib}
@article{arbinger2006designing,
title = {Designing with an embedded soft-core processor},
author = {Arbinger, Don and Erdmann, Jeremy},
journal = {Embedded cracking the code to systems development},
year = {2006},
volume = {14},
pages = {76-89},
}
end{filecontents}
documentclass{article}
bibliographystyle{alphadin-nosp}
begin{document}
cite{arbinger2006designing}
bibliography{jobname}
end{document}
Since Mico gave the same answer just a minute and a half earlier, let me try to justify this answers presence with a bit of advertising for biblatex
.
As mentioned above DIN 1505-2 has been superseded by ISO 690 and so it makes little sense to continue using styles from the din1505
bundle, to which alphadin
belongs, for new documents.
A similar style can be achieved with biblatex
, which is much more flexible when it comes to small changes like this. See bibtex vs. biber and biblatex vs. natbib, What to do to switch to biblatex?, Biblatex with Biber: Configuring my editor to avoid undefined citations and Guidelines for customizing biblatex styles for more introductory posts on biblatex
.
RequirePackage{filecontents}
begin{filecontents}{jobname.bib}
@article{arbinger2006designing,
title = {Designing with an embedded soft-core processor},
author = {Arbinger, Don and Erdmann, Jeremy},
journal = {Embedded cracking the code to systems development},
year = {2006},
volume = {14},
pages = {76-89},
}
end{filecontents}
documentclass[ngerman]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage[style=alphabetic]{biblatex}
DeclareNameAlias{author}{sortname}
DeclareNameAlias{editor}{sortname}
DeclareNameAlias{translator}{sortname}
DeclareNameAlias{sortname}{family-given}
DeclareDelimFormat{multinamedelim}{addsemicolonspace}
DeclareDelimAlias{finalnamedelim}{multinamedelim}
renewcommand*{mkbibnamefamily}{textsc}
DeclareFieldFormat
[article,inbook,incollection,inproceedings,patent,thesis,unpublished]
{title}{#1isdot}
addbibresource{jobname.bib}
begin{document}
cite{arbinger2006designing}
printbibliography
end{document}
add a comment |
alphadin
implements the norm DIN 1505-2, which is now superseded by (the slightly less terrible) (DIN) ISO 690. DIN 1505-2 uses semicolons (as well as en-dashes and slashes) with a leading and following space. The norm does not follow German tradition, which never places a space before a semicolon, but it also does not go full French, because it does not place spaces before colons.
That behaviour is hard-coded in alphadin.bst
and has to be changed manually by modifying the file.
Locate the style you want to change on your machine. You can find the file path by typing
kpsewhich alphadin.bst
into a terminal. Failing that get the files from CTAN: https://ctan.org/tex-archive/biblio/bibtex/contrib/german/din1505Copy the file to a place where LaTeX can find it (https://texfaq.org/FAQ-inst-wlcf), the directory of your current document will do just fine, and rename it. Many LaTeX files require you to rename the file in their license conditions. But even if the license is not clear on that, it is extremely good practice to rename changed files. Let's say the new name is
alphadin-nospace.bst
Find all six
" ; "
in the file and replace them with"; "
. In my copy the relevant lines are
- 408
- 415
- 449
- 483
- 502
- 1199
Ideally you place a short notice of the changes, your name and the date at the top of the file.
Save the modified and renamed file.
Use
bibliographystyle{alphadin-nospace}
instead ofbibliographystyle{alphadin}
in your document.
RequirePackage{filecontents}
begin{filecontents}{jobname.bib}
@article{arbinger2006designing,
title = {Designing with an embedded soft-core processor},
author = {Arbinger, Don and Erdmann, Jeremy},
journal = {Embedded cracking the code to systems development},
year = {2006},
volume = {14},
pages = {76-89},
}
end{filecontents}
documentclass{article}
bibliographystyle{alphadin-nosp}
begin{document}
cite{arbinger2006designing}
bibliography{jobname}
end{document}
Since Mico gave the same answer just a minute and a half earlier, let me try to justify this answers presence with a bit of advertising for biblatex
.
As mentioned above DIN 1505-2 has been superseded by ISO 690 and so it makes little sense to continue using styles from the din1505
bundle, to which alphadin
belongs, for new documents.
A similar style can be achieved with biblatex
, which is much more flexible when it comes to small changes like this. See bibtex vs. biber and biblatex vs. natbib, What to do to switch to biblatex?, Biblatex with Biber: Configuring my editor to avoid undefined citations and Guidelines for customizing biblatex styles for more introductory posts on biblatex
.
RequirePackage{filecontents}
begin{filecontents}{jobname.bib}
@article{arbinger2006designing,
title = {Designing with an embedded soft-core processor},
author = {Arbinger, Don and Erdmann, Jeremy},
journal = {Embedded cracking the code to systems development},
year = {2006},
volume = {14},
pages = {76-89},
}
end{filecontents}
documentclass[ngerman]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage[style=alphabetic]{biblatex}
DeclareNameAlias{author}{sortname}
DeclareNameAlias{editor}{sortname}
DeclareNameAlias{translator}{sortname}
DeclareNameAlias{sortname}{family-given}
DeclareDelimFormat{multinamedelim}{addsemicolonspace}
DeclareDelimAlias{finalnamedelim}{multinamedelim}
renewcommand*{mkbibnamefamily}{textsc}
DeclareFieldFormat
[article,inbook,incollection,inproceedings,patent,thesis,unpublished]
{title}{#1isdot}
addbibresource{jobname.bib}
begin{document}
cite{arbinger2006designing}
printbibliography
end{document}
alphadin
implements the norm DIN 1505-2, which is now superseded by (the slightly less terrible) (DIN) ISO 690. DIN 1505-2 uses semicolons (as well as en-dashes and slashes) with a leading and following space. The norm does not follow German tradition, which never places a space before a semicolon, but it also does not go full French, because it does not place spaces before colons.
That behaviour is hard-coded in alphadin.bst
and has to be changed manually by modifying the file.
Locate the style you want to change on your machine. You can find the file path by typing
kpsewhich alphadin.bst
into a terminal. Failing that get the files from CTAN: https://ctan.org/tex-archive/biblio/bibtex/contrib/german/din1505Copy the file to a place where LaTeX can find it (https://texfaq.org/FAQ-inst-wlcf), the directory of your current document will do just fine, and rename it. Many LaTeX files require you to rename the file in their license conditions. But even if the license is not clear on that, it is extremely good practice to rename changed files. Let's say the new name is
alphadin-nospace.bst
Find all six
" ; "
in the file and replace them with"; "
. In my copy the relevant lines are
- 408
- 415
- 449
- 483
- 502
- 1199
Ideally you place a short notice of the changes, your name and the date at the top of the file.
Save the modified and renamed file.
Use
bibliographystyle{alphadin-nospace}
instead ofbibliographystyle{alphadin}
in your document.
RequirePackage{filecontents}
begin{filecontents}{jobname.bib}
@article{arbinger2006designing,
title = {Designing with an embedded soft-core processor},
author = {Arbinger, Don and Erdmann, Jeremy},
journal = {Embedded cracking the code to systems development},
year = {2006},
volume = {14},
pages = {76-89},
}
end{filecontents}
documentclass{article}
bibliographystyle{alphadin-nosp}
begin{document}
cite{arbinger2006designing}
bibliography{jobname}
end{document}
Since Mico gave the same answer just a minute and a half earlier, let me try to justify this answers presence with a bit of advertising for biblatex
.
As mentioned above DIN 1505-2 has been superseded by ISO 690 and so it makes little sense to continue using styles from the din1505
bundle, to which alphadin
belongs, for new documents.
A similar style can be achieved with biblatex
, which is much more flexible when it comes to small changes like this. See bibtex vs. biber and biblatex vs. natbib, What to do to switch to biblatex?, Biblatex with Biber: Configuring my editor to avoid undefined citations and Guidelines for customizing biblatex styles for more introductory posts on biblatex
.
RequirePackage{filecontents}
begin{filecontents}{jobname.bib}
@article{arbinger2006designing,
title = {Designing with an embedded soft-core processor},
author = {Arbinger, Don and Erdmann, Jeremy},
journal = {Embedded cracking the code to systems development},
year = {2006},
volume = {14},
pages = {76-89},
}
end{filecontents}
documentclass[ngerman]{article}
usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}
usepackage{babel}
usepackage{csquotes}
usepackage[style=alphabetic]{biblatex}
DeclareNameAlias{author}{sortname}
DeclareNameAlias{editor}{sortname}
DeclareNameAlias{translator}{sortname}
DeclareNameAlias{sortname}{family-given}
DeclareDelimFormat{multinamedelim}{addsemicolonspace}
DeclareDelimAlias{finalnamedelim}{multinamedelim}
renewcommand*{mkbibnamefamily}{textsc}
DeclareFieldFormat
[article,inbook,incollection,inproceedings,patent,thesis,unpublished]
{title}{#1isdot}
addbibresource{jobname.bib}
begin{document}
cite{arbinger2006designing}
printbibliography
end{document}
edited 25 mins ago
answered 42 mins ago
moewe
86.4k9110332
86.4k9110332
add a comment |
add a comment |
The presence of whitespace between an author's (or editor's) name and the semicolon appears to be a design feature rather than a bug of the alphadin
bibliography style. To wit, I was able to locate no fewer than six [6!] instances of " ; "
in the file: 2 in the function format.names
, and 1 each in the functions format.editors
, format.authors.organization
, format.editors.organization
, and format.crossref.editor
.
That said, what's definitely bizarre is that the coding string isn't given as "~; "
. Using ~
before ;
would disallow a line break immediately before the semicolon. Allowing a line break immediately before a semicolon must surely be a typographic blunder.
If you prefer not to have whitespace before the semicolons, I suggest you proceed as follows:
Locate the file
alphadin.bst
in your TeX distribution. Make a copy of this file and call the copy, say,alphadin-mod.bst
. (Do not edit an original file of the TeX distribution directly.)Open the file
alphadin-mod.bst
in a text editor. The program you use to edit your tex files will do fine.Do a global search-and-replace, changing
" ; "
to"; "
. A total of six instances should be affected.Save the file
alphadin-mod.bst
either in the directory where your main tex file is located or in a directory that's searched by BibTeX. If you choose the second option, be sure to update the filename database of your TeX distribution suitably.In the main tex file, change the instruction
bibliographystyle{alphadin}
tobibliographystyle{alphadin-mod}
and perform a full recompile cycle: LaTeX, BibTeX, and LaTeX twice more.
Happy BibTeXing!
RequirePackage{filecontents}
begin{filecontents}{mybib.bib}
@misc{ae:06,
title={Thoughts},
author={Arbinger, Don and Erdmann, Jeremy},
year={2006}
}
end{filecontents}
documentclass{scrbook}
bibliographystyle{alphadin-mod}
begin{document}
cite{ae:06}
bibliography{mybib}
end{document}
add a comment |
The presence of whitespace between an author's (or editor's) name and the semicolon appears to be a design feature rather than a bug of the alphadin
bibliography style. To wit, I was able to locate no fewer than six [6!] instances of " ; "
in the file: 2 in the function format.names
, and 1 each in the functions format.editors
, format.authors.organization
, format.editors.organization
, and format.crossref.editor
.
That said, what's definitely bizarre is that the coding string isn't given as "~; "
. Using ~
before ;
would disallow a line break immediately before the semicolon. Allowing a line break immediately before a semicolon must surely be a typographic blunder.
If you prefer not to have whitespace before the semicolons, I suggest you proceed as follows:
Locate the file
alphadin.bst
in your TeX distribution. Make a copy of this file and call the copy, say,alphadin-mod.bst
. (Do not edit an original file of the TeX distribution directly.)Open the file
alphadin-mod.bst
in a text editor. The program you use to edit your tex files will do fine.Do a global search-and-replace, changing
" ; "
to"; "
. A total of six instances should be affected.Save the file
alphadin-mod.bst
either in the directory where your main tex file is located or in a directory that's searched by BibTeX. If you choose the second option, be sure to update the filename database of your TeX distribution suitably.In the main tex file, change the instruction
bibliographystyle{alphadin}
tobibliographystyle{alphadin-mod}
and perform a full recompile cycle: LaTeX, BibTeX, and LaTeX twice more.
Happy BibTeXing!
RequirePackage{filecontents}
begin{filecontents}{mybib.bib}
@misc{ae:06,
title={Thoughts},
author={Arbinger, Don and Erdmann, Jeremy},
year={2006}
}
end{filecontents}
documentclass{scrbook}
bibliographystyle{alphadin-mod}
begin{document}
cite{ae:06}
bibliography{mybib}
end{document}
add a comment |
The presence of whitespace between an author's (or editor's) name and the semicolon appears to be a design feature rather than a bug of the alphadin
bibliography style. To wit, I was able to locate no fewer than six [6!] instances of " ; "
in the file: 2 in the function format.names
, and 1 each in the functions format.editors
, format.authors.organization
, format.editors.organization
, and format.crossref.editor
.
That said, what's definitely bizarre is that the coding string isn't given as "~; "
. Using ~
before ;
would disallow a line break immediately before the semicolon. Allowing a line break immediately before a semicolon must surely be a typographic blunder.
If you prefer not to have whitespace before the semicolons, I suggest you proceed as follows:
Locate the file
alphadin.bst
in your TeX distribution. Make a copy of this file and call the copy, say,alphadin-mod.bst
. (Do not edit an original file of the TeX distribution directly.)Open the file
alphadin-mod.bst
in a text editor. The program you use to edit your tex files will do fine.Do a global search-and-replace, changing
" ; "
to"; "
. A total of six instances should be affected.Save the file
alphadin-mod.bst
either in the directory where your main tex file is located or in a directory that's searched by BibTeX. If you choose the second option, be sure to update the filename database of your TeX distribution suitably.In the main tex file, change the instruction
bibliographystyle{alphadin}
tobibliographystyle{alphadin-mod}
and perform a full recompile cycle: LaTeX, BibTeX, and LaTeX twice more.
Happy BibTeXing!
RequirePackage{filecontents}
begin{filecontents}{mybib.bib}
@misc{ae:06,
title={Thoughts},
author={Arbinger, Don and Erdmann, Jeremy},
year={2006}
}
end{filecontents}
documentclass{scrbook}
bibliographystyle{alphadin-mod}
begin{document}
cite{ae:06}
bibliography{mybib}
end{document}
The presence of whitespace between an author's (or editor's) name and the semicolon appears to be a design feature rather than a bug of the alphadin
bibliography style. To wit, I was able to locate no fewer than six [6!] instances of " ; "
in the file: 2 in the function format.names
, and 1 each in the functions format.editors
, format.authors.organization
, format.editors.organization
, and format.crossref.editor
.
That said, what's definitely bizarre is that the coding string isn't given as "~; "
. Using ~
before ;
would disallow a line break immediately before the semicolon. Allowing a line break immediately before a semicolon must surely be a typographic blunder.
If you prefer not to have whitespace before the semicolons, I suggest you proceed as follows:
Locate the file
alphadin.bst
in your TeX distribution. Make a copy of this file and call the copy, say,alphadin-mod.bst
. (Do not edit an original file of the TeX distribution directly.)Open the file
alphadin-mod.bst
in a text editor. The program you use to edit your tex files will do fine.Do a global search-and-replace, changing
" ; "
to"; "
. A total of six instances should be affected.Save the file
alphadin-mod.bst
either in the directory where your main tex file is located or in a directory that's searched by BibTeX. If you choose the second option, be sure to update the filename database of your TeX distribution suitably.In the main tex file, change the instruction
bibliographystyle{alphadin}
tobibliographystyle{alphadin-mod}
and perform a full recompile cycle: LaTeX, BibTeX, and LaTeX twice more.
Happy BibTeXing!
RequirePackage{filecontents}
begin{filecontents}{mybib.bib}
@misc{ae:06,
title={Thoughts},
author={Arbinger, Don and Erdmann, Jeremy},
year={2006}
}
end{filecontents}
documentclass{scrbook}
bibliographystyle{alphadin-mod}
begin{document}
cite{ae:06}
bibliography{mybib}
end{document}
edited 24 mins ago
answered 44 mins ago
Mico
274k30369756
274k30369756
add a comment |
add a comment |
Incanus is a new contributor. Be nice, and check out our Code of Conduct.
Incanus is a new contributor. Be nice, and check out our Code of Conduct.
Incanus is a new contributor. Be nice, and check out our Code of Conduct.
Incanus is a new contributor. Be nice, and check out our Code of Conduct.
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f468119%2fhow-to-delete-space-between-author-and-semicolon-in-bibtex%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
@moewe oops thanks I deleted my comment, (If the OP had provided an example I would have tested first:-)
– David Carlisle
55 mins ago
For future questions, please consider adding a compilable example document instead of code snippets that have to be pieced together before they can be run. This is what we call an MWE (tex.meta.stackexchange.com/q/228/35864) or MWEB (tex.meta.stackexchange.com/q/4407/35864). MWEs make it much easier for people to get started helping you and they can avoid confusion by making sure that everyone is talking about the same thing. You can find examples of useful MWEs in the answers you got below.
– moewe
17 mins ago