Hi Hans,

 

Here is my problem,

 

When I compile my TeX source using “LaTeX” button in WinEdt, I can go ahead and create a “ps” code out of it using “dvi to ps” in WinEdt. Now this “ps” code can be compiled and converted to PDF using any acrobat distiller.

 

My issue is, what if I do not want to do this and directly want to create a PDF file using “PDFLaTeX” in WinEdt. I know I can do that, but when I submit that PDF document online to the publisher, it returns with an error saying that the PDF document submitted is not = or > version 4.0 of acrobat standards, also there is an error of embedded fonts. Now when I checked online there was this reference to change the value to true in the “updmap.cfg” to embed the fonts in the PDF document (I have a question there too, just changing the values of these three variables

 

dvipsDownloadBase35 true
pdftexDownloadBase14 true
dvipdfmDownloadBase14 true

 

will change the settings to embed fonts in the document (ps, or pdf depending on what method are we using)? Of course I have to call “updmap” once again to re-map everything before I start again. Now my question is that will this take care of all fonts or I have to specifically mention all the fonts I want to embed?)

 

Now according to you when I change the minor version in “pdftex.cfg” config file, it actually directs the PDFTeX engine to make necessary changes to reach to that version standard. Also PDFLaTeX  is bult upon PDFTeX so making this change will also insure that when I use PDFLaTeX , I am using the changed version standards for my document, right?

 

I think I am really confused at this point, or I don’t have the big picture yet. And thanks again for helping out.

 

Deepak

 


"Hans F. Nordhaug" <Hans.F.Nordhaug@hiMolde.no> wrote:
* Deepak Jha [2005-08-29]:
>
> Sorry Hans for the bold fonts, it seems my habit of posting numerous
> messages on various boards on net hasn't changed a lot. I got your
> idea, but isn't it like cheating, I mean keeping the same content,
> I will be changing only the name. Correct me if this is not true. I
> have following concerns:
>
> 1. Changing the version this way (the way you suggest), will not
> change anything other than the document property tag for pdf
> version, right?

Wrong. If you ask for pdf_minorversion 5 you get a document that
follows the specs for the PDF format 1.5. Since the specs for PDF are
backward compatible, you may or may see many changes in the PDF
depending on what features you use.

> 2. I want to somehow bring PDF version 4 or higher (I am adamant on
> this because of font embedding problems, and certain IEEE/other
> publication guidelines, which suggest that the final PDF should be
> from a version 4.0 or higher).

You (and your publisher) must get the terminology correct. Adobe
Acrobat 4.0 (the software which is from 1999) produces PDF files
using (the old) 1.3 PDF specs. pdftex by default produces documents
using the 1.4 PDF specs (which corresponds to Adobe Acrobat 5.0).

> 3. Final question, the PDFTeX doesn't use any acrobat engine
> embedded in itself, if so then cant the PDFTeX be upgraded to the
> level of version 4.0 or greater acrobat distiller/engine.

As I said above - pdftex is already way beyond Adobe Acrobat 4.0.

I think you should tell us the real problem...

Hans

> "Hans F. Nordhaug" wrote:
> (Please don't use all caps in the subject - it's like yelling out loud.)
>
> * Deepak Jha [2005-08-29]:
> > Hi all,
> >
> > I have a problem with the version of acrobat PDFTeX uses. The output
> > is done using an acrobat version lower than 4.0.
>
> pdfTeX isn't using Acrobat to produce pdf - it's doing everything
> itself. What you probably are thinking about is the version of PDF
> pdftex is producing. This you can controlchanging the value for
> pdf_minorversion in texmf\pdftex\config\pdftex.cfg or by adding
> "\pdfminorversion=N" (where N is 3, 4 or 5) to your tex files.
>
> Hans


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
MiKTeX-Users mailing list
MiKTeX-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/miktex-users

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com