subsection command not working in elsevier LaTeX template
1
I am working on Elsevier template with a single column format, I am facing an issue with subsections command not working as they are displayed like a normal section with wrong numbering, for example
documentclass[a4paper,fleqn]{cas-sc}
begin{document}
section{A}
subsection{AA}
subsubsection{BB}
end{document}
Can anyone help me on how to fix this issue?
elsevier
asked Feb 15 at 15:52
Noman BashirNoman Bashir
82
|
show 1 more comment
1
I am working on Elsevier template with a single column format, I am facing an issue with subsections command not working as they are displayed like a normal section with wrong numbering, for example
documentclass[a4paper,fleqn]{cas-sc}
begin{document}
section{A}
subsection{AA}
subsubsection{BB}
end{document}
Can anyone help me on how to fix this issue?
elsevier
asked Feb 15 at 15:52
Noman BashirNoman Bashir
82
@campa sorry, I could not understand your response. What is correct?
– Noman Bashir
Feb 15 at 16:01
@campa I just googled it (after commenting) and found it. Would you look at that, Elsevier switched toexpl3:). Well, then I think this is the expected behaviour...
– Phelype Oleinik
Feb 15 at 16:01
campa replied to a comment I deleted, so it looked out of context.
– Phelype Oleinik
Feb 15 at 16:02
Okay, what is the final situation now?
– Noman Bashir
Feb 15 at 16:02
Your example is minimal and there is nothing wrong with it, so it's not your fault. I think you'd need to contact the Elsevier support and ask it there. There are two possibilities: 1) This is a design choice and you have to live with it. 2) It's a bug and they need to fix it (looks more like it). Either way, only they know the answer, unfortunately.
– Phelype Oleinik
Feb 15 at 16:07
|
show 1 more comment
1
1
1
I am working on Elsevier template with a single column format, I am facing an issue with subsections command not working as they are displayed like a normal section with wrong numbering, for example
documentclass[a4paper,fleqn]{cas-sc}
begin{document}
section{A}
subsection{AA}
subsubsection{BB}
end{document}
Can anyone help me on how to fix this issue?
elsevier
asked Feb 15 at 15:52
Noman BashirNoman Bashir
82
I am working on Elsevier template with a single column format, I am facing an issue with subsections command not working as they are displayed like a normal section with wrong numbering, for example
documentclass[a4paper,fleqn]{cas-sc}
begin{document}
section{A}
subsection{AA}
subsubsection{BB}
end{document}
Can anyone help me on how to fix this issue?
elsevier
elsevier
asked Feb 15 at 15:52
Noman BashirNoman Bashir
82
asked Feb 15 at 15:52
Noman BashirNoman Bashir
82
asked Feb 15 at 15:52
Noman BashirNoman Bashir
82
asked Feb 15 at 15:52
Noman BashirNoman Bashir
82
asked Feb 15 at 15:52
Noman BashirNoman Bashir
82
82
@campa sorry, I could not understand your response. What is correct?
– Noman Bashir
Feb 15 at 16:01
@campa I just googled it (after commenting) and found it. Would you look at that, Elsevier switched toexpl3:). Well, then I think this is the expected behaviour...
– Phelype Oleinik
Feb 15 at 16:01
campa replied to a comment I deleted, so it looked out of context.
– Phelype Oleinik
Feb 15 at 16:02
Okay, what is the final situation now?
– Noman Bashir
Feb 15 at 16:02
Your example is minimal and there is nothing wrong with it, so it's not your fault. I think you'd need to contact the Elsevier support and ask it there. There are two possibilities: 1) This is a design choice and you have to live with it. 2) It's a bug and they need to fix it (looks more like it). Either way, only they know the answer, unfortunately.
– Phelype Oleinik
Feb 15 at 16:07
|
show 1 more comment
@campa sorry, I could not understand your response. What is correct?
– Noman Bashir
Feb 15 at 16:01
@campa I just googled it (after commenting) and found it. Would you look at that, Elsevier switched toexpl3:). Well, then I think this is the expected behaviour...
– Phelype Oleinik
Feb 15 at 16:01
campa replied to a comment I deleted, so it looked out of context.
– Phelype Oleinik
Feb 15 at 16:02
Okay, what is the final situation now?
– Noman Bashir
Feb 15 at 16:02
Your example is minimal and there is nothing wrong with it, so it's not your fault. I think you'd need to contact the Elsevier support and ask it there. There are two possibilities: 1) This is a design choice and you have to live with it. 2) It's a bug and they need to fix it (looks more like it). Either way, only they know the answer, unfortunately.
– Phelype Oleinik
Feb 15 at 16:07
@campa sorry, I could not understand your response. What is correct?
– Noman Bashir
Feb 15 at 16:01
@campa sorry, I could not understand your response. What is correct?
– Noman Bashir
Feb 15 at 16:01
@campa I just googled it (after commenting) and found it. Would you look at that, Elsevier switched to
expl3 :). Well, then I think this is the expected behaviour...– Phelype Oleinik
Feb 15 at 16:01
@campa I just googled it (after commenting) and found it. Would you look at that, Elsevier switched to
expl3 :). Well, then I think this is the expected behaviour...– Phelype Oleinik
Feb 15 at 16:01
campa replied to a comment I deleted, so it looked out of context.
– Phelype Oleinik
Feb 15 at 16:02
campa replied to a comment I deleted, so it looked out of context.
– Phelype Oleinik
Feb 15 at 16:02
Okay, what is the final situation now?
– Noman Bashir
Feb 15 at 16:02
Okay, what is the final situation now?
– Noman Bashir
Feb 15 at 16:02
Your example is minimal and there is nothing wrong with it, so it's not your fault. I think you'd need to contact the Elsevier support and ask it there. There are two possibilities: 1) This is a design choice and you have to live with it. 2) It's a bug and they need to fix it (looks more like it). Either way, only they know the answer, unfortunately.
– Phelype Oleinik
Feb 15 at 16:07
Your example is minimal and there is nothing wrong with it, so it's not your fault. I think you'd need to contact the Elsevier support and ask it there. There are two possibilities: 1) This is a design choice and you have to live with it. 2) It's a bug and they need to fix it (looks more like it). Either way, only they know the answer, unfortunately.
– Phelype Oleinik
Feb 15 at 16:07
|
show 1 more comment
1 Answer
1
active
oldest
votes
1
Yes, definitely a bug :)
The definition of section, subsection, and subsubsection in cas-common.sty uses the same counter, section, for all three levels. (i.e.: @startsection{section}...). If you copy that definition and use the correct counters the output looks correct:
documentclass[a4paper,fleqn]{cas-sc}
begin{document}
makeatletter
renewcommandsection{@startsection{section}{1}{z@}%
{15pt @plus 3p@ @minus 3p@}%
{4p@}%
{%let@hangfromrelax
sectionfontraggedrighthst[13pt]}}
renewcommandsubsection{@startsection{subsection}{2}{z@}%
{10pt @plus 3p@ @minus 2p@}%
{.1p@}%
{%let@hangfromrelax
ssectionfontraggedright }}
renewcommandsubsubsection{@startsection{subsubsection}{3}{z@}%
{10pt @plus 1p@ @minus .3p@}%
{.1p@}%
{%let@hangfromrelax
sssectionfontraggedright}}
makeatother
section{A}
subsection{AA}
subsubsection{BB}
end{document}
answered Feb 15 at 16:16
Phelype OleinikPhelype Oleinik
23.5k54586
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
});
}
});
draft saved
draft discarded
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%2f475049%2fsubsection-command-not-working-in-elsevier-latex-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
1
Yes, definitely a bug :)
The definition of section, subsection, and subsubsection in cas-common.sty uses the same counter, section, for all three levels. (i.e.: @startsection{section}...). If you copy that definition and use the correct counters the output looks correct:
documentclass[a4paper,fleqn]{cas-sc}
begin{document}
makeatletter
renewcommandsection{@startsection{section}{1}{z@}%
{15pt @plus 3p@ @minus 3p@}%
{4p@}%
{%let@hangfromrelax
sectionfontraggedrighthst[13pt]}}
renewcommandsubsection{@startsection{subsection}{2}{z@}%
{10pt @plus 3p@ @minus 2p@}%
{.1p@}%
{%let@hangfromrelax
ssectionfontraggedright }}
renewcommandsubsubsection{@startsection{subsubsection}{3}{z@}%
{10pt @plus 1p@ @minus .3p@}%
{.1p@}%
{%let@hangfromrelax
sssectionfontraggedright}}
makeatother
section{A}
subsection{AA}
subsubsection{BB}
end{document}
answered Feb 15 at 16:16
Phelype OleinikPhelype Oleinik
23.5k54586
add a comment |
1
Yes, definitely a bug :)
The definition of section, subsection, and subsubsection in cas-common.sty uses the same counter, section, for all three levels. (i.e.: @startsection{section}...). If you copy that definition and use the correct counters the output looks correct:
documentclass[a4paper,fleqn]{cas-sc}
begin{document}
makeatletter
renewcommandsection{@startsection{section}{1}{z@}%
{15pt @plus 3p@ @minus 3p@}%
{4p@}%
{%let@hangfromrelax
sectionfontraggedrighthst[13pt]}}
renewcommandsubsection{@startsection{subsection}{2}{z@}%
{10pt @plus 3p@ @minus 2p@}%
{.1p@}%
{%let@hangfromrelax
ssectionfontraggedright }}
renewcommandsubsubsection{@startsection{subsubsection}{3}{z@}%
{10pt @plus 1p@ @minus .3p@}%
{.1p@}%
{%let@hangfromrelax
sssectionfontraggedright}}
makeatother
section{A}
subsection{AA}
subsubsection{BB}
end{document}
answered Feb 15 at 16:16
Phelype OleinikPhelype Oleinik
23.5k54586
add a comment |
1
1
1
Yes, definitely a bug :)
The definition of section, subsection, and subsubsection in cas-common.sty uses the same counter, section, for all three levels. (i.e.: @startsection{section}...). If you copy that definition and use the correct counters the output looks correct:
documentclass[a4paper,fleqn]{cas-sc}
begin{document}
makeatletter
renewcommandsection{@startsection{section}{1}{z@}%
{15pt @plus 3p@ @minus 3p@}%
{4p@}%
{%let@hangfromrelax
sectionfontraggedrighthst[13pt]}}
renewcommandsubsection{@startsection{subsection}{2}{z@}%
{10pt @plus 3p@ @minus 2p@}%
{.1p@}%
{%let@hangfromrelax
ssectionfontraggedright }}
renewcommandsubsubsection{@startsection{subsubsection}{3}{z@}%
{10pt @plus 1p@ @minus .3p@}%
{.1p@}%
{%let@hangfromrelax
sssectionfontraggedright}}
makeatother
section{A}
subsection{AA}
subsubsection{BB}
end{document}
answered Feb 15 at 16:16
Phelype OleinikPhelype Oleinik
23.5k54586
Yes, definitely a bug :)
The definition of section, subsection, and subsubsection in cas-common.sty uses the same counter, section, for all three levels. (i.e.: @startsection{section}...). If you copy that definition and use the correct counters the output looks correct:
documentclass[a4paper,fleqn]{cas-sc}
begin{document}
makeatletter
renewcommandsection{@startsection{section}{1}{z@}%
{15pt @plus 3p@ @minus 3p@}%
{4p@}%
{%let@hangfromrelax
sectionfontraggedrighthst[13pt]}}
renewcommandsubsection{@startsection{subsection}{2}{z@}%
{10pt @plus 3p@ @minus 2p@}%
{.1p@}%
{%let@hangfromrelax
ssectionfontraggedright }}
renewcommandsubsubsection{@startsection{subsubsection}{3}{z@}%
{10pt @plus 1p@ @minus .3p@}%
{.1p@}%
{%let@hangfromrelax
sssectionfontraggedright}}
makeatother
section{A}
subsection{AA}
subsubsection{BB}
end{document}
answered Feb 15 at 16:16
Phelype OleinikPhelype Oleinik
23.5k54586
answered Feb 15 at 16:16
Phelype OleinikPhelype Oleinik
23.5k54586
answered Feb 15 at 16:16
Phelype OleinikPhelype Oleinik
23.5k54586
answered Feb 15 at 16:16
Phelype OleinikPhelype Oleinik
23.5k54586
23.5k54586
add a comment |
add a comment |
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
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%2f475049%2fsubsection-command-not-working-in-elsevier-latex-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
@campa sorry, I could not understand your response. What is correct?
– Noman Bashir
Feb 15 at 16:01
@campa I just googled it (after commenting) and found it. Would you look at that, Elsevier switched to
expl3:). Well, then I think this is the expected behaviour...– Phelype Oleinik
Feb 15 at 16:01
campa replied to a comment I deleted, so it looked out of context.
– Phelype Oleinik
Feb 15 at 16:02
Okay, what is the final situation now?
– Noman Bashir
Feb 15 at 16:02
Your example is minimal and there is nothing wrong with it, so it's not your fault. I think you'd need to contact the Elsevier support and ask it there. There are two possibilities: 1) This is a design choice and you have to live with it. 2) It's a bug and they need to fix it (looks more like it). Either way, only they know the answer, unfortunately.
– Phelype Oleinik
Feb 15 at 16:07