From: Pierre Weis <pierre.weis@inria.fr>
To: zilles@1969.ws (Karl Zilles)
Cc: martin_jambon@emailuser.net, caml-list@inria.fr
Subject: Re: [Caml-list] Printing text with holes
Date: Mon, 29 Sep 2003 23:47:45 +0200 (MET DST) [thread overview]
Message-ID: <200309292147.XAA30083@pauillac.inria.fr> (raw)
In-Reply-To: <3F7865E2.4090207@1969.ws> from Karl Zilles at "Sep 29, 103 10:03:30 am"
> Martin Jambon wrote:
> > Hello,
> >
> > I am curious to know what people use to print long text written in a
> > natural language, and containing many holes, like dynamically generated
> > web pages.
I just use htmlc, which is simple and efficient:
http://pauillac.inria.fr/htmlc/
It uses $identifiers as you suggested, + some Server Side Includes
expansions, + local environment definition facilities, + what you
would like to add to it in the future :)
Here is a brief excerpt of the Changes file:
1.20 (Documents environment variables expansion)
----
- Inside documents variables of the form $X, $(X), or ${X} are
considered to be bound in the Htmlc's global environment hash table
and expanded as their corresponding string associated value.
- New -e argument to load environment files that set up Htmlc's
global environment table. Environment files are list of lines
that contain a variable name and an associated string (following
Caml' lexical conventions).
- New server side directive: the line
<!--#include environment="filename"-->
in a document loads environment file ``filename'' and enriches the
global environment accordingly.
- New -s compilation flag to expand .shtml files into .html files.
1.10 (User's environment variables expansion)
----
- Throughout documents passed to htmlc, tags of the form <$X>
are considered to reference the variable X in the user's
gloabal environment: <$HOME> is thus replaced by the string
representation of the user's HOME directory.
(This expansion mechanism is disabled when including verbatim
files).
Hope this helps,
Pierre Weis
INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://pauillac.inria.fr/~weis/
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-09-29 21:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 13:16 Martin Jambon
2003-09-29 14:10 ` Christian Lindig
2003-09-29 16:25 ` Benjamin Geer
2003-09-29 16:39 ` Brian Hurt
2003-09-29 17:45 ` Jean-Marc EBER
2003-09-29 18:22 ` Brian Hurt
2003-09-29 20:48 ` Pierre Weis
2003-09-29 21:52 ` Richard Jones
2003-09-29 22:07 ` Fred Yankowski
2003-09-29 22:14 ` Daniel M. Albro
2003-09-29 22:19 ` Richard Jones
2003-09-29 22:23 ` Matthieu Sozeau
2003-09-30 3:56 ` Brian Hurt
2003-09-30 4:40 ` Brian Hurt
2003-09-30 6:11 ` David Brown
2003-09-29 18:57 ` Martin Jambon
2003-09-29 21:25 ` Pierre Weis
2003-09-30 12:52 ` skaller
2003-09-30 17:48 ` Martin Jambon
2003-09-29 18:16 ` Richard Jones
2003-09-29 17:00 ` Pierre Weis
2003-09-29 17:03 ` Karl Zilles
2003-09-29 21:47 ` Pierre Weis [this message]
2003-09-30 7:20 ` Jean-Christophe Filliatre
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=200309292147.XAA30083@pauillac.inria.fr \
--to=pierre.weis@inria.fr \
--cc=caml-list@inria.fr \
--cc=martin_jambon@emailuser.net \
--cc=zilles@1969.ws \
/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