Is Publisher the right tool for my book?

L

Lee Blevins

Brian Kvalheim said:
|| Nowhere on that page is there clear direction or acknowledgement that
|| there is a bug and what the fix is.

I guess I shouldn't assume that most people are smart enough to click on
Check for Updates.

I guess you're just a moron Brian.

I have been involved in computing since the inception of the personal
computer.

I have been involved in support as a profession for many years.

I have never had difficulty in presenting clear and concise answers to
questions.

Whenever questioned about a particular software download I don't suggest
somejust go to Sourceforge and start looking. You do apparently. It just
seems a common courtesy to supply the direct link.

You seem to avoid doing that.

My suspicion is that is by design.

What was so hard about actually pasting the url to the link?

Secondly, this is a link to Office 2003.
I didn't purchase Office 2003 and don't intend to.
Is there a problem with MS offereing the patch clearly to people who
only purchased Publisher?

They do sell Publisher as a standalone package. I bought it.

The description of the problem is consistent with Microsoft's denial of
bugs. Saying the problem happens with 500 meg files or larger.

Total bull crap.

The CMYK composite printing with Publisher was fucked with just about
any document. It rarely worked.

The performance of the product at my shop showed it couldn't have been
very well tested before release.

Perhaps the testing was done by people like you.

That would explain a lot.

But my new policy on Publisher seems to be working.

It goes like this.

You [the customer with the Publisher doc] pays for every minute of time
I interact with your document even if no output is created. It is not my
fault Microsoft made crappy software and I cannot lose money playing
with it. If you [the customer] does not like this, call Microsoft and
complain. But you have to pay me. I don't work for free.

On the other hand I can supply your contact info and they can send them
all to you. Please supply address, phone, etc.

The last publisher job I did I invited the printer to come sit at the PC
and show us how we were doing something wrong.

He was amazed. Every other program on the PC (XP) was working perfectly
and Publisher wouldn't create output. I explained to him that I would
have to charge for the time I had spent. He left and he doesn't send me
publisher files anymore.

It must be a good decision because my sales are up and my profitability
is up.

Feel free to use this as an example of how a company can improve it's
bottom lime by not taking in crappy low end bottom feeding shit.

To make my point very clear let me state it this way:

Publisher = Low end bottom feeding shit.

If that's the market you find yourself in and supporting, I suggest you
re-evaluate your business model.

I have.

I no longer take in Publisher without having a customer sign a release
that they will pay for every minute of time we spend even if there is no
output.

I suggest the National Association of Printers and Lithographers take my
release form and distribute it.
 
L

Lee Blevins

Brian Kvalheim said:
Lee Blevins wrote:
|| Doesn't matter to me.

Excellent. Makes your post moot.

No, the post was actually:

Sounds like MS bull - when somebody points out a problem you pass it off
as the program is not for pros but when somebody says it's not a
professional tool you claim that it is?

Doesn't matter to me. It's crap and the overwhelming majority of
prepress professionals know that. If you'd like to argue otherwise well
I guess it speaks to your prepress expertise. Or lack ot if.
 
B

Brian Kvalheim [MSFT MVP]

Hi Lee Blevins ([email protected]),
in the newsgroups
you posted:

||| Excellent. Makes your post moot.
||
|| No, the post was actually:

Like I said...

|| Sounds like MS bull - when somebody points out a problem you pass it
|| off as the program is not for pros but when somebody says it's not a
|| professional tool you claim that it is?

You have a cite?

|| Doesn't matter to me. It's crap and the overwhelming majority of
|| prepress professionals know that.

Maybe where you live. But it's not consistent with others and their
experiences and daily uses and output.

|| If you'd like to argue otherwise
|| well I guess it speaks to your prepress expertise. Or lack ot if.

And since I have over 10 years of experience operating in prepress
environment using Adobe, Quark, and Corel products in addition to the
knowledge and ability to output Microsoft Publisher files....where does that
leave you? Sounds like you have substantially MORE *lack* of prepress
experience if even YOU CAN'T FIGURE OUT how to use Publisher. Your fault,
not mine. I am just happy that we make an excellent margin/profit on our
Publisher files from hundreds of customers, in ADDITION to our use of Quark,
Corel and Adobe apps.

And because you can't figure out how to download an update to Publisher to
fix the known issue related to PS/CMYK, that is only YOUR fault. Not mine.
Not the consumers.

Call back when you are no longer wet behind your ears :eek:)
--
Brian Kvalheim
Microsoft Publisher MVP
http://www.publishermvps.com

This posting is provided "AS IS" with no warranties, and
confers no rights.
 
M

Mark Dunlop

"Brian Kvalheim said:
Hi Lee Blevins ([email protected]),
in the newsgroups
you posted: [...]

|| Sounds like MS bull - when somebody points out a problem you pass it
|| off as the program is not for pros but when somebody says it's not a
|| professional tool you claim that it is?

You have a cite?
On or shortly before 20 Dec 2003, in article
<[email protected]>, Brian Kvalheim
Because Publisher is not a professional DTP application.
[...]
 
B

Brian Kvalheim [MSFT MVP]

Hi Mark Dunlop ([email protected]),
in the newsgroups
you posted:

|| On or shortly before 20 Dec 2003, in article
|| <[email protected]>, Brian Kvalheim
|| [...]
||| Because Publisher is not a professional DTP application.
|| [...]
|| --
|| Mark Dunlop

Um, no. Where I said it WAS a professional DTP application. Gotta love the
spin you guys have in the usenet.
--
Brian Kvalheim
Microsoft Publisher MVP
http://www.publishermvps.com

This posting is provided "AS IS" with no warranties, and
confers no rights.
 
M

Mark Dunlop

"Brian Kvalheim said:
Hi Mark Dunlop ([email protected]),
in the newsgroups
you posted:

|| On or shortly before 20 Dec 2003, in article
|| <[email protected]>, Brian Kvalheim
|| [...]
||| Because Publisher is not a professional DTP application.
|| [...]
|| --
|| Mark Dunlop

Um, no. Where I said it WAS a professional DTP application.

Er, no. Where you said: 'Because Publisher is not a professional DTP
application.' Those are your words.
Gotta love the
spin you guys have in the usenet.

And what spin would that be?
 
R

RSD99

Well ... you tried to tell *me* many times that it was ... and that *I* was
mistaken in stating that it (essentially) did not have the 'chops' to
compete with offerings such as PageMaker, InDesign, Ventura, or Quark
eXpress ... let alone Serif's PagePlus.

Selective memory, again, Brian?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top