Using a 'corporate author' in the “author” field of a bibliographic entry (spelling out the name in full)
I want to list a company name in the author field of a bibliographic entry:
@book{CUDA,
author = {NVIDIA Corporation},
title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide},
publisher = {NVIDIA Corporation},
year = {2007}
}
But the entry keeps showing up "N. Corporation". Is there a way to get the full author name to show up? I'm currently using the siam BibTEX style.
bibtex
add a comment |
I want to list a company name in the author field of a bibliographic entry:
@book{CUDA,
author = {NVIDIA Corporation},
title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide},
publisher = {NVIDIA Corporation},
year = {2007}
}
But the entry keeps showing up "N. Corporation". Is there a way to get the full author name to show up? I'm currently using the siam BibTEX style.
bibtex
add a comment |
I want to list a company name in the author field of a bibliographic entry:
@book{CUDA,
author = {NVIDIA Corporation},
title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide},
publisher = {NVIDIA Corporation},
year = {2007}
}
But the entry keeps showing up "N. Corporation". Is there a way to get the full author name to show up? I'm currently using the siam BibTEX style.
bibtex
I want to list a company name in the author field of a bibliographic entry:
@book{CUDA,
author = {NVIDIA Corporation},
title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide},
publisher = {NVIDIA Corporation},
year = {2007}
}
But the entry keeps showing up "N. Corporation". Is there a way to get the full author name to show up? I'm currently using the siam BibTEX style.
bibtex
bibtex
edited Mar 14 '15 at 10:48
Mico
273k30369756
273k30369756
asked Feb 11 '11 at 3:34
aterrel
388135
388135
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Just enclose the the author field in another set of braces:
@book{CUDA,
author = {{NVIDIA Corporation}},
title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide},
publisher = {NVIDIA Corporation},
year = {2007}
}
8
Enclosing in braces will also make BibTeX obey the capitalization.
– Kit
Feb 11 '11 at 4:42
2
@Kit - Making BibTeX obey capitalization by enclosing the material in an extra pair of curly braces is mainly of relevance for thetitlefield. To the best of my knowledge, no BibTeX style messes with the capitalization of names in theauthorandeditorfields.
– Mico
Jun 23 '14 at 8:08
Does not work well if you are using alphanumeric ordering for the references. A reference with author in double curly brackets will be listed at the very end of the bibliography. Any suggestions on how to fix?
– koo
Sep 15 '16 at 21:20
1
@koo Using thealphabibliography style either with or withoutnatbibsorts things correctly. So there's probably something else going on. If you can reproduce the problem with a minimal document you can ask a new question. See How to write a MWEB (Minimal working example with Bibliography)? for how to make the example.
– Alan Munn
Sep 15 '16 at 23:11
1
When working with the IEEE style, the double braces alone did not work for me. Adding a backslash did the trick:@book{CUDA, author = {{NVIDIA Corporation}}, title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide}, publisher = {NVIDIA Corporation}, year = {2007} }
– Alessandro Cuttin
Aug 21 '17 at 13:40
|
show 1 more 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%2f10808%2fusing-a-corporate-author-in-the-author-field-of-a-bibliographic-entry-spell%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Just enclose the the author field in another set of braces:
@book{CUDA,
author = {{NVIDIA Corporation}},
title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide},
publisher = {NVIDIA Corporation},
year = {2007}
}
8
Enclosing in braces will also make BibTeX obey the capitalization.
– Kit
Feb 11 '11 at 4:42
2
@Kit - Making BibTeX obey capitalization by enclosing the material in an extra pair of curly braces is mainly of relevance for thetitlefield. To the best of my knowledge, no BibTeX style messes with the capitalization of names in theauthorandeditorfields.
– Mico
Jun 23 '14 at 8:08
Does not work well if you are using alphanumeric ordering for the references. A reference with author in double curly brackets will be listed at the very end of the bibliography. Any suggestions on how to fix?
– koo
Sep 15 '16 at 21:20
1
@koo Using thealphabibliography style either with or withoutnatbibsorts things correctly. So there's probably something else going on. If you can reproduce the problem with a minimal document you can ask a new question. See How to write a MWEB (Minimal working example with Bibliography)? for how to make the example.
– Alan Munn
Sep 15 '16 at 23:11
1
When working with the IEEE style, the double braces alone did not work for me. Adding a backslash did the trick:@book{CUDA, author = {{NVIDIA Corporation}}, title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide}, publisher = {NVIDIA Corporation}, year = {2007} }
– Alessandro Cuttin
Aug 21 '17 at 13:40
|
show 1 more comment
Just enclose the the author field in another set of braces:
@book{CUDA,
author = {{NVIDIA Corporation}},
title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide},
publisher = {NVIDIA Corporation},
year = {2007}
}
8
Enclosing in braces will also make BibTeX obey the capitalization.
– Kit
Feb 11 '11 at 4:42
2
@Kit - Making BibTeX obey capitalization by enclosing the material in an extra pair of curly braces is mainly of relevance for thetitlefield. To the best of my knowledge, no BibTeX style messes with the capitalization of names in theauthorandeditorfields.
– Mico
Jun 23 '14 at 8:08
Does not work well if you are using alphanumeric ordering for the references. A reference with author in double curly brackets will be listed at the very end of the bibliography. Any suggestions on how to fix?
– koo
Sep 15 '16 at 21:20
1
@koo Using thealphabibliography style either with or withoutnatbibsorts things correctly. So there's probably something else going on. If you can reproduce the problem with a minimal document you can ask a new question. See How to write a MWEB (Minimal working example with Bibliography)? for how to make the example.
– Alan Munn
Sep 15 '16 at 23:11
1
When working with the IEEE style, the double braces alone did not work for me. Adding a backslash did the trick:@book{CUDA, author = {{NVIDIA Corporation}}, title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide}, publisher = {NVIDIA Corporation}, year = {2007} }
– Alessandro Cuttin
Aug 21 '17 at 13:40
|
show 1 more comment
Just enclose the the author field in another set of braces:
@book{CUDA,
author = {{NVIDIA Corporation}},
title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide},
publisher = {NVIDIA Corporation},
year = {2007}
}
Just enclose the the author field in another set of braces:
@book{CUDA,
author = {{NVIDIA Corporation}},
title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide},
publisher = {NVIDIA Corporation},
year = {2007}
}
answered Feb 11 '11 at 3:54
Alan Munn
158k27425700
158k27425700
8
Enclosing in braces will also make BibTeX obey the capitalization.
– Kit
Feb 11 '11 at 4:42
2
@Kit - Making BibTeX obey capitalization by enclosing the material in an extra pair of curly braces is mainly of relevance for thetitlefield. To the best of my knowledge, no BibTeX style messes with the capitalization of names in theauthorandeditorfields.
– Mico
Jun 23 '14 at 8:08
Does not work well if you are using alphanumeric ordering for the references. A reference with author in double curly brackets will be listed at the very end of the bibliography. Any suggestions on how to fix?
– koo
Sep 15 '16 at 21:20
1
@koo Using thealphabibliography style either with or withoutnatbibsorts things correctly. So there's probably something else going on. If you can reproduce the problem with a minimal document you can ask a new question. See How to write a MWEB (Minimal working example with Bibliography)? for how to make the example.
– Alan Munn
Sep 15 '16 at 23:11
1
When working with the IEEE style, the double braces alone did not work for me. Adding a backslash did the trick:@book{CUDA, author = {{NVIDIA Corporation}}, title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide}, publisher = {NVIDIA Corporation}, year = {2007} }
– Alessandro Cuttin
Aug 21 '17 at 13:40
|
show 1 more comment
8
Enclosing in braces will also make BibTeX obey the capitalization.
– Kit
Feb 11 '11 at 4:42
2
@Kit - Making BibTeX obey capitalization by enclosing the material in an extra pair of curly braces is mainly of relevance for thetitlefield. To the best of my knowledge, no BibTeX style messes with the capitalization of names in theauthorandeditorfields.
– Mico
Jun 23 '14 at 8:08
Does not work well if you are using alphanumeric ordering for the references. A reference with author in double curly brackets will be listed at the very end of the bibliography. Any suggestions on how to fix?
– koo
Sep 15 '16 at 21:20
1
@koo Using thealphabibliography style either with or withoutnatbibsorts things correctly. So there's probably something else going on. If you can reproduce the problem with a minimal document you can ask a new question. See How to write a MWEB (Minimal working example with Bibliography)? for how to make the example.
– Alan Munn
Sep 15 '16 at 23:11
1
When working with the IEEE style, the double braces alone did not work for me. Adding a backslash did the trick:@book{CUDA, author = {{NVIDIA Corporation}}, title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide}, publisher = {NVIDIA Corporation}, year = {2007} }
– Alessandro Cuttin
Aug 21 '17 at 13:40
8
8
Enclosing in braces will also make BibTeX obey the capitalization.
– Kit
Feb 11 '11 at 4:42
Enclosing in braces will also make BibTeX obey the capitalization.
– Kit
Feb 11 '11 at 4:42
2
2
@Kit - Making BibTeX obey capitalization by enclosing the material in an extra pair of curly braces is mainly of relevance for the
title field. To the best of my knowledge, no BibTeX style messes with the capitalization of names in the author and editor fields.– Mico
Jun 23 '14 at 8:08
@Kit - Making BibTeX obey capitalization by enclosing the material in an extra pair of curly braces is mainly of relevance for the
title field. To the best of my knowledge, no BibTeX style messes with the capitalization of names in the author and editor fields.– Mico
Jun 23 '14 at 8:08
Does not work well if you are using alphanumeric ordering for the references. A reference with author in double curly brackets will be listed at the very end of the bibliography. Any suggestions on how to fix?
– koo
Sep 15 '16 at 21:20
Does not work well if you are using alphanumeric ordering for the references. A reference with author in double curly brackets will be listed at the very end of the bibliography. Any suggestions on how to fix?
– koo
Sep 15 '16 at 21:20
1
1
@koo Using the
alpha bibliography style either with or without natbib sorts things correctly. So there's probably something else going on. If you can reproduce the problem with a minimal document you can ask a new question. See How to write a MWEB (Minimal working example with Bibliography)? for how to make the example.– Alan Munn
Sep 15 '16 at 23:11
@koo Using the
alpha bibliography style either with or without natbib sorts things correctly. So there's probably something else going on. If you can reproduce the problem with a minimal document you can ask a new question. See How to write a MWEB (Minimal working example with Bibliography)? for how to make the example.– Alan Munn
Sep 15 '16 at 23:11
1
1
When working with the IEEE style, the double braces alone did not work for me. Adding a backslash did the trick:
@book{CUDA, author = {{NVIDIA Corporation}}, title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide}, publisher = {NVIDIA Corporation}, year = {2007} }– Alessandro Cuttin
Aug 21 '17 at 13:40
When working with the IEEE style, the double braces alone did not work for me. Adding a backslash did the trick:
@book{CUDA, author = {{NVIDIA Corporation}}, title = {NVIDIA CUDA Compute Unified Device Architecture Programming Guide}, publisher = {NVIDIA Corporation}, year = {2007} }– Alessandro Cuttin
Aug 21 '17 at 13:40
|
show 1 more 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.
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%2f10808%2fusing-a-corporate-author-in-the-author-field-of-a-bibliographic-entry-spell%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