From: ecashin@coe.uga.edu (Ed L. Cashin)
Cc: ntg-context@ntg.nl
Subject: Re: AW: print user text in fields
Date: 11 Nov 1999 10:10:15 -0500 [thread overview]
Message-ID: <m3ogd1hxns.fsf@kali.coe.uga.edu> (raw)
In-Reply-To: <0F3313EC125AD311981100105AB3A75D107ADA@N0795.mdf.fvbb.de>
Haseloff, Lutz <Lutz.Haseloff@mdf.brandenburg.de> writes:
> > Hi. I'm now (re)reading the uptodate-1 document. I notice that when
> > I type some text into the text fields and then print, the text I
> > entered does not show up in the printed version. Is that a Acrobat
> > Reader thing or a ConTeXt thing?
>
> You have to make the fields printable:
> \setupfields [][][][option=printable]
>
> > There are some departments on campus who use HTML forms on the web as
> > static forms. They enter text into the HTML fields and then instead
> > of submitting the form, they just print it. It's not a very reliable
> > way to do things, but they do it. Could the same be done in
> > ConTeXt-generated pdf documents?
>
> YES YOU CAN, i work for several weeks to build such forms
> and i can give you some examples for ConTeXt in source form.
This is great news, and my little test worked just now. I realize
now, upon looking more closely, that there is a lot to learn about
form fields in context.
I looked for "stelveldenin" and "definieerveld" in the Dutch manual,
but I suppose that these features haven't made it into the manual yet,
since I didn't see them there.
Is uptodate number one the only place to read about fields or am I
forgetting/missing another source of documentation?
--
--Ed Cashin PGP public key:
ecashin@coe.uga.edu http://www.coe.uga.edu/~ecashin/pgp/
next prev parent reply other threads:[~1999-11-11 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-11 6:19 Haseloff, Lutz
1999-11-11 15:10 ` Ed L. Cashin [this message]
1999-11-11 18:09 Berend de Boer
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=m3ogd1hxns.fsf@kali.coe.uga.edu \
--to=ecashin@coe.uga.edu \
--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).