From: Matthew Baker <mbaker@zeus.gmd.de>
Cc: Context List <ntg-context@ntg.nl>
Subject: Re: upside-down form elements?
Date: Wed, 2 Jun 1999 16:29:45 +0200 [thread overview]
Message-ID: <Pine.SGI.4.04.9906021619270.186400-100000@sono> (raw)
In-Reply-To: <375538BD.BE642BD3@wxs.nl>
On Wed, 2 Jun 1999, Hans Hagen wrote:
> I've attached a file, and I want to make sure field 2 and 3 print ok
> everywhere, so whoever want to test on whatever platform ...
Tested on SGI Acroread 4.0 beta and Linux Acroread 3.02 and worked on
both. I assume box 1 is supposed to be incorrect? I can test on Win95
when I get home tonight, but I suppose there is no shortage on win95
testers :)
Actually, there was a problem with Acroread 3.0x Linux that I didn't
mention because other forms I have, which were not produced by Context,
resulted in the same problem. This problem was that the form contents did
not display in PostScript file: they make it into the Postscript file but
for some reason are invisible. Boxes 2 and 3 in test.pdf now appear
correct (so Context is doing better than the alternative packages in this
respect!)
> I'll send the 2 line patch and the test.tex file to thanh and matthew
> for further testing. (Matthew: you should change the macros in the
> spec-tpd.tex driver (run time loaded, so no fmt generation needed).
Which macros would that be?
--
Dr. Matthew Baker matthew.baker@gmd.de
GMD - FIT.MMK http://fit.gmd.de/hci/pages/matthew.baker.html
next prev parent reply other threads:[~1999-06-02 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-01 13:18 Matthew Baker
1999-06-01 14:43 ` Hans Hagen
1999-06-02 9:12 ` Matthew Baker
1999-06-02 13:59 ` Hans Hagen
1999-06-02 14:29 ` Matthew Baker [this message]
1999-06-02 15:10 ` Hans Hagen
1999-06-01 15:44 ` Taco Hoekwater
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=Pine.SGI.4.04.9906021619270.186400-100000@sono \
--to=mbaker@zeus.gmd.de \
--cc=Matthew.Baker@gmd.de \
--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).