Understanding the template
for my thesis I got handed a TeX template and I was trying to understand the code before doing anything redundant or useless. I got most of it figured out but then there's this piece of code I can't decipher:
makeatletter
defthebibliography#1{chapter*{References@mkboth
{REFERENCES}{REFERENCES}}list
{[arabic{enumi}]}{settowidthlabelwidth{[#1]}leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}
defnewblock{hskip .11em plus .33em minus .07em}
sloppyclubpenalty4000widowpenalty4000
sfcode`.=1000relax}
makeatother
It's right before the bibliography.
Is anyone able to help me understand this arcane language?
bibliographies
|
show 5 more comments
for my thesis I got handed a TeX template and I was trying to understand the code before doing anything redundant or useless. I got most of it figured out but then there's this piece of code I can't decipher:
makeatletter
defthebibliography#1{chapter*{References@mkboth
{REFERENCES}{REFERENCES}}list
{[arabic{enumi}]}{settowidthlabelwidth{[#1]}leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}
defnewblock{hskip .11em plus .33em minus .07em}
sloppyclubpenalty4000widowpenalty4000
sfcode`.=1000relax}
makeatother
It's right before the bibliography.
Is anyone able to help me understand this arcane language?
bibliographies
1
Welcome to TeX.SE. Very nice your final comment :-).
– Sebastiano
Mar 6 at 20:53
1
Does your template also provide code forendthebibliography
?
– Mico
Mar 6 at 20:55
1
That template is mandatory in your University? If not, you are taking too long to delete it. My suggestions: (1) Start with a standard class as book, scrbook or memoir (2) Add only what you really understand and what you really really need (3) Take ideas from anywhere, but last site to search for outstanding code are the thesis templates (4) Write your bibliography usingbiblatex
, not writing directlybibtem
s in thethebibliography
environment (5) Remember the KISS principle.
– Fran
Mar 6 at 22:06
1
In this case there are probably 'better' ways (which are conceptually nicer and compatible with more standard idioms) to achieve the same result. (It should be enough to redefinebibname
to read "References", this could be done as in tex.stackexchange.com/q/82993/35864). That need not mean that the entire template is bad and should be avoided. But given the extensive contact many users here have had with bad templates it is good to be on guard.
– moewe
Mar 7 at 10:19
1
Of course the really bad issues only rear their heads a few hours before the important deadline.
– moewe
Mar 7 at 10:28
|
show 5 more comments
for my thesis I got handed a TeX template and I was trying to understand the code before doing anything redundant or useless. I got most of it figured out but then there's this piece of code I can't decipher:
makeatletter
defthebibliography#1{chapter*{References@mkboth
{REFERENCES}{REFERENCES}}list
{[arabic{enumi}]}{settowidthlabelwidth{[#1]}leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}
defnewblock{hskip .11em plus .33em minus .07em}
sloppyclubpenalty4000widowpenalty4000
sfcode`.=1000relax}
makeatother
It's right before the bibliography.
Is anyone able to help me understand this arcane language?
bibliographies
for my thesis I got handed a TeX template and I was trying to understand the code before doing anything redundant or useless. I got most of it figured out but then there's this piece of code I can't decipher:
makeatletter
defthebibliography#1{chapter*{References@mkboth
{REFERENCES}{REFERENCES}}list
{[arabic{enumi}]}{settowidthlabelwidth{[#1]}leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}
defnewblock{hskip .11em plus .33em minus .07em}
sloppyclubpenalty4000widowpenalty4000
sfcode`.=1000relax}
makeatother
It's right before the bibliography.
Is anyone able to help me understand this arcane language?
bibliographies
bibliographies
edited Mar 6 at 23:36
user31729
asked Mar 6 at 20:39
Superuser27Superuser27
61715
61715
1
Welcome to TeX.SE. Very nice your final comment :-).
– Sebastiano
Mar 6 at 20:53
1
Does your template also provide code forendthebibliography
?
– Mico
Mar 6 at 20:55
1
That template is mandatory in your University? If not, you are taking too long to delete it. My suggestions: (1) Start with a standard class as book, scrbook or memoir (2) Add only what you really understand and what you really really need (3) Take ideas from anywhere, but last site to search for outstanding code are the thesis templates (4) Write your bibliography usingbiblatex
, not writing directlybibtem
s in thethebibliography
environment (5) Remember the KISS principle.
– Fran
Mar 6 at 22:06
1
In this case there are probably 'better' ways (which are conceptually nicer and compatible with more standard idioms) to achieve the same result. (It should be enough to redefinebibname
to read "References", this could be done as in tex.stackexchange.com/q/82993/35864). That need not mean that the entire template is bad and should be avoided. But given the extensive contact many users here have had with bad templates it is good to be on guard.
– moewe
Mar 7 at 10:19
1
Of course the really bad issues only rear their heads a few hours before the important deadline.
– moewe
Mar 7 at 10:28
|
show 5 more comments
1
Welcome to TeX.SE. Very nice your final comment :-).
– Sebastiano
Mar 6 at 20:53
1
Does your template also provide code forendthebibliography
?
– Mico
Mar 6 at 20:55
1
That template is mandatory in your University? If not, you are taking too long to delete it. My suggestions: (1) Start with a standard class as book, scrbook or memoir (2) Add only what you really understand and what you really really need (3) Take ideas from anywhere, but last site to search for outstanding code are the thesis templates (4) Write your bibliography usingbiblatex
, not writing directlybibtem
s in thethebibliography
environment (5) Remember the KISS principle.
– Fran
Mar 6 at 22:06
1
In this case there are probably 'better' ways (which are conceptually nicer and compatible with more standard idioms) to achieve the same result. (It should be enough to redefinebibname
to read "References", this could be done as in tex.stackexchange.com/q/82993/35864). That need not mean that the entire template is bad and should be avoided. But given the extensive contact many users here have had with bad templates it is good to be on guard.
– moewe
Mar 7 at 10:19
1
Of course the really bad issues only rear their heads a few hours before the important deadline.
– moewe
Mar 7 at 10:28
1
1
Welcome to TeX.SE. Very nice your final comment :-).
– Sebastiano
Mar 6 at 20:53
Welcome to TeX.SE. Very nice your final comment :-).
– Sebastiano
Mar 6 at 20:53
1
1
Does your template also provide code for
endthebibliography
?– Mico
Mar 6 at 20:55
Does your template also provide code for
endthebibliography
?– Mico
Mar 6 at 20:55
1
1
That template is mandatory in your University? If not, you are taking too long to delete it. My suggestions: (1) Start with a standard class as book, scrbook or memoir (2) Add only what you really understand and what you really really need (3) Take ideas from anywhere, but last site to search for outstanding code are the thesis templates (4) Write your bibliography using
biblatex
, not writing directly bibtem
s in the thebibliography
environment (5) Remember the KISS principle.– Fran
Mar 6 at 22:06
That template is mandatory in your University? If not, you are taking too long to delete it. My suggestions: (1) Start with a standard class as book, scrbook or memoir (2) Add only what you really understand and what you really really need (3) Take ideas from anywhere, but last site to search for outstanding code are the thesis templates (4) Write your bibliography using
biblatex
, not writing directly bibtem
s in the thebibliography
environment (5) Remember the KISS principle.– Fran
Mar 6 at 22:06
1
1
In this case there are probably 'better' ways (which are conceptually nicer and compatible with more standard idioms) to achieve the same result. (It should be enough to redefine
bibname
to read "References", this could be done as in tex.stackexchange.com/q/82993/35864). That need not mean that the entire template is bad and should be avoided. But given the extensive contact many users here have had with bad templates it is good to be on guard.– moewe
Mar 7 at 10:19
In this case there are probably 'better' ways (which are conceptually nicer and compatible with more standard idioms) to achieve the same result. (It should be enough to redefine
bibname
to read "References", this could be done as in tex.stackexchange.com/q/82993/35864). That need not mean that the entire template is bad and should be avoided. But given the extensive contact many users here have had with bad templates it is good to be on guard.– moewe
Mar 7 at 10:19
1
1
Of course the really bad issues only rear their heads a few hours before the important deadline.
– moewe
Mar 7 at 10:28
Of course the really bad issues only rear their heads a few hours before the important deadline.
– moewe
Mar 7 at 10:28
|
show 5 more comments
1 Answer
1
active
oldest
votes
With slightly different indentation the code reads
makeatletter
defthebibliography#1{%
chapter*{References@mkboth{REFERENCES}{REFERENCES}}%
list
{[arabic{enumi}]}
{settowidthlabelwidth{[#1]}%
leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}%
defnewblock{hskip .11em plus .33em minus .07em}%
sloppy
clubpenalty4000
widowpenalty4000
sfcode`.=1000relax}
makeatother
It modifies the command thebibliography
that forms the basis of the begin code of
begin{thebibliography}{<longest label>}
bibitem{<key>} <entry text>
end{thebibliography}
In detail
chapter*{References@mkboth{REFERENCES}{REFERENCES}}%
First the code typesets an unnumbered chapter References and adds running heads on both sides reading REFERENCES.
list
{[arabic{enumi}]}
The bibliography is typeset as a list using the counter enumi
(a bit unusual, the standard implementations use the counter enumiv
, but normally that does not matter). The label number/label is wrapped in square brackets
{settowidthlabelwidth{[#1]}%
leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}%
This is standard stuff that sets up a list with sensible margins for this scenario.
defnewblock{hskip .11em plus .33em minus .07em}%
Defines the additional stretchable space that newblock
inserts. newblock
is a command issued by many bibliography styles to separate larger blocks of information in the bibliography. It allows for visual separation and can help improve line breaking with its additional stretchiness.
sloppy
Sets parameters for line breaking, see What is the meaning of fussy, sloppy, emergencystretch, tolerance, hbadness?. This setting is usually good at avoiding overfull, but could give sub-par result for longer paragraphs of text. For the bibliography that is probably acceptable.
clubpenalty4000
widowpenalty4000
Sets parameters to control widows and orphans. See How do I prevent widow/orphan lines? and https://texfaq.org/FAQ-widows.
sfcode`.=1000relax
Disable the larger space after sentence-ending .
s in the bibliography. See also Double space between sentences.
Compared to the standard definition in report.cls
(it's the same in book.cls
and only slightly different in article.cls
)
newenvironment{thebibliography}[1]
{chapter*{bibname}%
@mkboth{MakeUppercasebibname}{MakeUppercasebibname}%
list{@biblabel{@arabicc@enumiv}}%
{settowidthlabelwidth{@biblabel{#1}}%
leftmarginlabelwidth
advanceleftmarginlabelsep
@openbib@code
usecounter{enumiv}%
letp@enumiv@empty
renewcommandtheenumiv{@arabicc@enumiv}}%
sloppy
clubpenalty4000
@clubpenalty clubpenalty
widowpenalty4000%
sfcode`.@m}
{def@noitemerr
{@latex@warning{Empty `thebibliography' environment}}%
endlist}
newcommandnewblock{hskip .11em@plus.33em@minus.07em}
we note the following differences:
- Your code only redefines the begin code (presumably the end code is left unchanged).
- Your code uses
enumi
instead ofenumiv
. In practice that difference should hardly matter. - The standard code has customisable macros in some places where your code has hard-coded values (
[...]
vs@biblabel{...}
;References
vsbibname
; ).
- In particular the standard classes would print
bibname
, which defaults to Bibliography, while your code has References hard-coded. This is about the only visible difference between your code and the standard definition for 'normal use' (assuming the standard definition ofdef@biblabel#1{[#1]}
, which is hard-coded in your definition).
- In particular the standard classes would print
- Since your code redefines
newblock
in the begin code, all changes that are made to that command in the document will be void.
FWIW I found http://kb.mit.edu/confluence/x/YJ47 which recommends pretty much the code you showed. Alan Hoenig's TeX Unbound: LaTeX & TeX Strategies for Fonts, Graphics, & More shows a similar definition on p. 546. The definition is quite similar in style to the one in apalike.sty
. I also found several LaTeX 2.09 .sty
s with similar idioms using enumi
(http://mirrors.ctan.org/macros/latex209/contrib/misc/chapref.sty, http://mirrors.ctan.org/macros/latex209/contrib/misc/cites.sty). Maybe the code is inspired by older LaTeX 2.09 code?
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%2f478099%2funderstanding-the-template%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
With slightly different indentation the code reads
makeatletter
defthebibliography#1{%
chapter*{References@mkboth{REFERENCES}{REFERENCES}}%
list
{[arabic{enumi}]}
{settowidthlabelwidth{[#1]}%
leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}%
defnewblock{hskip .11em plus .33em minus .07em}%
sloppy
clubpenalty4000
widowpenalty4000
sfcode`.=1000relax}
makeatother
It modifies the command thebibliography
that forms the basis of the begin code of
begin{thebibliography}{<longest label>}
bibitem{<key>} <entry text>
end{thebibliography}
In detail
chapter*{References@mkboth{REFERENCES}{REFERENCES}}%
First the code typesets an unnumbered chapter References and adds running heads on both sides reading REFERENCES.
list
{[arabic{enumi}]}
The bibliography is typeset as a list using the counter enumi
(a bit unusual, the standard implementations use the counter enumiv
, but normally that does not matter). The label number/label is wrapped in square brackets
{settowidthlabelwidth{[#1]}%
leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}%
This is standard stuff that sets up a list with sensible margins for this scenario.
defnewblock{hskip .11em plus .33em minus .07em}%
Defines the additional stretchable space that newblock
inserts. newblock
is a command issued by many bibliography styles to separate larger blocks of information in the bibliography. It allows for visual separation and can help improve line breaking with its additional stretchiness.
sloppy
Sets parameters for line breaking, see What is the meaning of fussy, sloppy, emergencystretch, tolerance, hbadness?. This setting is usually good at avoiding overfull, but could give sub-par result for longer paragraphs of text. For the bibliography that is probably acceptable.
clubpenalty4000
widowpenalty4000
Sets parameters to control widows and orphans. See How do I prevent widow/orphan lines? and https://texfaq.org/FAQ-widows.
sfcode`.=1000relax
Disable the larger space after sentence-ending .
s in the bibliography. See also Double space between sentences.
Compared to the standard definition in report.cls
(it's the same in book.cls
and only slightly different in article.cls
)
newenvironment{thebibliography}[1]
{chapter*{bibname}%
@mkboth{MakeUppercasebibname}{MakeUppercasebibname}%
list{@biblabel{@arabicc@enumiv}}%
{settowidthlabelwidth{@biblabel{#1}}%
leftmarginlabelwidth
advanceleftmarginlabelsep
@openbib@code
usecounter{enumiv}%
letp@enumiv@empty
renewcommandtheenumiv{@arabicc@enumiv}}%
sloppy
clubpenalty4000
@clubpenalty clubpenalty
widowpenalty4000%
sfcode`.@m}
{def@noitemerr
{@latex@warning{Empty `thebibliography' environment}}%
endlist}
newcommandnewblock{hskip .11em@plus.33em@minus.07em}
we note the following differences:
- Your code only redefines the begin code (presumably the end code is left unchanged).
- Your code uses
enumi
instead ofenumiv
. In practice that difference should hardly matter. - The standard code has customisable macros in some places where your code has hard-coded values (
[...]
vs@biblabel{...}
;References
vsbibname
; ).
- In particular the standard classes would print
bibname
, which defaults to Bibliography, while your code has References hard-coded. This is about the only visible difference between your code and the standard definition for 'normal use' (assuming the standard definition ofdef@biblabel#1{[#1]}
, which is hard-coded in your definition).
- In particular the standard classes would print
- Since your code redefines
newblock
in the begin code, all changes that are made to that command in the document will be void.
FWIW I found http://kb.mit.edu/confluence/x/YJ47 which recommends pretty much the code you showed. Alan Hoenig's TeX Unbound: LaTeX & TeX Strategies for Fonts, Graphics, & More shows a similar definition on p. 546. The definition is quite similar in style to the one in apalike.sty
. I also found several LaTeX 2.09 .sty
s with similar idioms using enumi
(http://mirrors.ctan.org/macros/latex209/contrib/misc/chapref.sty, http://mirrors.ctan.org/macros/latex209/contrib/misc/cites.sty). Maybe the code is inspired by older LaTeX 2.09 code?
add a comment |
With slightly different indentation the code reads
makeatletter
defthebibliography#1{%
chapter*{References@mkboth{REFERENCES}{REFERENCES}}%
list
{[arabic{enumi}]}
{settowidthlabelwidth{[#1]}%
leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}%
defnewblock{hskip .11em plus .33em minus .07em}%
sloppy
clubpenalty4000
widowpenalty4000
sfcode`.=1000relax}
makeatother
It modifies the command thebibliography
that forms the basis of the begin code of
begin{thebibliography}{<longest label>}
bibitem{<key>} <entry text>
end{thebibliography}
In detail
chapter*{References@mkboth{REFERENCES}{REFERENCES}}%
First the code typesets an unnumbered chapter References and adds running heads on both sides reading REFERENCES.
list
{[arabic{enumi}]}
The bibliography is typeset as a list using the counter enumi
(a bit unusual, the standard implementations use the counter enumiv
, but normally that does not matter). The label number/label is wrapped in square brackets
{settowidthlabelwidth{[#1]}%
leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}%
This is standard stuff that sets up a list with sensible margins for this scenario.
defnewblock{hskip .11em plus .33em minus .07em}%
Defines the additional stretchable space that newblock
inserts. newblock
is a command issued by many bibliography styles to separate larger blocks of information in the bibliography. It allows for visual separation and can help improve line breaking with its additional stretchiness.
sloppy
Sets parameters for line breaking, see What is the meaning of fussy, sloppy, emergencystretch, tolerance, hbadness?. This setting is usually good at avoiding overfull, but could give sub-par result for longer paragraphs of text. For the bibliography that is probably acceptable.
clubpenalty4000
widowpenalty4000
Sets parameters to control widows and orphans. See How do I prevent widow/orphan lines? and https://texfaq.org/FAQ-widows.
sfcode`.=1000relax
Disable the larger space after sentence-ending .
s in the bibliography. See also Double space between sentences.
Compared to the standard definition in report.cls
(it's the same in book.cls
and only slightly different in article.cls
)
newenvironment{thebibliography}[1]
{chapter*{bibname}%
@mkboth{MakeUppercasebibname}{MakeUppercasebibname}%
list{@biblabel{@arabicc@enumiv}}%
{settowidthlabelwidth{@biblabel{#1}}%
leftmarginlabelwidth
advanceleftmarginlabelsep
@openbib@code
usecounter{enumiv}%
letp@enumiv@empty
renewcommandtheenumiv{@arabicc@enumiv}}%
sloppy
clubpenalty4000
@clubpenalty clubpenalty
widowpenalty4000%
sfcode`.@m}
{def@noitemerr
{@latex@warning{Empty `thebibliography' environment}}%
endlist}
newcommandnewblock{hskip .11em@plus.33em@minus.07em}
we note the following differences:
- Your code only redefines the begin code (presumably the end code is left unchanged).
- Your code uses
enumi
instead ofenumiv
. In practice that difference should hardly matter. - The standard code has customisable macros in some places where your code has hard-coded values (
[...]
vs@biblabel{...}
;References
vsbibname
; ).
- In particular the standard classes would print
bibname
, which defaults to Bibliography, while your code has References hard-coded. This is about the only visible difference between your code and the standard definition for 'normal use' (assuming the standard definition ofdef@biblabel#1{[#1]}
, which is hard-coded in your definition).
- In particular the standard classes would print
- Since your code redefines
newblock
in the begin code, all changes that are made to that command in the document will be void.
FWIW I found http://kb.mit.edu/confluence/x/YJ47 which recommends pretty much the code you showed. Alan Hoenig's TeX Unbound: LaTeX & TeX Strategies for Fonts, Graphics, & More shows a similar definition on p. 546. The definition is quite similar in style to the one in apalike.sty
. I also found several LaTeX 2.09 .sty
s with similar idioms using enumi
(http://mirrors.ctan.org/macros/latex209/contrib/misc/chapref.sty, http://mirrors.ctan.org/macros/latex209/contrib/misc/cites.sty). Maybe the code is inspired by older LaTeX 2.09 code?
add a comment |
With slightly different indentation the code reads
makeatletter
defthebibliography#1{%
chapter*{References@mkboth{REFERENCES}{REFERENCES}}%
list
{[arabic{enumi}]}
{settowidthlabelwidth{[#1]}%
leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}%
defnewblock{hskip .11em plus .33em minus .07em}%
sloppy
clubpenalty4000
widowpenalty4000
sfcode`.=1000relax}
makeatother
It modifies the command thebibliography
that forms the basis of the begin code of
begin{thebibliography}{<longest label>}
bibitem{<key>} <entry text>
end{thebibliography}
In detail
chapter*{References@mkboth{REFERENCES}{REFERENCES}}%
First the code typesets an unnumbered chapter References and adds running heads on both sides reading REFERENCES.
list
{[arabic{enumi}]}
The bibliography is typeset as a list using the counter enumi
(a bit unusual, the standard implementations use the counter enumiv
, but normally that does not matter). The label number/label is wrapped in square brackets
{settowidthlabelwidth{[#1]}%
leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}%
This is standard stuff that sets up a list with sensible margins for this scenario.
defnewblock{hskip .11em plus .33em minus .07em}%
Defines the additional stretchable space that newblock
inserts. newblock
is a command issued by many bibliography styles to separate larger blocks of information in the bibliography. It allows for visual separation and can help improve line breaking with its additional stretchiness.
sloppy
Sets parameters for line breaking, see What is the meaning of fussy, sloppy, emergencystretch, tolerance, hbadness?. This setting is usually good at avoiding overfull, but could give sub-par result for longer paragraphs of text. For the bibliography that is probably acceptable.
clubpenalty4000
widowpenalty4000
Sets parameters to control widows and orphans. See How do I prevent widow/orphan lines? and https://texfaq.org/FAQ-widows.
sfcode`.=1000relax
Disable the larger space after sentence-ending .
s in the bibliography. See also Double space between sentences.
Compared to the standard definition in report.cls
(it's the same in book.cls
and only slightly different in article.cls
)
newenvironment{thebibliography}[1]
{chapter*{bibname}%
@mkboth{MakeUppercasebibname}{MakeUppercasebibname}%
list{@biblabel{@arabicc@enumiv}}%
{settowidthlabelwidth{@biblabel{#1}}%
leftmarginlabelwidth
advanceleftmarginlabelsep
@openbib@code
usecounter{enumiv}%
letp@enumiv@empty
renewcommandtheenumiv{@arabicc@enumiv}}%
sloppy
clubpenalty4000
@clubpenalty clubpenalty
widowpenalty4000%
sfcode`.@m}
{def@noitemerr
{@latex@warning{Empty `thebibliography' environment}}%
endlist}
newcommandnewblock{hskip .11em@plus.33em@minus.07em}
we note the following differences:
- Your code only redefines the begin code (presumably the end code is left unchanged).
- Your code uses
enumi
instead ofenumiv
. In practice that difference should hardly matter. - The standard code has customisable macros in some places where your code has hard-coded values (
[...]
vs@biblabel{...}
;References
vsbibname
; ).
- In particular the standard classes would print
bibname
, which defaults to Bibliography, while your code has References hard-coded. This is about the only visible difference between your code and the standard definition for 'normal use' (assuming the standard definition ofdef@biblabel#1{[#1]}
, which is hard-coded in your definition).
- In particular the standard classes would print
- Since your code redefines
newblock
in the begin code, all changes that are made to that command in the document will be void.
FWIW I found http://kb.mit.edu/confluence/x/YJ47 which recommends pretty much the code you showed. Alan Hoenig's TeX Unbound: LaTeX & TeX Strategies for Fonts, Graphics, & More shows a similar definition on p. 546. The definition is quite similar in style to the one in apalike.sty
. I also found several LaTeX 2.09 .sty
s with similar idioms using enumi
(http://mirrors.ctan.org/macros/latex209/contrib/misc/chapref.sty, http://mirrors.ctan.org/macros/latex209/contrib/misc/cites.sty). Maybe the code is inspired by older LaTeX 2.09 code?
With slightly different indentation the code reads
makeatletter
defthebibliography#1{%
chapter*{References@mkboth{REFERENCES}{REFERENCES}}%
list
{[arabic{enumi}]}
{settowidthlabelwidth{[#1]}%
leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}%
defnewblock{hskip .11em plus .33em minus .07em}%
sloppy
clubpenalty4000
widowpenalty4000
sfcode`.=1000relax}
makeatother
It modifies the command thebibliography
that forms the basis of the begin code of
begin{thebibliography}{<longest label>}
bibitem{<key>} <entry text>
end{thebibliography}
In detail
chapter*{References@mkboth{REFERENCES}{REFERENCES}}%
First the code typesets an unnumbered chapter References and adds running heads on both sides reading REFERENCES.
list
{[arabic{enumi}]}
The bibliography is typeset as a list using the counter enumi
(a bit unusual, the standard implementations use the counter enumiv
, but normally that does not matter). The label number/label is wrapped in square brackets
{settowidthlabelwidth{[#1]}%
leftmarginlabelwidth
advanceleftmarginlabelsep
usecounter{enumi}}%
This is standard stuff that sets up a list with sensible margins for this scenario.
defnewblock{hskip .11em plus .33em minus .07em}%
Defines the additional stretchable space that newblock
inserts. newblock
is a command issued by many bibliography styles to separate larger blocks of information in the bibliography. It allows for visual separation and can help improve line breaking with its additional stretchiness.
sloppy
Sets parameters for line breaking, see What is the meaning of fussy, sloppy, emergencystretch, tolerance, hbadness?. This setting is usually good at avoiding overfull, but could give sub-par result for longer paragraphs of text. For the bibliography that is probably acceptable.
clubpenalty4000
widowpenalty4000
Sets parameters to control widows and orphans. See How do I prevent widow/orphan lines? and https://texfaq.org/FAQ-widows.
sfcode`.=1000relax
Disable the larger space after sentence-ending .
s in the bibliography. See also Double space between sentences.
Compared to the standard definition in report.cls
(it's the same in book.cls
and only slightly different in article.cls
)
newenvironment{thebibliography}[1]
{chapter*{bibname}%
@mkboth{MakeUppercasebibname}{MakeUppercasebibname}%
list{@biblabel{@arabicc@enumiv}}%
{settowidthlabelwidth{@biblabel{#1}}%
leftmarginlabelwidth
advanceleftmarginlabelsep
@openbib@code
usecounter{enumiv}%
letp@enumiv@empty
renewcommandtheenumiv{@arabicc@enumiv}}%
sloppy
clubpenalty4000
@clubpenalty clubpenalty
widowpenalty4000%
sfcode`.@m}
{def@noitemerr
{@latex@warning{Empty `thebibliography' environment}}%
endlist}
newcommandnewblock{hskip .11em@plus.33em@minus.07em}
we note the following differences:
- Your code only redefines the begin code (presumably the end code is left unchanged).
- Your code uses
enumi
instead ofenumiv
. In practice that difference should hardly matter. - The standard code has customisable macros in some places where your code has hard-coded values (
[...]
vs@biblabel{...}
;References
vsbibname
; ).
- In particular the standard classes would print
bibname
, which defaults to Bibliography, while your code has References hard-coded. This is about the only visible difference between your code and the standard definition for 'normal use' (assuming the standard definition ofdef@biblabel#1{[#1]}
, which is hard-coded in your definition).
- In particular the standard classes would print
- Since your code redefines
newblock
in the begin code, all changes that are made to that command in the document will be void.
FWIW I found http://kb.mit.edu/confluence/x/YJ47 which recommends pretty much the code you showed. Alan Hoenig's TeX Unbound: LaTeX & TeX Strategies for Fonts, Graphics, & More shows a similar definition on p. 546. The definition is quite similar in style to the one in apalike.sty
. I also found several LaTeX 2.09 .sty
s with similar idioms using enumi
(http://mirrors.ctan.org/macros/latex209/contrib/misc/chapref.sty, http://mirrors.ctan.org/macros/latex209/contrib/misc/cites.sty). Maybe the code is inspired by older LaTeX 2.09 code?
edited Mar 7 at 7:20
answered Mar 6 at 20:55
moewemoewe
93.7k10115353
93.7k10115353
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%2f478099%2funderstanding-the-template%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
1
Welcome to TeX.SE. Very nice your final comment :-).
– Sebastiano
Mar 6 at 20:53
1
Does your template also provide code for
endthebibliography
?– Mico
Mar 6 at 20:55
1
That template is mandatory in your University? If not, you are taking too long to delete it. My suggestions: (1) Start with a standard class as book, scrbook or memoir (2) Add only what you really understand and what you really really need (3) Take ideas from anywhere, but last site to search for outstanding code are the thesis templates (4) Write your bibliography using
biblatex
, not writing directlybibtem
s in thethebibliography
environment (5) Remember the KISS principle.– Fran
Mar 6 at 22:06
1
In this case there are probably 'better' ways (which are conceptually nicer and compatible with more standard idioms) to achieve the same result. (It should be enough to redefine
bibname
to read "References", this could be done as in tex.stackexchange.com/q/82993/35864). That need not mean that the entire template is bad and should be avoided. But given the extensive contact many users here have had with bad templates it is good to be on guard.– moewe
Mar 7 at 10:19
1
Of course the really bad issues only rear their heads a few hours before the important deadline.
– moewe
Mar 7 at 10:28