Sort subsections alphabetically
We need to make a paper that describes a list of interfaces. The assignment however says we need to sort the interfaces alphabetically. Because this list is quite long (20+) I am looking for a way to sort the subsections (each subsection describes an interface) alphabetically. Without having to move code myself.
Is there a package that can handle this?
Here is a sample of the code:
newcommand{interfaceItem}[5]{
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
sectioning sorting
add a comment |
We need to make a paper that describes a list of interfaces. The assignment however says we need to sort the interfaces alphabetically. Because this list is quite long (20+) I am looking for a way to sort the subsections (each subsection describes an interface) alphabetically. Without having to move code myself.
Is there a package that can handle this?
Here is a sample of the code:
newcommand{interfaceItem}[5]{
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
sectioning sorting
1
Would it be possible to have each subsection in a separate file, and then have a program compile the whole document together before leaving it to TeX?
– Henrik Hansen
Apr 21 '12 at 11:56
This sheds some light on your options: tex.stackexchange.com/questions/51967/…
– Henrik Hansen
Apr 21 '12 at 11:57
Well the subsection itself is written by a macro. I don't think it's that difficult to write the code to a file instead.
– Willem Van Onsem
Apr 21 '12 at 11:58
Can you give an indication how your paper is organised? If the whole text of the subsections has to be moved, this is certainly impossible from within TeX if the subsections are not "contained" in some sort of structure.
– Stephan Lehmke
Apr 22 '12 at 7:18
I have added a small description.
– Willem Van Onsem
Apr 23 '12 at 7:38
add a comment |
We need to make a paper that describes a list of interfaces. The assignment however says we need to sort the interfaces alphabetically. Because this list is quite long (20+) I am looking for a way to sort the subsections (each subsection describes an interface) alphabetically. Without having to move code myself.
Is there a package that can handle this?
Here is a sample of the code:
newcommand{interfaceItem}[5]{
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
sectioning sorting
We need to make a paper that describes a list of interfaces. The assignment however says we need to sort the interfaces alphabetically. Because this list is quite long (20+) I am looking for a way to sort the subsections (each subsection describes an interface) alphabetically. Without having to move code myself.
Is there a package that can handle this?
Here is a sample of the code:
newcommand{interfaceItem}[5]{
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
sectioning sorting
sectioning sorting
edited Feb 1 '14 at 20:07
asked Apr 21 '12 at 11:50
Willem Van Onsem
2,12312347
2,12312347
1
Would it be possible to have each subsection in a separate file, and then have a program compile the whole document together before leaving it to TeX?
– Henrik Hansen
Apr 21 '12 at 11:56
This sheds some light on your options: tex.stackexchange.com/questions/51967/…
– Henrik Hansen
Apr 21 '12 at 11:57
Well the subsection itself is written by a macro. I don't think it's that difficult to write the code to a file instead.
– Willem Van Onsem
Apr 21 '12 at 11:58
Can you give an indication how your paper is organised? If the whole text of the subsections has to be moved, this is certainly impossible from within TeX if the subsections are not "contained" in some sort of structure.
– Stephan Lehmke
Apr 22 '12 at 7:18
I have added a small description.
– Willem Van Onsem
Apr 23 '12 at 7:38
add a comment |
1
Would it be possible to have each subsection in a separate file, and then have a program compile the whole document together before leaving it to TeX?
– Henrik Hansen
Apr 21 '12 at 11:56
This sheds some light on your options: tex.stackexchange.com/questions/51967/…
– Henrik Hansen
Apr 21 '12 at 11:57
Well the subsection itself is written by a macro. I don't think it's that difficult to write the code to a file instead.
– Willem Van Onsem
Apr 21 '12 at 11:58
Can you give an indication how your paper is organised? If the whole text of the subsections has to be moved, this is certainly impossible from within TeX if the subsections are not "contained" in some sort of structure.
– Stephan Lehmke
Apr 22 '12 at 7:18
I have added a small description.
– Willem Van Onsem
Apr 23 '12 at 7:38
1
1
Would it be possible to have each subsection in a separate file, and then have a program compile the whole document together before leaving it to TeX?
– Henrik Hansen
Apr 21 '12 at 11:56
Would it be possible to have each subsection in a separate file, and then have a program compile the whole document together before leaving it to TeX?
– Henrik Hansen
Apr 21 '12 at 11:56
This sheds some light on your options: tex.stackexchange.com/questions/51967/…
– Henrik Hansen
Apr 21 '12 at 11:57
This sheds some light on your options: tex.stackexchange.com/questions/51967/…
– Henrik Hansen
Apr 21 '12 at 11:57
Well the subsection itself is written by a macro. I don't think it's that difficult to write the code to a file instead.
– Willem Van Onsem
Apr 21 '12 at 11:58
Well the subsection itself is written by a macro. I don't think it's that difficult to write the code to a file instead.
– Willem Van Onsem
Apr 21 '12 at 11:58
Can you give an indication how your paper is organised? If the whole text of the subsections has to be moved, this is certainly impossible from within TeX if the subsections are not "contained" in some sort of structure.
– Stephan Lehmke
Apr 22 '12 at 7:18
Can you give an indication how your paper is organised? If the whole text of the subsections has to be moved, this is certainly impossible from within TeX if the subsections are not "contained" in some sort of structure.
– Stephan Lehmke
Apr 22 '12 at 7:18
I have added a small description.
– Willem Van Onsem
Apr 23 '12 at 7:38
I have added a small description.
– Willem Van Onsem
Apr 23 '12 at 7:38
add a comment |
2 Answers
2
active
oldest
votes
Here's an implementation:
documentclass{article}
usepackage{xparse}
ExplSyntaxOn
NewDocumentCommand{interfaceItem}{mmmmm}
{
seq_put_right:Nn l_commusoft_interfaces_seq {#1}
cs_new:cpn { commusoft_interface_#1: } {
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
}
NewDocumentCommand{printInterfaces}{ }
{
seq_sort:Nn l_commusoft_interfaces_seq
{
string_compare:nnnTF {##1} {>} {##2} {sort_return_swapped:} {sort_return_same:}
}
seq_map_inline:Nn l_commusoft_interfaces_seq { use:c { commusoft_interface_##1: } }
}
seq_new:N l_commusoft_interfaces_seq
prg_new_conditional:Npnn string_compare:nnn #1 #2 #3 {TF}
{
if_int_compare:w pdftex_strcmp:D {#1}{#3} #2 c_zero
prg_return_true:
else:
prg_return_false:
fi
}
ExplSyntaxOff
interfaceItem{A}{A1}{A2}{A3}{A4}
interfaceItem{C}{C1}{C2}{C3}{C4}
interfaceItem{B}{B1}{B2}{B3}{B4}
begin{document}
printInterfaces
end{document}
However, a simpler strategy can be easier:
makeatletter
newcommand{interfaceItem}[5]{
@namedef{interface@detokenize{#1}}{%
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
}
newcommand{printInterface}[1]{%
@nameuse{interface@detokenize{#1}}%
}
makeatother
You define your interfaces as before, in the preamble,
interfaceItem{A}{A1}{A2}{A3}{A4}
interfaceItem{C}{C1}{C2}{C3}{C4}
interfaceItem{B}{B1}{B2}{B3}{B4}
and then say
printinterface{A}
printinterface{B}
printinterface{C}
Sorting a list of short commands is easier than sorting big chunks of code.
add a comment |
TeX is Turing complete language so I am sure the problem can be "easily" solved. However, this is best done (at least on Unix) with the standard Unix tools. Create a directory interfaces in which you would create a separate .tex file for the description of each interface. Something like
z-interface.tex
a-interface.tex
q-interface.tex
b-interface.tex
Now do something like
ls interfaces > interface-names.txt
which will create interface-names.txt file with interfaces sorted in alphabetical order. Using awk you can easily add input
TeX command in front of each file name. Like
awk '{print "\input",$1}' interface-names.txt > interface-names.tex
Now just put the following line
input interface-names.tex
into your main .tex file and you will have all sub sections in proper order as long as main .tex file and interface .tex files are in the same directory.
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%2f52801%2fsort-subsections-alphabetically%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Here's an implementation:
documentclass{article}
usepackage{xparse}
ExplSyntaxOn
NewDocumentCommand{interfaceItem}{mmmmm}
{
seq_put_right:Nn l_commusoft_interfaces_seq {#1}
cs_new:cpn { commusoft_interface_#1: } {
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
}
NewDocumentCommand{printInterfaces}{ }
{
seq_sort:Nn l_commusoft_interfaces_seq
{
string_compare:nnnTF {##1} {>} {##2} {sort_return_swapped:} {sort_return_same:}
}
seq_map_inline:Nn l_commusoft_interfaces_seq { use:c { commusoft_interface_##1: } }
}
seq_new:N l_commusoft_interfaces_seq
prg_new_conditional:Npnn string_compare:nnn #1 #2 #3 {TF}
{
if_int_compare:w pdftex_strcmp:D {#1}{#3} #2 c_zero
prg_return_true:
else:
prg_return_false:
fi
}
ExplSyntaxOff
interfaceItem{A}{A1}{A2}{A3}{A4}
interfaceItem{C}{C1}{C2}{C3}{C4}
interfaceItem{B}{B1}{B2}{B3}{B4}
begin{document}
printInterfaces
end{document}
However, a simpler strategy can be easier:
makeatletter
newcommand{interfaceItem}[5]{
@namedef{interface@detokenize{#1}}{%
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
}
newcommand{printInterface}[1]{%
@nameuse{interface@detokenize{#1}}%
}
makeatother
You define your interfaces as before, in the preamble,
interfaceItem{A}{A1}{A2}{A3}{A4}
interfaceItem{C}{C1}{C2}{C3}{C4}
interfaceItem{B}{B1}{B2}{B3}{B4}
and then say
printinterface{A}
printinterface{B}
printinterface{C}
Sorting a list of short commands is easier than sorting big chunks of code.
add a comment |
Here's an implementation:
documentclass{article}
usepackage{xparse}
ExplSyntaxOn
NewDocumentCommand{interfaceItem}{mmmmm}
{
seq_put_right:Nn l_commusoft_interfaces_seq {#1}
cs_new:cpn { commusoft_interface_#1: } {
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
}
NewDocumentCommand{printInterfaces}{ }
{
seq_sort:Nn l_commusoft_interfaces_seq
{
string_compare:nnnTF {##1} {>} {##2} {sort_return_swapped:} {sort_return_same:}
}
seq_map_inline:Nn l_commusoft_interfaces_seq { use:c { commusoft_interface_##1: } }
}
seq_new:N l_commusoft_interfaces_seq
prg_new_conditional:Npnn string_compare:nnn #1 #2 #3 {TF}
{
if_int_compare:w pdftex_strcmp:D {#1}{#3} #2 c_zero
prg_return_true:
else:
prg_return_false:
fi
}
ExplSyntaxOff
interfaceItem{A}{A1}{A2}{A3}{A4}
interfaceItem{C}{C1}{C2}{C3}{C4}
interfaceItem{B}{B1}{B2}{B3}{B4}
begin{document}
printInterfaces
end{document}
However, a simpler strategy can be easier:
makeatletter
newcommand{interfaceItem}[5]{
@namedef{interface@detokenize{#1}}{%
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
}
newcommand{printInterface}[1]{%
@nameuse{interface@detokenize{#1}}%
}
makeatother
You define your interfaces as before, in the preamble,
interfaceItem{A}{A1}{A2}{A3}{A4}
interfaceItem{C}{C1}{C2}{C3}{C4}
interfaceItem{B}{B1}{B2}{B3}{B4}
and then say
printinterface{A}
printinterface{B}
printinterface{C}
Sorting a list of short commands is easier than sorting big chunks of code.
add a comment |
Here's an implementation:
documentclass{article}
usepackage{xparse}
ExplSyntaxOn
NewDocumentCommand{interfaceItem}{mmmmm}
{
seq_put_right:Nn l_commusoft_interfaces_seq {#1}
cs_new:cpn { commusoft_interface_#1: } {
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
}
NewDocumentCommand{printInterfaces}{ }
{
seq_sort:Nn l_commusoft_interfaces_seq
{
string_compare:nnnTF {##1} {>} {##2} {sort_return_swapped:} {sort_return_same:}
}
seq_map_inline:Nn l_commusoft_interfaces_seq { use:c { commusoft_interface_##1: } }
}
seq_new:N l_commusoft_interfaces_seq
prg_new_conditional:Npnn string_compare:nnn #1 #2 #3 {TF}
{
if_int_compare:w pdftex_strcmp:D {#1}{#3} #2 c_zero
prg_return_true:
else:
prg_return_false:
fi
}
ExplSyntaxOff
interfaceItem{A}{A1}{A2}{A3}{A4}
interfaceItem{C}{C1}{C2}{C3}{C4}
interfaceItem{B}{B1}{B2}{B3}{B4}
begin{document}
printInterfaces
end{document}
However, a simpler strategy can be easier:
makeatletter
newcommand{interfaceItem}[5]{
@namedef{interface@detokenize{#1}}{%
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
}
newcommand{printInterface}[1]{%
@nameuse{interface@detokenize{#1}}%
}
makeatother
You define your interfaces as before, in the preamble,
interfaceItem{A}{A1}{A2}{A3}{A4}
interfaceItem{C}{C1}{C2}{C3}{C4}
interfaceItem{B}{B1}{B2}{B3}{B4}
and then say
printinterface{A}
printinterface{B}
printinterface{C}
Sorting a list of short commands is easier than sorting big chunks of code.
Here's an implementation:
documentclass{article}
usepackage{xparse}
ExplSyntaxOn
NewDocumentCommand{interfaceItem}{mmmmm}
{
seq_put_right:Nn l_commusoft_interfaces_seq {#1}
cs_new:cpn { commusoft_interface_#1: } {
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
}
NewDocumentCommand{printInterfaces}{ }
{
seq_sort:Nn l_commusoft_interfaces_seq
{
string_compare:nnnTF {##1} {>} {##2} {sort_return_swapped:} {sort_return_same:}
}
seq_map_inline:Nn l_commusoft_interfaces_seq { use:c { commusoft_interface_##1: } }
}
seq_new:N l_commusoft_interfaces_seq
prg_new_conditional:Npnn string_compare:nnn #1 #2 #3 {TF}
{
if_int_compare:w pdftex_strcmp:D {#1}{#3} #2 c_zero
prg_return_true:
else:
prg_return_false:
fi
}
ExplSyntaxOff
interfaceItem{A}{A1}{A2}{A3}{A4}
interfaceItem{C}{C1}{C2}{C3}{C4}
interfaceItem{B}{B1}{B2}{B3}{B4}
begin{document}
printInterfaces
end{document}
However, a simpler strategy can be easier:
makeatletter
newcommand{interfaceItem}[5]{
@namedef{interface@detokenize{#1}}{%
subsection{#1}label{interfaceItem:#1}
paragraph{Paragraph 1}#2
paragraph{Paragraph 2}#3
paragraph{Paragraph 3}#4
paragraph{Paragraph 4}#5
}
}
newcommand{printInterface}[1]{%
@nameuse{interface@detokenize{#1}}%
}
makeatother
You define your interfaces as before, in the preamble,
interfaceItem{A}{A1}{A2}{A3}{A4}
interfaceItem{C}{C1}{C2}{C3}{C4}
interfaceItem{B}{B1}{B2}{B3}{B4}
and then say
printinterface{A}
printinterface{B}
printinterface{C}
Sorting a list of short commands is easier than sorting big chunks of code.
edited 30 mins ago
answered Apr 23 '12 at 8:25
egreg
708k8618813163
708k8618813163
add a comment |
add a comment |
TeX is Turing complete language so I am sure the problem can be "easily" solved. However, this is best done (at least on Unix) with the standard Unix tools. Create a directory interfaces in which you would create a separate .tex file for the description of each interface. Something like
z-interface.tex
a-interface.tex
q-interface.tex
b-interface.tex
Now do something like
ls interfaces > interface-names.txt
which will create interface-names.txt file with interfaces sorted in alphabetical order. Using awk you can easily add input
TeX command in front of each file name. Like
awk '{print "\input",$1}' interface-names.txt > interface-names.tex
Now just put the following line
input interface-names.tex
into your main .tex file and you will have all sub sections in proper order as long as main .tex file and interface .tex files are in the same directory.
add a comment |
TeX is Turing complete language so I am sure the problem can be "easily" solved. However, this is best done (at least on Unix) with the standard Unix tools. Create a directory interfaces in which you would create a separate .tex file for the description of each interface. Something like
z-interface.tex
a-interface.tex
q-interface.tex
b-interface.tex
Now do something like
ls interfaces > interface-names.txt
which will create interface-names.txt file with interfaces sorted in alphabetical order. Using awk you can easily add input
TeX command in front of each file name. Like
awk '{print "\input",$1}' interface-names.txt > interface-names.tex
Now just put the following line
input interface-names.tex
into your main .tex file and you will have all sub sections in proper order as long as main .tex file and interface .tex files are in the same directory.
add a comment |
TeX is Turing complete language so I am sure the problem can be "easily" solved. However, this is best done (at least on Unix) with the standard Unix tools. Create a directory interfaces in which you would create a separate .tex file for the description of each interface. Something like
z-interface.tex
a-interface.tex
q-interface.tex
b-interface.tex
Now do something like
ls interfaces > interface-names.txt
which will create interface-names.txt file with interfaces sorted in alphabetical order. Using awk you can easily add input
TeX command in front of each file name. Like
awk '{print "\input",$1}' interface-names.txt > interface-names.tex
Now just put the following line
input interface-names.tex
into your main .tex file and you will have all sub sections in proper order as long as main .tex file and interface .tex files are in the same directory.
TeX is Turing complete language so I am sure the problem can be "easily" solved. However, this is best done (at least on Unix) with the standard Unix tools. Create a directory interfaces in which you would create a separate .tex file for the description of each interface. Something like
z-interface.tex
a-interface.tex
q-interface.tex
b-interface.tex
Now do something like
ls interfaces > interface-names.txt
which will create interface-names.txt file with interfaces sorted in alphabetical order. Using awk you can easily add input
TeX command in front of each file name. Like
awk '{print "\input",$1}' interface-names.txt > interface-names.tex
Now just put the following line
input interface-names.tex
into your main .tex file and you will have all sub sections in proper order as long as main .tex file and interface .tex files are in the same directory.
edited Apr 22 '12 at 4:06
answered Apr 22 '12 at 2:50
Predrag Punosevac
6,76714163
6,76714163
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f52801%2fsort-subsections-alphabetically%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
Would it be possible to have each subsection in a separate file, and then have a program compile the whole document together before leaving it to TeX?
– Henrik Hansen
Apr 21 '12 at 11:56
This sheds some light on your options: tex.stackexchange.com/questions/51967/…
– Henrik Hansen
Apr 21 '12 at 11:57
Well the subsection itself is written by a macro. I don't think it's that difficult to write the code to a file instead.
– Willem Van Onsem
Apr 21 '12 at 11:58
Can you give an indication how your paper is organised? If the whole text of the subsections has to be moved, this is certainly impossible from within TeX if the subsections are not "contained" in some sort of structure.
– Stephan Lehmke
Apr 22 '12 at 7:18
I have added a small description.
– Willem Van Onsem
Apr 23 '12 at 7:38