From: Robert L Knighten <RLK@knighten.org>
To: Categories list <categories@mta.ca>
Subject: re: Warning about Adobe 8
Date: Sun, 28 Oct 2007 17:13:39 -0700 [thread overview]
Message-ID: <E1ImdFu-0004Xe-6A@mailserv.mta.ca> (raw)
Michael Barr writes:
> Whatever you do, do not upgrade to Adobe reader 8. I found this on the
> texhax list.
>
> >>Has anyone else been clobbered by the discovery that Adobe Acrobat 8
> >>tacitly suppresses all ligature glyphs of the fi, fl, ff, ffi, and ffl
> >>sort and displays blanks in their place. They do this without warning,
> >>so that a file which displays perfectly well in Acrobat 7 is made
> >>unreadable in Acrobat 8.
> >>
>
> It turns out that files converted (from the ps file) by the distiller
> (which costs something like $500) do not have this problem. I guess Adobe
> is tired of free use of their format. At TAC, we still consider the dvi
> to be the official format.
>
> Michael
>
What is the context? I've been using Adobe Reader 8 on Windows since it first
came out and have never seen this, very definitely including pdf files created
by pdflatex on both Windows and Linux. As a quick check I just created a
number of pdf files in various ways on both Windows and Linux and viewed them
in both places using both Adobe Reader 7 and Adobe Reader 8 and was unable to
see any difference at all.
-- Bob
--
Robert L. Knighten
RLK@knighten.org
next reply other threads:[~2007-10-29 0:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 0:13 Robert L Knighten [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-30 9:10 Andrej Bauer
2007-10-30 7:58 Gaucher Philippe
2007-10-30 3:04 Peter Selinger
2007-10-29 12:35 Michael Barr
2007-10-29 12:20 Robert J. MacG. Dawson
2007-10-29 7:05 Michael Mislove
2007-10-29 0:26 Vaughan Pratt
2007-10-28 13:06 Michael Barr
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=E1ImdFu-0004Xe-6A@mailserv.mta.ca \
--to=rlk@knighten.org \
--cc=categories@mta.ca \
/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).