List of deprecated commands and their `appreciated' alternatives












14















I'm wondering if there is a list of deprecated LaTeX commands and suggestions for commands that are to be used instead.






macros incompatibility robust-commands







share|improve this question

























  • not really, there are no commands in the latex format officially classed as deprecated, and if you include contributed packages, there are thousands of packages, some of which may or may not be classed as replacements or improvements on other packages, depending who you ask.

    – David Carlisle
    Jan 13 '17 at 0:36






  • 1





    You can find suggestions under the best-practices tag, such as this question or this one.

    – Kurzd
    Jan 13 '17 at 2:39













  • Related: How to keep up with packages and know which ones are obsolete?

    – Werner
    Jan 13 at 20:36
















14















I'm wondering if there is a list of deprecated LaTeX commands and suggestions for commands that are to be used instead.






macros incompatibility robust-commands







share|improve this question

























  • not really, there are no commands in the latex format officially classed as deprecated, and if you include contributed packages, there are thousands of packages, some of which may or may not be classed as replacements or improvements on other packages, depending who you ask.

    – David Carlisle
    Jan 13 '17 at 0:36






  • 1





    You can find suggestions under the best-practices tag, such as this question or this one.

    – Kurzd
    Jan 13 '17 at 2:39













  • Related: How to keep up with packages and know which ones are obsolete?

    – Werner
    Jan 13 at 20:36














14












14








14


3






I'm wondering if there is a list of deprecated LaTeX commands and suggestions for commands that are to be used instead.






macros incompatibility robust-commands







share|improve this question
















I'm wondering if there is a list of deprecated LaTeX commands and suggestions for commands that are to be used instead.






macros incompatibility robust-commands




macros incompatibility robust-commands






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 13 '17 at 10:11









egreg

714k8618953184




714k8618953184










asked Jan 13 '17 at 0:09









marmotmarmot

93.1k4109204




93.1k4109204













  • not really, there are no commands in the latex format officially classed as deprecated, and if you include contributed packages, there are thousands of packages, some of which may or may not be classed as replacements or improvements on other packages, depending who you ask.

    – David Carlisle
    Jan 13 '17 at 0:36






  • 1





    You can find suggestions under the best-practices tag, such as this question or this one.

    – Kurzd
    Jan 13 '17 at 2:39













  • Related: How to keep up with packages and know which ones are obsolete?

    – Werner
    Jan 13 at 20:36



















  • not really, there are no commands in the latex format officially classed as deprecated, and if you include contributed packages, there are thousands of packages, some of which may or may not be classed as replacements or improvements on other packages, depending who you ask.

    – David Carlisle
    Jan 13 '17 at 0:36






  • 1





    You can find suggestions under the best-practices tag, such as this question or this one.

    – Kurzd
    Jan 13 '17 at 2:39













  • Related: How to keep up with packages and know which ones are obsolete?

    – Werner
    Jan 13 at 20:36

















not really, there are no commands in the latex format officially classed as deprecated, and if you include contributed packages, there are thousands of packages, some of which may or may not be classed as replacements or improvements on other packages, depending who you ask.

– David Carlisle
Jan 13 '17 at 0:36





not really, there are no commands in the latex format officially classed as deprecated, and if you include contributed packages, there are thousands of packages, some of which may or may not be classed as replacements or improvements on other packages, depending who you ask.

– David Carlisle
Jan 13 '17 at 0:36




1




1





You can find suggestions under the best-practices tag, such as this question or this one.

– Kurzd
Jan 13 '17 at 2:39







You can find suggestions under the best-practices tag, such as this question or this one.

– Kurzd
Jan 13 '17 at 2:39















Related: How to keep up with packages and know which ones are obsolete?

– Werner
Jan 13 at 20:36





Related: How to keep up with packages and know which ones are obsolete?

– Werner
Jan 13 at 20:36










1 Answer
1






active

oldest

votes


















15














Short answer: Run texdoc l2tabuen in the OS prompt.



Long answer: Although may be are not officially deprecated LaTeX2e commands, as David said, novices often fall in old documentation, examples and templates, taking obsolete or not well understood practices, as writing the non-deprecated '{a} when with minimal settings in the preamble and a suitable keyboard you can simply write "á", or using the deprecated {bf ... } of LaTeX2.0, that do not use the new font selection scheme (NFSS) of LaTeX2e, instead of textbf{...} or {bfseries ...}, or using obsolete packages (as anysize to set up document margins instead of the ge­om­e­try pack­age) and even obsolete fonts and classes.



One should mention also inputenc, in no way an obsolete package, but since utf8 is actually the gold standard encoding, use of usepackage[utf8]{inputenc} with pdflatex is obsolete at least in standard classes because is now the default, but the novice will see this command in thousands of examples anywhere. It will take time to forget it!



Others, not so novices tend to use TeX commands instead of the LaTeX syntax (often my fault), as parindent1em instead of setlength{parindent}{1em} or deffoo{...} instead of newcommandfoo{..}. In my defense I will say that this is fine while you understand the risks.



Many of these common pitfalls are covered by the l2tabu german document (note that there are an English version as well as in some other languages).






share|improve this answer


























  • On your note about inputenc: It's not actually deprecated, but since April 2018 the file utf8.def (loaded by usepackage[utf8]{inputenc}) is included in LaTeX by default, so including usepackage[utf8]{inputenc} in releases later than April 2018 will simply do nothing. And since this is in the LaTeX kernel, it affects any document class, not only the standard ones :)

    – Phelype Oleinik
    Jan 13 at 20:25











  • @PhelypeOleinik I did not say that is a deprecated package, just the contrary ("in no way an obsolete package"). With respect a non standard class, I just created the xxx.cls custom class that is LoadClass{article} usepackage[latin1]{inputenc} and therefore utf8 is no longer the default encoding of any document class. :)

    – Fran
    Jan 13 at 21:34













  • Ooh, yes, if the class forces an encoding, then it's another story :)

    – Phelype Oleinik
    Jan 13 at 21:37











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%2f348453%2flist-of-deprecated-commands-and-their-appreciated-alternatives%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









15














Short answer: Run texdoc l2tabuen in the OS prompt.



Long answer: Although may be are not officially deprecated LaTeX2e commands, as David said, novices often fall in old documentation, examples and templates, taking obsolete or not well understood practices, as writing the non-deprecated '{a} when with minimal settings in the preamble and a suitable keyboard you can simply write "á", or using the deprecated {bf ... } of LaTeX2.0, that do not use the new font selection scheme (NFSS) of LaTeX2e, instead of textbf{...} or {bfseries ...}, or using obsolete packages (as anysize to set up document margins instead of the ge­om­e­try pack­age) and even obsolete fonts and classes.



One should mention also inputenc, in no way an obsolete package, but since utf8 is actually the gold standard encoding, use of usepackage[utf8]{inputenc} with pdflatex is obsolete at least in standard classes because is now the default, but the novice will see this command in thousands of examples anywhere. It will take time to forget it!



Others, not so novices tend to use TeX commands instead of the LaTeX syntax (often my fault), as parindent1em instead of setlength{parindent}{1em} or deffoo{...} instead of newcommandfoo{..}. In my defense I will say that this is fine while you understand the risks.



Many of these common pitfalls are covered by the l2tabu german document (note that there are an English version as well as in some other languages).






share|improve this answer


























  • On your note about inputenc: It's not actually deprecated, but since April 2018 the file utf8.def (loaded by usepackage[utf8]{inputenc}) is included in LaTeX by default, so including usepackage[utf8]{inputenc} in releases later than April 2018 will simply do nothing. And since this is in the LaTeX kernel, it affects any document class, not only the standard ones :)

    – Phelype Oleinik
    Jan 13 at 20:25











  • @PhelypeOleinik I did not say that is a deprecated package, just the contrary ("in no way an obsolete package"). With respect a non standard class, I just created the xxx.cls custom class that is LoadClass{article} usepackage[latin1]{inputenc} and therefore utf8 is no longer the default encoding of any document class. :)

    – Fran
    Jan 13 at 21:34













  • Ooh, yes, if the class forces an encoding, then it's another story :)

    – Phelype Oleinik
    Jan 13 at 21:37
















15














Short answer: Run texdoc l2tabuen in the OS prompt.



Long answer: Although may be are not officially deprecated LaTeX2e commands, as David said, novices often fall in old documentation, examples and templates, taking obsolete or not well understood practices, as writing the non-deprecated '{a} when with minimal settings in the preamble and a suitable keyboard you can simply write "á", or using the deprecated {bf ... } of LaTeX2.0, that do not use the new font selection scheme (NFSS) of LaTeX2e, instead of textbf{...} or {bfseries ...}, or using obsolete packages (as anysize to set up document margins instead of the ge­om­e­try pack­age) and even obsolete fonts and classes.



One should mention also inputenc, in no way an obsolete package, but since utf8 is actually the gold standard encoding, use of usepackage[utf8]{inputenc} with pdflatex is obsolete at least in standard classes because is now the default, but the novice will see this command in thousands of examples anywhere. It will take time to forget it!



Others, not so novices tend to use TeX commands instead of the LaTeX syntax (often my fault), as parindent1em instead of setlength{parindent}{1em} or deffoo{...} instead of newcommandfoo{..}. In my defense I will say that this is fine while you understand the risks.



Many of these common pitfalls are covered by the l2tabu german document (note that there are an English version as well as in some other languages).






share|improve this answer


























  • On your note about inputenc: It's not actually deprecated, but since April 2018 the file utf8.def (loaded by usepackage[utf8]{inputenc}) is included in LaTeX by default, so including usepackage[utf8]{inputenc} in releases later than April 2018 will simply do nothing. And since this is in the LaTeX kernel, it affects any document class, not only the standard ones :)

    – Phelype Oleinik
    Jan 13 at 20:25











  • @PhelypeOleinik I did not say that is a deprecated package, just the contrary ("in no way an obsolete package"). With respect a non standard class, I just created the xxx.cls custom class that is LoadClass{article} usepackage[latin1]{inputenc} and therefore utf8 is no longer the default encoding of any document class. :)

    – Fran
    Jan 13 at 21:34













  • Ooh, yes, if the class forces an encoding, then it's another story :)

    – Phelype Oleinik
    Jan 13 at 21:37














15












15








15







Short answer: Run texdoc l2tabuen in the OS prompt.



Long answer: Although may be are not officially deprecated LaTeX2e commands, as David said, novices often fall in old documentation, examples and templates, taking obsolete or not well understood practices, as writing the non-deprecated '{a} when with minimal settings in the preamble and a suitable keyboard you can simply write "á", or using the deprecated {bf ... } of LaTeX2.0, that do not use the new font selection scheme (NFSS) of LaTeX2e, instead of textbf{...} or {bfseries ...}, or using obsolete packages (as anysize to set up document margins instead of the ge­om­e­try pack­age) and even obsolete fonts and classes.



One should mention also inputenc, in no way an obsolete package, but since utf8 is actually the gold standard encoding, use of usepackage[utf8]{inputenc} with pdflatex is obsolete at least in standard classes because is now the default, but the novice will see this command in thousands of examples anywhere. It will take time to forget it!



Others, not so novices tend to use TeX commands instead of the LaTeX syntax (often my fault), as parindent1em instead of setlength{parindent}{1em} or deffoo{...} instead of newcommandfoo{..}. In my defense I will say that this is fine while you understand the risks.



Many of these common pitfalls are covered by the l2tabu german document (note that there are an English version as well as in some other languages).






share|improve this answer















Short answer: Run texdoc l2tabuen in the OS prompt.



Long answer: Although may be are not officially deprecated LaTeX2e commands, as David said, novices often fall in old documentation, examples and templates, taking obsolete or not well understood practices, as writing the non-deprecated '{a} when with minimal settings in the preamble and a suitable keyboard you can simply write "á", or using the deprecated {bf ... } of LaTeX2.0, that do not use the new font selection scheme (NFSS) of LaTeX2e, instead of textbf{...} or {bfseries ...}, or using obsolete packages (as anysize to set up document margins instead of the ge­om­e­try pack­age) and even obsolete fonts and classes.



One should mention also inputenc, in no way an obsolete package, but since utf8 is actually the gold standard encoding, use of usepackage[utf8]{inputenc} with pdflatex is obsolete at least in standard classes because is now the default, but the novice will see this command in thousands of examples anywhere. It will take time to forget it!



Others, not so novices tend to use TeX commands instead of the LaTeX syntax (often my fault), as parindent1em instead of setlength{parindent}{1em} or deffoo{...} instead of newcommandfoo{..}. In my defense I will say that this is fine while you understand the risks.



Many of these common pitfalls are covered by the l2tabu german document (note that there are an English version as well as in some other languages).







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 13 at 20:13









Phelype Oleinik

21.6k54381




21.6k54381










answered Jan 13 '17 at 3:12









FranFran

51.9k6115176




51.9k6115176













  • On your note about inputenc: It's not actually deprecated, but since April 2018 the file utf8.def (loaded by usepackage[utf8]{inputenc}) is included in LaTeX by default, so including usepackage[utf8]{inputenc} in releases later than April 2018 will simply do nothing. And since this is in the LaTeX kernel, it affects any document class, not only the standard ones :)

    – Phelype Oleinik
    Jan 13 at 20:25











  • @PhelypeOleinik I did not say that is a deprecated package, just the contrary ("in no way an obsolete package"). With respect a non standard class, I just created the xxx.cls custom class that is LoadClass{article} usepackage[latin1]{inputenc} and therefore utf8 is no longer the default encoding of any document class. :)

    – Fran
    Jan 13 at 21:34













  • Ooh, yes, if the class forces an encoding, then it's another story :)

    – Phelype Oleinik
    Jan 13 at 21:37



















  • On your note about inputenc: It's not actually deprecated, but since April 2018 the file utf8.def (loaded by usepackage[utf8]{inputenc}) is included in LaTeX by default, so including usepackage[utf8]{inputenc} in releases later than April 2018 will simply do nothing. And since this is in the LaTeX kernel, it affects any document class, not only the standard ones :)

    – Phelype Oleinik
    Jan 13 at 20:25











  • @PhelypeOleinik I did not say that is a deprecated package, just the contrary ("in no way an obsolete package"). With respect a non standard class, I just created the xxx.cls custom class that is LoadClass{article} usepackage[latin1]{inputenc} and therefore utf8 is no longer the default encoding of any document class. :)

    – Fran
    Jan 13 at 21:34













  • Ooh, yes, if the class forces an encoding, then it's another story :)

    – Phelype Oleinik
    Jan 13 at 21:37

















On your note about inputenc: It's not actually deprecated, but since April 2018 the file utf8.def (loaded by usepackage[utf8]{inputenc}) is included in LaTeX by default, so including usepackage[utf8]{inputenc} in releases later than April 2018 will simply do nothing. And since this is in the LaTeX kernel, it affects any document class, not only the standard ones :)

– Phelype Oleinik
Jan 13 at 20:25





On your note about inputenc: It's not actually deprecated, but since April 2018 the file utf8.def (loaded by usepackage[utf8]{inputenc}) is included in LaTeX by default, so including usepackage[utf8]{inputenc} in releases later than April 2018 will simply do nothing. And since this is in the LaTeX kernel, it affects any document class, not only the standard ones :)

– Phelype Oleinik
Jan 13 at 20:25













@PhelypeOleinik I did not say that is a deprecated package, just the contrary ("in no way an obsolete package"). With respect a non standard class, I just created the xxx.cls custom class that is LoadClass{article} usepackage[latin1]{inputenc} and therefore utf8 is no longer the default encoding of any document class. :)

– Fran
Jan 13 at 21:34







@PhelypeOleinik I did not say that is a deprecated package, just the contrary ("in no way an obsolete package"). With respect a non standard class, I just created the xxx.cls custom class that is LoadClass{article} usepackage[latin1]{inputenc} and therefore utf8 is no longer the default encoding of any document class. :)

– Fran
Jan 13 at 21:34















Ooh, yes, if the class forces an encoding, then it's another story :)

– Phelype Oleinik
Jan 13 at 21:37





Ooh, yes, if the class forces an encoding, then it's another story :)

– Phelype Oleinik
Jan 13 at 21:37


















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%2f348453%2flist-of-deprecated-commands-and-their-appreciated-alternatives%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

How to change which sound is reproduced for terminal bell?

Image
3 Recently upgrade to 18.10 from 18.04, and using the terminal is becoming annoying: the new alert sound is a drip ( /usr/share/sounds/gnome/default/alerts/drip.ogg ), and the previous one is still located at ( /usr/share/sounds/ubuntu/stereo/bell.ogg ). My issue is that at the gnome-terminal, when autocompleting or pressing left BOTH sounds are reproduced, at the same time. I want to just have ubuntu/stereo/bell.ogg active, not both . At the moment I have been only able to reduce the volume of the alerts (but still both are played), or turn the alerts down (but I dislike both "solutions"). gnome-terminal 18.10 teminal-bell share | improve this question
Read more

Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

Image
up vote 5 down vote favorite 2 I would like to make it so that the vertical space below the title of each chapter is the same when using the Bjornstrup package (i.e. so that the descenders do not affect the spacing - as shown by the red arrow in the picture below). I think I'm fairly happy with the spacing around "A chapter", so I'd really like titles without descenders (e.g. "Contents") to have the same vertical spacing as "A chapter" below the title. I would also like to remove the large "0" in the contents title. Any help appreciated, as always. documentclass[11pt,a4paper]{book} % Packages[![enter image description here][1]][1] usepackage[left=3.5cm, right=3.5cm, top=4.3cm, bottom=4.25cm]{geometry} usepackage[utf8]{inputenc} usepackage{libertine} usepackage[libertine]{newtx
Read more

Can I use Tabulator js library in my java Spring + Thymeleaf project?

Image
0 I want to add Tabulator js to my java project. I added tabulator.min.js, tabulator.min.css to resources folder. After that added to my html page these dependencies as recommending in readme.md. <link rel="stylesheet" th:href="@{/css/tabulator.min.css}"> <script type="text/javascript" th:src="@{/js/tabulator.min.js}"></script> Now my tables view all elements, that I have in the html page, but not correct. In the documentation of Tabulator is example how to create header and table, var table = new Tabulator("#example-table", { columns:[ {title:"Name", field:"name", sorter:"string", width:200, editor:true}, {title:"Age", field:"age", sorter:"
Read more