save as pdf (font embedding)

SP 3.4 added an option during saveas t oenable embedding fonts.

I too use swisop1 font and use both cute pdf and the SW 'save as pdf'

- I have not encountered this - I have just checked and the swisop1 is embedded into the pdf file using both pdf creators. I send these out all the time as the SW pdf is a little faster at generating but creates all the sheets , while with cute pdf I can select which sheets to print. Had no complaints yet - but then I have a poor customer relations department and maybe they have given up complaining !! ;-)

I'm not sure what is going on with your set up.

running sw2006 sp0

Do you want me to email a pdf and sw file to you , for you to investigate?

TTFN

Jonathan.

Jonathan,

You are still on SP0.0 which uses BlueBeam for the PDF writer. MHill is using SP3.0 which has changed to using Adobe for the PDF writer. This is not an apples to apples comparison.

If in fact this is an "across the board" problem, you would more than likely see the same problem if you upgraded to SP3.0. However there are supposedly several PDF fixes in SP3.4, which I cannot verify (still on SP3.0 here).

That would explain it. I didn't realise the SW pdf was bluebeam - when the Bluebeam first came out as an addin - 2004 ? - I remember it was rubbish and realy screwed up my machine!!

Roll on SW2007 ;-)

TTFN

Jonathan

Dale Dunn wrote in news:Xns978CB4B31C73Ddaledunnatjamestoolc@65.24.7.27:

Thanks for the info. I hadn't looked at the release notes to see what was changing in all of the minor 3.x releases. I'll load 3.4 and give it a try.

I think the potential for SW to make dramatic improvements in the pdf export dept is much higher with adobe than with bluebeam. I never liked the way bluebeam handled things and have avoided it when possible. Putting a proper pdf export option on the save as list is a big help to me due to our workflow here.

MHill

As much as I have gripped about the new Adobe PDF add-in, I do agree that the potential for more functionality improvements is greater with Adobe. Whether we need it or not is dependent upon the user and their workplace practices. I personally needed no further functionality. BlueBeam always worked great for me.

It's just that so far, we have had to deal with all these problems with the Adobe add-in. I still don't believe that it's quite ready for prime time yet. And, I doubt that the Adobe add-in will EVER be as quick and easy to use as the BlueBeam counterpart for simply making general PDF's.

My $0.02 worth.

MHill wrote in news: snipped-for-privacy@news.supernews.com:

Response from my VAR is that this is NOT working correctly, an SPR has been issed, and a fix has been developed, coming in SP4, "sometime in April".

Certainly, this switch to Adobe was premature from a development standpoint. I think even basic testing could have identified these types of issues that are critical flaws in the program.

Given that the open source community has worked out PDF creation beautifully, I don't see why SW, when partnered with the developer of the standard, can't quite get it right.

MHill

you think they didn't know it wasn't ready?... ;o)