From: john Culleton <John@wexfordpress.com>
To: ntg-context@ntg.nl
Subject: Re: How to redefine \section temporaly?
Date: Sun, 1 Sep 2013 13:02:42 -0400 [thread overview]
Message-ID: <20130901130242.295656fc@localb.wexfordpress.net> (raw)
In-Reply-To: <3738642.m1qO42jPmq@nereid>
On Sat, 31 Aug 2013 23:10:07 +0200
Romain Diss <romain.diss@yahoo.fr> wrote:
> Hi all,
>
> I wrote some articles with context and they contain (of course)
> sections. Now I have to include all these articles in a book but each
> article should become a section of the book. So I wonder if there is
> a way to convert the \section command of the article files into
> \subsection in the book.
>
> Minimal not working (but supposed to explain my problem) example:
>
> %%% article.tex
> \startsection[title=A first point]
> ... \stopsection
> \startsection[title=A second point]
> ... \stopsection
>
> %%% book.tex
> % command to make the \section of the input articles become
> \subsection % commands
> \startsection[title=My first article]
> \input article
> \stopsection
>
> %%% end
>
>
> I know I can change the \section commands of the article.tex into
> \ArticleSection and switch with
> \definehead[ArticleSection][section]
> \definehead[ArticleSection][subsection]
> depending of the context, but it would be better (for me) to not
> modify the article.tex files.
>
> Any ideas?
>
> Thank in advance.
>
If faced with this problem I would import the tex file into gvim and do
a mass change with one statement like:
:% s/\\section/\\subsection/
Then I would save the tex file under a different name.
If there are already subsections I would convert them to subsubsections
first, then convert the sections to subsections. Eqch step is just a
singl command in gvim.
--
John Culleton
Wexford Press
Free list of books for self-publishers:
http://wexfordpress.net/shortlist.html
PDF e-book: "Create Book Covers with Scribus"
available at http://www.booklocker.com/books/4055.html
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-09-01 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 21:10 Romain Diss
2013-08-31 21:55 ` Hans Hagen
2013-09-01 18:46 ` Romain Diss
2013-09-01 17:02 ` john Culleton [this message]
2013-09-04 10:49 ` Romain Diss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130901130242.295656fc@localb.wexfordpress.net \
--to=john@wexfordpress.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).