On 10/07/2009 11:22 AM, kmc wrote:
Thanks Lars for the explanation, the font get installed and your words
also inspired me to get the oldstyle figures out in dtpj. Except that
the oldstyle figures are named "one/two/three.textoldstyle" in order
to be distinguished from "one/two/three.taboldstyle" etc. So what I
did is edit t1cj.etx, change \setcommand\digit#1{#1oldstyle} to
\setcommand\digit#1{#1.textoldstyle} and save it under another
encoding file, etc.
2009/10/7 Pierre MacKay <[email protected]
<mailto:[email protected]>>
.., it is a good idea to try the result out on the latest Adobe
Reader. You may find that your work simply results in an unusable
PDF unless you subscribe to Adobe. com. For the moment, I have to
do so, but that still does not answer the question of the loss of
archival PDFs.
Pierre MacKay
I didn't seem to come across the problem using Acrobat Pro, and
Acrobat Reader 9 under Linux. To my experience, PDFs generated by
pdfLaTeX are highly compatible.
I've uploaded a test file on Rapidshare proofing the DinText font
that, you can see if your Reader can get it correctly displayed.
http://rapidshare.com/files/289938119/t1fonttest.pdf.html
--
kmc
Acrobat Pro is what the Adobe.com site uses, so I am sure it works
fine. I would like to avoid it, and to continue the use of
Ghostscript. There is where the problem lies. There, and with the loss
of PDF archives that can still be displayed on Reader 6 and 7, but not
on 8 and 9.
I suppose that Acrobat Pro gives you the option of writing XPDF/3, but
it sure doesn't offer it on the Adobe.com site. Does it give you the
ability to set Trimbox, Bleedbox and Mediabox to different values? That
seems to be available only with the << >> setdistillerparams convention,
and I find nothing in PDFTeX that recognizes the need for this or that
offers a way to introduce distillerparams. This has become a necessity
with up-to-date printing houses, which no longer pay attention to
visible crop marks (in fact, they deplore them).
Pierre MacKay
