From: Peter Davis <pfd@pfdstudio.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Separate layout and content XML files?
Date: Fri, 12 Nov 2010 08:17:15 -0500 [thread overview]
Message-ID: <AANLkTimR8phRS5dyMMEdhRgRandyzgW=VZ3Fyu+ofNYV@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim-VsapMxY+sVDthgNHXboz=NbPnWAroZ8wHzbt@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 609 bytes --]
On Fri, Nov 12, 2010 at 7:55 AM, Martin Schröder <martin@oneiros.de> wrote:
> 2010/11/12 Peter Davis <pfd@pfdstudio.com>:
> > Is that clear?
>
> It's called database publishing. :-)
>
Exactly. (Or sometimes variable data printing ... VDP.)
I guess the "layout" XML file would basically be used to construct a macro
that draws the page, and the "content" XML would basically invoke that macro
with different arguments for each recipient.
Does that seem like the most effective way to do this? Any examples of
anything like this, or of using an XML to define a macro?
Thank you.
-pd
[-- Attachment #1.2: Type: text/html, Size: 1034 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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:[~2010-11-12 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 4:30 Peter Davis
2010-11-12 4:34 ` Aditya Mahajan
2010-11-12 12:51 ` Peter Davis
2010-11-12 12:55 ` Martin Schröder
2010-11-12 13:17 ` Peter Davis [this message]
2010-11-12 13:39 ` Hans van der Meer
2010-11-12 13:47 ` Peter Davis
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='AANLkTimR8phRS5dyMMEdhRgRandyzgW=VZ3Fyu+ofNYV@mail.gmail.com' \
--to=pfd@pfdstudio.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).