ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Fabian Doerk" <fabian.doerk@planless.org>
Subject: document structure facility
Date: Mon, 26 May 2003 21:49:52 +0200 (CEST)	[thread overview]
Message-ID: <55146.141.28.224.2.1053978592.squirrel@idoru.planless.org> (raw)

Hey all,

i've a question regarding the context document structuring facility.
Maybe you can show me the right direction or show me what i made wrong.

I'am currently working on a semester project, whose goal it is to
build a CVS/ConTeXt Server accessible via Zope webapplications (an
selfmade documentation management system). Our approach is to split
the per semster documentation in products and the texts in
components. The whole documentation is integrated in a project. Via
webfrontend the user will be able to generate either the whole
documentation of all semesters (project, including all products) or
just one product.

We've created a hierarchical directory structure like the following
excerpt:

    CVSROOT/
        ReaktorDocs/
            Complete/
                Makefile
                ReaktorDocs.tex                 (projectfile)
                path.tex                   (included by ReactorDocs.tex)
                products.tex               (included by ReactorDocs.tex)
            Semester01/
                Documentation/
                    Makefile
                    Semester01.tex              (product file)
                    figures/
                        ...
                    text/
                        Makefile
                        semester01_txt001.tex   (component file)
                        semester01_txt002.tex   (component file)
                Protocols/
                    ...
            Semester02/
                ...
            Semester03/
                ...
            Styles/
                p-eng-doc-default.tex           (environment file)
                p-eng-prot-default.tex          (environment file)
                ...

We've got it working in so far that the user can checkout one modul
and gets the Semester directory and the styles directory (of course
an cvs issue). The compilation of either one product or the whole
project works too, via help of \usepath and tex conditions in every
product file, which detects whether the front/back -matters should be
omitted (for project compilation) or beeing kept (for product
compilation).

The only thing i can't figure out, is why the counter for \part and
\chapter (probably all sectioning commands used in the products)
resets per product. Is there any solution for that problem or a
workaround to display an continuous \placecontent in the project scope?


thanks in advance,
Fabian Doerk

                 reply	other threads:[~2003-05-26 19:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=55146.141.28.224.2.1053978592.squirrel@idoru.planless.org \
    --to=fabian.doerk@planless.org \
    --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).