end description item with a dotFootnote to an item in a description environmentHow to align description item...

Why was the small council so happy for Tyrion to become the Master of Coin?

Can an x86 CPU running in real mode be considered to be basically an 8086 CPU?

How does strength of boric acid solution increase in presence of salicylic acid?

Email Account under attack (really) - anything I can do?

Why does Kotter return in Welcome Back Kotter?

Is there really no realistic way for a skeleton monster to move around without magic?

Is it unprofessional to ask if a job posting on GlassDoor is real?

Can I make popcorn with any corn?

Theorems that impeded progress

Why are weather verbs 曇る and 晴れる treated differently in this sentence?

How do we improve the relationship with a client software team that performs poorly and is becoming less collaborative?

How to feed LSTM with different input array sizes?

How to test if a transaction is standard without spending real money?

can i play a electric guitar through a bass amp?

How much RAM could one put in a typical 80386 setup?

Is it possible to rebuild the bike frame (to make it lighter) by welding aluminum tubes

Is there any sparring that doesn't involve punches to the head?

"You are your self first supporter", a more proper way to say it

What defenses are there against being summoned by the Gate spell?

What do you call a Matrix-like slowdown and camera movement effect?

How to re-create Edward Weson's Pepper No. 30?

Can a German sentence have two subjects?

Japan - Plan around max visa duration

What typically incentivizes a professor to change jobs to a lower ranking university?



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”













1















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:



enter image description here



Is there a way to tail automatically "it 1" and "ittt 2" with a dot?










share|improve this question





























    1















    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:



    enter image description here



    Is there a way to tail automatically "it 1" and "ittt 2" with a dot?










    share|improve this question



























      1












      1








      1








      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:



      enter image description here



      Is there a way to tail automatically "it 1" and "ittt 2" with a dot?










      share|improve this question
















      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:



      enter image description here



      Is there a way to tail automatically "it 1" and "ittt 2" with a dot?







      labels description






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 6 hours ago









      Bernard

      175k778208




      175k778208










      asked 7 hours ago









      ViestursViesturs

      1,96141227




      1,96141227






















          1 Answer
          1






          active

          oldest

          votes


















          2














          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.}


          **it 1.** description 1//**ittt 2.** description 2





          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.






          share|improve this answer





















          • 1





            +1, but it might be useful to note that this changes all description environments to have a period after the label.

            – egreg
            4 hours ago











          • @egreg Indeed, added a short comment about that. Thanks for the hint.

            – moewe
            4 hours ago






          • 1





            @WeijunZhou Fixed. Thanks.

            – moewe
            4 hours ago












          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
          });


          }
          });














          draft saved

          draft discarded


















          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









          2














          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.}


          **it 1.** description 1//**ittt 2.** description 2





          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.






          share|improve this answer





















          • 1





            +1, but it might be useful to note that this changes all description environments to have a period after the label.

            – egreg
            4 hours ago











          • @egreg Indeed, added a short comment about that. Thanks for the hint.

            – moewe
            4 hours ago






          • 1





            @WeijunZhou Fixed. Thanks.

            – moewe
            4 hours ago
















          2














          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.}


          **it 1.** description 1//**ittt 2.** description 2





          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.






          share|improve this answer





















          • 1





            +1, but it might be useful to note that this changes all description environments to have a period after the label.

            – egreg
            4 hours ago











          • @egreg Indeed, added a short comment about that. Thanks for the hint.

            – moewe
            4 hours ago






          • 1





            @WeijunZhou Fixed. Thanks.

            – moewe
            4 hours ago














          2












          2








          2







          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.}


          **it 1.** description 1//**ittt 2.** description 2





          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.






          share|improve this answer















          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.}


          **it 1.** description 1//**ittt 2.** description 2





          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.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 4 hours ago

























          answered 7 hours ago









          moewemoewe

          96.4k10117361




          96.4k10117361








          • 1





            +1, but it might be useful to note that this changes all description environments to have a period after the label.

            – egreg
            4 hours ago











          • @egreg Indeed, added a short comment about that. Thanks for the hint.

            – moewe
            4 hours ago






          • 1





            @WeijunZhou Fixed. Thanks.

            – moewe
            4 hours ago














          • 1





            +1, but it might be useful to note that this changes all description environments to have a period after the label.

            – egreg
            4 hours ago











          • @egreg Indeed, added a short comment about that. Thanks for the hint.

            – moewe
            4 hours ago






          • 1





            @WeijunZhou Fixed. Thanks.

            – moewe
            4 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
          4 hours ago





          +1, but it might be useful to note that this changes all description environments to have a period after the label.

          – egreg
          4 hours ago













          @egreg Indeed, added a short comment about that. Thanks for the hint.

          – moewe
          4 hours ago





          @egreg Indeed, added a short comment about that. Thanks for the hint.

          – moewe
          4 hours ago




          1




          1





          @WeijunZhou Fixed. Thanks.

          – moewe
          4 hours ago





          @WeijunZhou Fixed. Thanks.

          – moewe
          4 hours ago


















          draft saved

          draft discarded




















































          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.




          draft saved


          draft discarded














          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





















































          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







          Popular posts from this blog

          Installing LyX: “No textclass is found.”LyX installation error- text class not found- 'Reconfigure' or...

          (1602) Indiana Índice Designación y nombre Características orbitales Véase...

          Universidad Autónoma de Occidente Índice Historia Campus Facultades Programas Académicos Medios de...