end description item with a dotFootnote to an item in a description environmentHow to align description item...
GPS Rollover on Android Smartphones
What are these boxed doors outside store fronts in New York?
Is it tax fraud for an individual to declare non-taxable revenue as taxable income? (US tax laws)
What defenses are there against being summoned by the Gate spell?
Why don't electromagnetic waves interact with each other?
Do any Labour MPs support no-deal?
Can an x86 CPU running in real mode be considered to be basically an 8086 CPU?
How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?
Type 1 Error & Type 2 Error's pregnancy test analogy: is it legit?
Can a German sentence have two subjects?
If I cast Expeditious Retreat, can I Dash as a bonus action on the same turn?
DOS, create pipe for stdin/stdout of command.com(or 4dos.com) in C or Batch?
Can I make popcorn with any corn?
Modeling an IPv4 Address
Mathematical cryptic clues
Mains transformer blew up amplifier, incorrect description in wiring instructions?
How to write a macro that is braces sensitive?
TGV timetables / schedules?
XeLaTeX and pdfLaTeX ignore hyphenation
The use of multiple foreign keys on same column in SQL Server
How to add power-LED to my small amplifier?
How much RAM could one put in a typical 80386 setup?
"which" command doesn't work / path of Safari?
"You are your self first supporter", a more proper way to say it
end description item with a dot
Footnote to an item in a description environmentHow to align description item labels on the right?force long text inside item[{texttt{}] to wrapItemize item on new line when nested in a descriptionLine break after description labelshow “continued” for nested description list item on page breakRemove whitespace after item in descriptionNumbered description list with dot leaders?Reduce the space between label and item in a description listBeamer Overlay for the “description” of the “item label”
Consider this example:
documentclass{report}
begin{document}
begin{description}
item[it 1] description 1
item[ittt 2] description 2
end{description}
end{document}
which renders:

Is there a way to tail automatically "it 1" and "ittt 2" with a dot?
labels description
add a comment |
Consider this example:
documentclass{report}
begin{document}
begin{description}
item[it 1] description 1
item[ittt 2] description 2
end{description}
end{document}
which renders:

Is there a way to tail automatically "it 1" and "ittt 2" with a dot?
labels description
add a comment |
Consider this example:
documentclass{report}
begin{document}
begin{description}
item[it 1] description 1
item[ittt 2] description 2
end{description}
end{document}
which renders:

Is there a way to tail automatically "it 1" and "ittt 2" with a dot?
labels description
Consider this example:
documentclass{report}
begin{document}
begin{description}
item[it 1] description 1
item[ittt 2] description 2
end{description}
end{document}
which renders:

Is there a way to tail automatically "it 1" and "ittt 2" with a dot?
labels description
labels description
edited 7 hours ago
Bernard
175k778208
175k778208
asked 8 hours ago
ViestursViesturs
1,96141227
1,96141227
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The command descriptionlabel controls the format of the description label. Its default definition, which you can find in ll. 438-439 of report.cls, is
newcommand*descriptionlabel[1]{hspacelabelsep
normalfontbfseries #1}
You can include a period and make it read
renewcommand*descriptionlabel[1]{hspacelabelsep
normalfontbfseries #1.}

If applied in the preamble this change is global and affects all description environments. If you want to change only one environment you can keep the redefinition local with grouping
begingroup
renewcommand*descriptionlabel[1]{%
hspacelabelsep
normalfontbfseries #1.}
begin{description}
item[it 1] description 1
item[ittt 2] description 2
end{description}
endgroup
If you are using enumitem something like
newcommand*dotteddescriptionlabel[1]{%
normalfontbfseries #1.}
in the preamble and then
begin{description}[format=dotteddescriptionlabel]
item[it 1] description 1
item[ittt 2] description 2
end{description}
would also work since format may take an argument. Indeed
newcommand*dotteddescriptionlabel[1]{#1.}
would have been enough since the remaining format settings are inherited from the standard dotteddescriptionlabel.
1
+1, but it might be useful to note that this changes alldescriptionenvironments to have a period after the label.
– egreg
5 hours ago
@egreg Indeed, added a short comment about that. Thanks for the hint.
– moewe
5 hours ago
1
@WeijunZhou Fixed. Thanks.
– moewe
5 hours ago
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%2f483636%2fend-description-item-with-a-dot%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
The command descriptionlabel controls the format of the description label. Its default definition, which you can find in ll. 438-439 of report.cls, is
newcommand*descriptionlabel[1]{hspacelabelsep
normalfontbfseries #1}
You can include a period and make it read
renewcommand*descriptionlabel[1]{hspacelabelsep
normalfontbfseries #1.}

If applied in the preamble this change is global and affects all description environments. If you want to change only one environment you can keep the redefinition local with grouping
begingroup
renewcommand*descriptionlabel[1]{%
hspacelabelsep
normalfontbfseries #1.}
begin{description}
item[it 1] description 1
item[ittt 2] description 2
end{description}
endgroup
If you are using enumitem something like
newcommand*dotteddescriptionlabel[1]{%
normalfontbfseries #1.}
in the preamble and then
begin{description}[format=dotteddescriptionlabel]
item[it 1] description 1
item[ittt 2] description 2
end{description}
would also work since format may take an argument. Indeed
newcommand*dotteddescriptionlabel[1]{#1.}
would have been enough since the remaining format settings are inherited from the standard dotteddescriptionlabel.
1
+1, but it might be useful to note that this changes alldescriptionenvironments to have a period after the label.
– egreg
5 hours ago
@egreg Indeed, added a short comment about that. Thanks for the hint.
– moewe
5 hours ago
1
@WeijunZhou Fixed. Thanks.
– moewe
5 hours ago
add a comment |
The command descriptionlabel controls the format of the description label. Its default definition, which you can find in ll. 438-439 of report.cls, is
newcommand*descriptionlabel[1]{hspacelabelsep
normalfontbfseries #1}
You can include a period and make it read
renewcommand*descriptionlabel[1]{hspacelabelsep
normalfontbfseries #1.}

If applied in the preamble this change is global and affects all description environments. If you want to change only one environment you can keep the redefinition local with grouping
begingroup
renewcommand*descriptionlabel[1]{%
hspacelabelsep
normalfontbfseries #1.}
begin{description}
item[it 1] description 1
item[ittt 2] description 2
end{description}
endgroup
If you are using enumitem something like
newcommand*dotteddescriptionlabel[1]{%
normalfontbfseries #1.}
in the preamble and then
begin{description}[format=dotteddescriptionlabel]
item[it 1] description 1
item[ittt 2] description 2
end{description}
would also work since format may take an argument. Indeed
newcommand*dotteddescriptionlabel[1]{#1.}
would have been enough since the remaining format settings are inherited from the standard dotteddescriptionlabel.
1
+1, but it might be useful to note that this changes alldescriptionenvironments to have a period after the label.
– egreg
5 hours ago
@egreg Indeed, added a short comment about that. Thanks for the hint.
– moewe
5 hours ago
1
@WeijunZhou Fixed. Thanks.
– moewe
5 hours ago
add a comment |
The command descriptionlabel controls the format of the description label. Its default definition, which you can find in ll. 438-439 of report.cls, is
newcommand*descriptionlabel[1]{hspacelabelsep
normalfontbfseries #1}
You can include a period and make it read
renewcommand*descriptionlabel[1]{hspacelabelsep
normalfontbfseries #1.}

If applied in the preamble this change is global and affects all description environments. If you want to change only one environment you can keep the redefinition local with grouping
begingroup
renewcommand*descriptionlabel[1]{%
hspacelabelsep
normalfontbfseries #1.}
begin{description}
item[it 1] description 1
item[ittt 2] description 2
end{description}
endgroup
If you are using enumitem something like
newcommand*dotteddescriptionlabel[1]{%
normalfontbfseries #1.}
in the preamble and then
begin{description}[format=dotteddescriptionlabel]
item[it 1] description 1
item[ittt 2] description 2
end{description}
would also work since format may take an argument. Indeed
newcommand*dotteddescriptionlabel[1]{#1.}
would have been enough since the remaining format settings are inherited from the standard dotteddescriptionlabel.
The command descriptionlabel controls the format of the description label. Its default definition, which you can find in ll. 438-439 of report.cls, is
newcommand*descriptionlabel[1]{hspacelabelsep
normalfontbfseries #1}
You can include a period and make it read
renewcommand*descriptionlabel[1]{hspacelabelsep
normalfontbfseries #1.}

If applied in the preamble this change is global and affects all description environments. If you want to change only one environment you can keep the redefinition local with grouping
begingroup
renewcommand*descriptionlabel[1]{%
hspacelabelsep
normalfontbfseries #1.}
begin{description}
item[it 1] description 1
item[ittt 2] description 2
end{description}
endgroup
If you are using enumitem something like
newcommand*dotteddescriptionlabel[1]{%
normalfontbfseries #1.}
in the preamble and then
begin{description}[format=dotteddescriptionlabel]
item[it 1] description 1
item[ittt 2] description 2
end{description}
would also work since format may take an argument. Indeed
newcommand*dotteddescriptionlabel[1]{#1.}
would have been enough since the remaining format settings are inherited from the standard dotteddescriptionlabel.
edited 5 hours ago
answered 8 hours ago
moewemoewe
96.4k10117361
96.4k10117361
1
+1, but it might be useful to note that this changes alldescriptionenvironments to have a period after the label.
– egreg
5 hours ago
@egreg Indeed, added a short comment about that. Thanks for the hint.
– moewe
5 hours ago
1
@WeijunZhou Fixed. Thanks.
– moewe
5 hours ago
add a comment |
1
+1, but it might be useful to note that this changes alldescriptionenvironments to have a period after the label.
– egreg
5 hours ago
@egreg Indeed, added a short comment about that. Thanks for the hint.
– moewe
5 hours ago
1
@WeijunZhou Fixed. Thanks.
– moewe
5 hours ago
1
1
+1, but it might be useful to note that this changes all
description environments to have a period after the label.– egreg
5 hours ago
+1, but it might be useful to note that this changes all
description environments to have a period after the label.– egreg
5 hours ago
@egreg Indeed, added a short comment about that. Thanks for the hint.
– moewe
5 hours ago
@egreg Indeed, added a short comment about that. Thanks for the hint.
– moewe
5 hours ago
1
1
@WeijunZhou Fixed. Thanks.
– moewe
5 hours ago
@WeijunZhou Fixed. Thanks.
– moewe
5 hours ago
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%2f483636%2fend-description-item-with-a-dot%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