PDF Add-in colors changed to black using Publisher 2007

[Postdead]

I have Publisher 2007 which shows it to be Beta2 though it came pre-installed
on a recently purchased PC. Help shows that it is SP1 MSO (12.0.6213.1000)

I installed theMicrosoft Office PDF/XML add-in which works well apart from
where text is coloured. Where is is the case, it is converted to black in the
resulting PDF.

I have tried High Quality and OCmmercial printing setting and checked
advanced options but can't see any setting which may be causing this.

Design Checker flags the coloured text as being RGB so I converted it to
CMYK but is still gets changed to Black when Publish to PDF (or Save as PDF)
are used.

(I tried to Apply to the Beta feedback site to report this
bughttps://connect.microsoft.com/feedback/default.aspx?SiteID=227
but whilst there were Apply buttons for other software these now seme to
have been removed for this product even though there are still recent
feedback posts being recorded.)

PS: Adobe Acrobat Standard is also installed and preserves the colour of the
text but I would prefer to use the PDF add-in becuase it seems more relliable
when rendering non-standard fonts.

 

[Mary Sauer]

What printer do you have as a default while you are creating your publication?
Do you have the same problem if you setup Adobe PDF as the printer first, create
and then save as a PDF?

 

[Postdead]

Dear Mary

Thanks for this tip - You are right, changing my Default Printer in Printers
& Faxes to Adobe PDF or Any Colour capable printer results in the PDF created
using the MS Add-in being in colour (color!).

I don't know what you think constitutes a 'bug' but this certainly does in
my book! Changing to a colour printer driver as default each time I want to
use this feature is simply a no-no which is a pity becuase it seems very
stable in every other regard.

 

[Mary Sauer]

There are many bugs in Publisher 2007. The Microsoft PDF add-in isn't one of
them. I use it more often than Acrobat.

At least you found a workaround. There are bugs in Publisher's page setup that
I've never found suitable workarounds.

Thanks for your follow up post, I appreciate it.