Non-breaking space in citet using natbib?
When adding citations in the body of a document I'm used to write
... in some interesting paper~cite{interesting}.
So that (if I'm using numbered references) the word “paper” and the citation number stick together and do not accidentally end up in two different lines.
It seems, however, that the citet
command from natbib
(which should produce something like “Authors [4]”), does not use a ~
between the names of the authors and the citation number so that, on a few rare occasions, I end up with something like
... Authors
[4].
Which is annoying. Is there an easy way to make natbib
use a non-breaking space there?
spacing line-breaking natbib
add a comment |
When adding citations in the body of a document I'm used to write
... in some interesting paper~cite{interesting}.
So that (if I'm using numbered references) the word “paper” and the citation number stick together and do not accidentally end up in two different lines.
It seems, however, that the citet
command from natbib
(which should produce something like “Authors [4]”), does not use a ~
between the names of the authors and the citation number so that, on a few rare occasions, I end up with something like
... Authors
[4].
Which is annoying. Is there an easy way to make natbib
use a non-breaking space there?
spacing line-breaking natbib
add a comment |
When adding citations in the body of a document I'm used to write
... in some interesting paper~cite{interesting}.
So that (if I'm using numbered references) the word “paper” and the citation number stick together and do not accidentally end up in two different lines.
It seems, however, that the citet
command from natbib
(which should produce something like “Authors [4]”), does not use a ~
between the names of the authors and the citation number so that, on a few rare occasions, I end up with something like
... Authors
[4].
Which is annoying. Is there an easy way to make natbib
use a non-breaking space there?
spacing line-breaking natbib
When adding citations in the body of a document I'm used to write
... in some interesting paper~cite{interesting}.
So that (if I'm using numbered references) the word “paper” and the citation number stick together and do not accidentally end up in two different lines.
It seems, however, that the citet
command from natbib
(which should produce something like “Authors [4]”), does not use a ~
between the names of the authors and the citation number so that, on a few rare occasions, I end up with something like
... Authors
[4].
Which is annoying. Is there an easy way to make natbib
use a non-breaking space there?
spacing line-breaking natbib
spacing line-breaking natbib
edited Aug 5 '11 at 15:34
lockstep
193k53593723
193k53593723
asked Oct 25 '10 at 14:40
Juan A. NavarroJuan A. Navarro
36.7k27116163
36.7k27116163
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Looks like NAT@spacechar
needs to be redefined:
documentclass{article}
usepackage[numbers]{natbib}
makeatletter
% defNAT@spacechar{ }% OLD
defNAT@spacechar{~}% NEW
makeatother
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{a01,
author = {Author, A.},
year = {2001},
title = {Alpha},
}
end{filecontents}
begin{document}
Let's test if author and citation number end up in different lines: citet{a01}.
bibliographystyle{plainnat}
bibliography{jobname}
end{document}
Thanks! It does the trick. I wonder why this isn't the default behavior of natbib or, at least, there is an option to more easily set this.
– Juan A. Navarro
Oct 25 '10 at 15:49
1
I guess the default behavior was chosen with author-year-citations in mind, where allowing a line break between author and year is acceptable.
– lockstep
Oct 25 '10 at 15:58
2
Hey! I realize this is an almost 4 year old question, but I just tried to solve exactly the same line-breakingcitet{}
problem, and trying your suggestion did not make any difference. (I inserted the re-definition in the document preamble). Do you have any idea why that might be, or what I might try?
– penelope
Jun 24 '14 at 12:48
add a comment |
Since NAT@spacechar
is used, this redefinition prevents such breaks:
makeatletter
renewcommand*{NAT@spacechar}{~}
makeatother
This could affect also places where a break could be desired. Thus, an easy way for your rare occasions would be to use just mbox
around the citation:
... in the paper mbox{citet{interesting}}.
1
Also thanks for the suggestion. However note that thembox
wont always produce the desired result if the author name contains several words (or there are several authors), as there is nothing wrong with breaking the line between those names.
– Juan A. Navarro
Oct 25 '10 at 15:52
Stefans suggestion will also prevent hyphenation of author names.
– lockstep
Oct 25 '10 at 15:55
@Juan @lockstep: that's right! It's just intended to fix the line breaking for such occasions like in the question, where the author isn't hyphenated. Of course, such adjustment should be done at last, when the final version is being produced. This local correction avoids the global effect of changingNAT@spacechar
to be unbreakable.
– Stefan Kottwitz♦
Oct 25 '10 at 16:37
add a comment |
lockstep and Stefan Kottwitz suggest redefining NAT@spacechar
. That may have worked at one time, but I find that it no longer works now, seven years later, using natbib 2010/09/13 8.31b (PWD, AO)
from TeXLive 2016. A comment from @penelope also mentions that this approach was no longer working as of mid-2014.
The following strategy does work for me as of now. Add the following to your document preamble somewhere after usepackage{natbib}
:
bibpunct{nolinebreak{}[}{]}{,}{n}{}{,}
The key piece of this is the nolinebreak{}[
, which discourages LaTeX from breaking a line before the [
that starts a group of bracketed citation numbers. The remaining arguments to bibpunct
merely replicate the standard punctuation for bracketed, numbered citations.
Note that the {}
immediately after nolinebreak
is not really an empty argument to nolinebreak
. Rather, it simply prevents nolinebreak
from mistaking the following [
for the start of an optional argument. That being said, nolinebreak
does accept an optional argument that determines how strongly a break should be discouraged. So you could instead use something like bibpunct{nolinebreak[0][}{]}{,}{n}{}{,}
to make the no-break directive merely a mild request, all the way up to bibpunct{nolinebreak[4][}{]}{,}{n}{}{,}
for a strict demand. The latter is equivalent to the default treatment you get if you use the bibpunct{nolinebreak{}[}{]}{,}{n}{}{,}
form I suggested initially.
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
});
}
});
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%2f4542%2fnon-breaking-space-in-citet-using-natbib%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Looks like NAT@spacechar
needs to be redefined:
documentclass{article}
usepackage[numbers]{natbib}
makeatletter
% defNAT@spacechar{ }% OLD
defNAT@spacechar{~}% NEW
makeatother
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{a01,
author = {Author, A.},
year = {2001},
title = {Alpha},
}
end{filecontents}
begin{document}
Let's test if author and citation number end up in different lines: citet{a01}.
bibliographystyle{plainnat}
bibliography{jobname}
end{document}
Thanks! It does the trick. I wonder why this isn't the default behavior of natbib or, at least, there is an option to more easily set this.
– Juan A. Navarro
Oct 25 '10 at 15:49
1
I guess the default behavior was chosen with author-year-citations in mind, where allowing a line break between author and year is acceptable.
– lockstep
Oct 25 '10 at 15:58
2
Hey! I realize this is an almost 4 year old question, but I just tried to solve exactly the same line-breakingcitet{}
problem, and trying your suggestion did not make any difference. (I inserted the re-definition in the document preamble). Do you have any idea why that might be, or what I might try?
– penelope
Jun 24 '14 at 12:48
add a comment |
Looks like NAT@spacechar
needs to be redefined:
documentclass{article}
usepackage[numbers]{natbib}
makeatletter
% defNAT@spacechar{ }% OLD
defNAT@spacechar{~}% NEW
makeatother
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{a01,
author = {Author, A.},
year = {2001},
title = {Alpha},
}
end{filecontents}
begin{document}
Let's test if author and citation number end up in different lines: citet{a01}.
bibliographystyle{plainnat}
bibliography{jobname}
end{document}
Thanks! It does the trick. I wonder why this isn't the default behavior of natbib or, at least, there is an option to more easily set this.
– Juan A. Navarro
Oct 25 '10 at 15:49
1
I guess the default behavior was chosen with author-year-citations in mind, where allowing a line break between author and year is acceptable.
– lockstep
Oct 25 '10 at 15:58
2
Hey! I realize this is an almost 4 year old question, but I just tried to solve exactly the same line-breakingcitet{}
problem, and trying your suggestion did not make any difference. (I inserted the re-definition in the document preamble). Do you have any idea why that might be, or what I might try?
– penelope
Jun 24 '14 at 12:48
add a comment |
Looks like NAT@spacechar
needs to be redefined:
documentclass{article}
usepackage[numbers]{natbib}
makeatletter
% defNAT@spacechar{ }% OLD
defNAT@spacechar{~}% NEW
makeatother
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{a01,
author = {Author, A.},
year = {2001},
title = {Alpha},
}
end{filecontents}
begin{document}
Let's test if author and citation number end up in different lines: citet{a01}.
bibliographystyle{plainnat}
bibliography{jobname}
end{document}
Looks like NAT@spacechar
needs to be redefined:
documentclass{article}
usepackage[numbers]{natbib}
makeatletter
% defNAT@spacechar{ }% OLD
defNAT@spacechar{~}% NEW
makeatother
usepackage{filecontents}
begin{filecontents}{jobname.bib}
@misc{a01,
author = {Author, A.},
year = {2001},
title = {Alpha},
}
end{filecontents}
begin{document}
Let's test if author and citation number end up in different lines: citet{a01}.
bibliographystyle{plainnat}
bibliography{jobname}
end{document}
answered Oct 25 '10 at 15:40
locksteplockstep
193k53593723
193k53593723
Thanks! It does the trick. I wonder why this isn't the default behavior of natbib or, at least, there is an option to more easily set this.
– Juan A. Navarro
Oct 25 '10 at 15:49
1
I guess the default behavior was chosen with author-year-citations in mind, where allowing a line break between author and year is acceptable.
– lockstep
Oct 25 '10 at 15:58
2
Hey! I realize this is an almost 4 year old question, but I just tried to solve exactly the same line-breakingcitet{}
problem, and trying your suggestion did not make any difference. (I inserted the re-definition in the document preamble). Do you have any idea why that might be, or what I might try?
– penelope
Jun 24 '14 at 12:48
add a comment |
Thanks! It does the trick. I wonder why this isn't the default behavior of natbib or, at least, there is an option to more easily set this.
– Juan A. Navarro
Oct 25 '10 at 15:49
1
I guess the default behavior was chosen with author-year-citations in mind, where allowing a line break between author and year is acceptable.
– lockstep
Oct 25 '10 at 15:58
2
Hey! I realize this is an almost 4 year old question, but I just tried to solve exactly the same line-breakingcitet{}
problem, and trying your suggestion did not make any difference. (I inserted the re-definition in the document preamble). Do you have any idea why that might be, or what I might try?
– penelope
Jun 24 '14 at 12:48
Thanks! It does the trick. I wonder why this isn't the default behavior of natbib or, at least, there is an option to more easily set this.
– Juan A. Navarro
Oct 25 '10 at 15:49
Thanks! It does the trick. I wonder why this isn't the default behavior of natbib or, at least, there is an option to more easily set this.
– Juan A. Navarro
Oct 25 '10 at 15:49
1
1
I guess the default behavior was chosen with author-year-citations in mind, where allowing a line break between author and year is acceptable.
– lockstep
Oct 25 '10 at 15:58
I guess the default behavior was chosen with author-year-citations in mind, where allowing a line break between author and year is acceptable.
– lockstep
Oct 25 '10 at 15:58
2
2
Hey! I realize this is an almost 4 year old question, but I just tried to solve exactly the same line-breaking
citet{}
problem, and trying your suggestion did not make any difference. (I inserted the re-definition in the document preamble). Do you have any idea why that might be, or what I might try?– penelope
Jun 24 '14 at 12:48
Hey! I realize this is an almost 4 year old question, but I just tried to solve exactly the same line-breaking
citet{}
problem, and trying your suggestion did not make any difference. (I inserted the re-definition in the document preamble). Do you have any idea why that might be, or what I might try?– penelope
Jun 24 '14 at 12:48
add a comment |
Since NAT@spacechar
is used, this redefinition prevents such breaks:
makeatletter
renewcommand*{NAT@spacechar}{~}
makeatother
This could affect also places where a break could be desired. Thus, an easy way for your rare occasions would be to use just mbox
around the citation:
... in the paper mbox{citet{interesting}}.
1
Also thanks for the suggestion. However note that thembox
wont always produce the desired result if the author name contains several words (or there are several authors), as there is nothing wrong with breaking the line between those names.
– Juan A. Navarro
Oct 25 '10 at 15:52
Stefans suggestion will also prevent hyphenation of author names.
– lockstep
Oct 25 '10 at 15:55
@Juan @lockstep: that's right! It's just intended to fix the line breaking for such occasions like in the question, where the author isn't hyphenated. Of course, such adjustment should be done at last, when the final version is being produced. This local correction avoids the global effect of changingNAT@spacechar
to be unbreakable.
– Stefan Kottwitz♦
Oct 25 '10 at 16:37
add a comment |
Since NAT@spacechar
is used, this redefinition prevents such breaks:
makeatletter
renewcommand*{NAT@spacechar}{~}
makeatother
This could affect also places where a break could be desired. Thus, an easy way for your rare occasions would be to use just mbox
around the citation:
... in the paper mbox{citet{interesting}}.
1
Also thanks for the suggestion. However note that thembox
wont always produce the desired result if the author name contains several words (or there are several authors), as there is nothing wrong with breaking the line between those names.
– Juan A. Navarro
Oct 25 '10 at 15:52
Stefans suggestion will also prevent hyphenation of author names.
– lockstep
Oct 25 '10 at 15:55
@Juan @lockstep: that's right! It's just intended to fix the line breaking for such occasions like in the question, where the author isn't hyphenated. Of course, such adjustment should be done at last, when the final version is being produced. This local correction avoids the global effect of changingNAT@spacechar
to be unbreakable.
– Stefan Kottwitz♦
Oct 25 '10 at 16:37
add a comment |
Since NAT@spacechar
is used, this redefinition prevents such breaks:
makeatletter
renewcommand*{NAT@spacechar}{~}
makeatother
This could affect also places where a break could be desired. Thus, an easy way for your rare occasions would be to use just mbox
around the citation:
... in the paper mbox{citet{interesting}}.
Since NAT@spacechar
is used, this redefinition prevents such breaks:
makeatletter
renewcommand*{NAT@spacechar}{~}
makeatother
This could affect also places where a break could be desired. Thus, an easy way for your rare occasions would be to use just mbox
around the citation:
... in the paper mbox{citet{interesting}}.
answered Oct 25 '10 at 15:49
Stefan Kottwitz♦Stefan Kottwitz
179k65573762
179k65573762
1
Also thanks for the suggestion. However note that thembox
wont always produce the desired result if the author name contains several words (or there are several authors), as there is nothing wrong with breaking the line between those names.
– Juan A. Navarro
Oct 25 '10 at 15:52
Stefans suggestion will also prevent hyphenation of author names.
– lockstep
Oct 25 '10 at 15:55
@Juan @lockstep: that's right! It's just intended to fix the line breaking for such occasions like in the question, where the author isn't hyphenated. Of course, such adjustment should be done at last, when the final version is being produced. This local correction avoids the global effect of changingNAT@spacechar
to be unbreakable.
– Stefan Kottwitz♦
Oct 25 '10 at 16:37
add a comment |
1
Also thanks for the suggestion. However note that thembox
wont always produce the desired result if the author name contains several words (or there are several authors), as there is nothing wrong with breaking the line between those names.
– Juan A. Navarro
Oct 25 '10 at 15:52
Stefans suggestion will also prevent hyphenation of author names.
– lockstep
Oct 25 '10 at 15:55
@Juan @lockstep: that's right! It's just intended to fix the line breaking for such occasions like in the question, where the author isn't hyphenated. Of course, such adjustment should be done at last, when the final version is being produced. This local correction avoids the global effect of changingNAT@spacechar
to be unbreakable.
– Stefan Kottwitz♦
Oct 25 '10 at 16:37
1
1
Also thanks for the suggestion. However note that the
mbox
wont always produce the desired result if the author name contains several words (or there are several authors), as there is nothing wrong with breaking the line between those names.– Juan A. Navarro
Oct 25 '10 at 15:52
Also thanks for the suggestion. However note that the
mbox
wont always produce the desired result if the author name contains several words (or there are several authors), as there is nothing wrong with breaking the line between those names.– Juan A. Navarro
Oct 25 '10 at 15:52
Stefans suggestion will also prevent hyphenation of author names.
– lockstep
Oct 25 '10 at 15:55
Stefans suggestion will also prevent hyphenation of author names.
– lockstep
Oct 25 '10 at 15:55
@Juan @lockstep: that's right! It's just intended to fix the line breaking for such occasions like in the question, where the author isn't hyphenated. Of course, such adjustment should be done at last, when the final version is being produced. This local correction avoids the global effect of changing
NAT@spacechar
to be unbreakable.– Stefan Kottwitz♦
Oct 25 '10 at 16:37
@Juan @lockstep: that's right! It's just intended to fix the line breaking for such occasions like in the question, where the author isn't hyphenated. Of course, such adjustment should be done at last, when the final version is being produced. This local correction avoids the global effect of changing
NAT@spacechar
to be unbreakable.– Stefan Kottwitz♦
Oct 25 '10 at 16:37
add a comment |
lockstep and Stefan Kottwitz suggest redefining NAT@spacechar
. That may have worked at one time, but I find that it no longer works now, seven years later, using natbib 2010/09/13 8.31b (PWD, AO)
from TeXLive 2016. A comment from @penelope also mentions that this approach was no longer working as of mid-2014.
The following strategy does work for me as of now. Add the following to your document preamble somewhere after usepackage{natbib}
:
bibpunct{nolinebreak{}[}{]}{,}{n}{}{,}
The key piece of this is the nolinebreak{}[
, which discourages LaTeX from breaking a line before the [
that starts a group of bracketed citation numbers. The remaining arguments to bibpunct
merely replicate the standard punctuation for bracketed, numbered citations.
Note that the {}
immediately after nolinebreak
is not really an empty argument to nolinebreak
. Rather, it simply prevents nolinebreak
from mistaking the following [
for the start of an optional argument. That being said, nolinebreak
does accept an optional argument that determines how strongly a break should be discouraged. So you could instead use something like bibpunct{nolinebreak[0][}{]}{,}{n}{}{,}
to make the no-break directive merely a mild request, all the way up to bibpunct{nolinebreak[4][}{]}{,}{n}{}{,}
for a strict demand. The latter is equivalent to the default treatment you get if you use the bibpunct{nolinebreak{}[}{]}{,}{n}{}{,}
form I suggested initially.
add a comment |
lockstep and Stefan Kottwitz suggest redefining NAT@spacechar
. That may have worked at one time, but I find that it no longer works now, seven years later, using natbib 2010/09/13 8.31b (PWD, AO)
from TeXLive 2016. A comment from @penelope also mentions that this approach was no longer working as of mid-2014.
The following strategy does work for me as of now. Add the following to your document preamble somewhere after usepackage{natbib}
:
bibpunct{nolinebreak{}[}{]}{,}{n}{}{,}
The key piece of this is the nolinebreak{}[
, which discourages LaTeX from breaking a line before the [
that starts a group of bracketed citation numbers. The remaining arguments to bibpunct
merely replicate the standard punctuation for bracketed, numbered citations.
Note that the {}
immediately after nolinebreak
is not really an empty argument to nolinebreak
. Rather, it simply prevents nolinebreak
from mistaking the following [
for the start of an optional argument. That being said, nolinebreak
does accept an optional argument that determines how strongly a break should be discouraged. So you could instead use something like bibpunct{nolinebreak[0][}{]}{,}{n}{}{,}
to make the no-break directive merely a mild request, all the way up to bibpunct{nolinebreak[4][}{]}{,}{n}{}{,}
for a strict demand. The latter is equivalent to the default treatment you get if you use the bibpunct{nolinebreak{}[}{]}{,}{n}{}{,}
form I suggested initially.
add a comment |
lockstep and Stefan Kottwitz suggest redefining NAT@spacechar
. That may have worked at one time, but I find that it no longer works now, seven years later, using natbib 2010/09/13 8.31b (PWD, AO)
from TeXLive 2016. A comment from @penelope also mentions that this approach was no longer working as of mid-2014.
The following strategy does work for me as of now. Add the following to your document preamble somewhere after usepackage{natbib}
:
bibpunct{nolinebreak{}[}{]}{,}{n}{}{,}
The key piece of this is the nolinebreak{}[
, which discourages LaTeX from breaking a line before the [
that starts a group of bracketed citation numbers. The remaining arguments to bibpunct
merely replicate the standard punctuation for bracketed, numbered citations.
Note that the {}
immediately after nolinebreak
is not really an empty argument to nolinebreak
. Rather, it simply prevents nolinebreak
from mistaking the following [
for the start of an optional argument. That being said, nolinebreak
does accept an optional argument that determines how strongly a break should be discouraged. So you could instead use something like bibpunct{nolinebreak[0][}{]}{,}{n}{}{,}
to make the no-break directive merely a mild request, all the way up to bibpunct{nolinebreak[4][}{]}{,}{n}{}{,}
for a strict demand. The latter is equivalent to the default treatment you get if you use the bibpunct{nolinebreak{}[}{]}{,}{n}{}{,}
form I suggested initially.
lockstep and Stefan Kottwitz suggest redefining NAT@spacechar
. That may have worked at one time, but I find that it no longer works now, seven years later, using natbib 2010/09/13 8.31b (PWD, AO)
from TeXLive 2016. A comment from @penelope also mentions that this approach was no longer working as of mid-2014.
The following strategy does work for me as of now. Add the following to your document preamble somewhere after usepackage{natbib}
:
bibpunct{nolinebreak{}[}{]}{,}{n}{}{,}
The key piece of this is the nolinebreak{}[
, which discourages LaTeX from breaking a line before the [
that starts a group of bracketed citation numbers. The remaining arguments to bibpunct
merely replicate the standard punctuation for bracketed, numbered citations.
Note that the {}
immediately after nolinebreak
is not really an empty argument to nolinebreak
. Rather, it simply prevents nolinebreak
from mistaking the following [
for the start of an optional argument. That being said, nolinebreak
does accept an optional argument that determines how strongly a break should be discouraged. So you could instead use something like bibpunct{nolinebreak[0][}{]}{,}{n}{}{,}
to make the no-break directive merely a mild request, all the way up to bibpunct{nolinebreak[4][}{]}{,}{n}{}{,}
for a strict demand. The latter is equivalent to the default treatment you get if you use the bibpunct{nolinebreak{}[}{]}{,}{n}{}{,}
form I suggested initially.
edited 44 mins ago
answered Apr 15 '17 at 22:21
Ben LiblitBen Liblit
973816
973816
add a comment |
add a comment |
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%2f4542%2fnon-breaking-space-in-citet-using-natbib%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