Maureen,
The answer is a lot of practice.
While I appreciate the fact that you and Don have chosen to defend me and
confront this person, you should know that he already knows he is wrong. An
IT professional? Maybe. Here to save the children from the evils of
Publisher webs? Nonsense!
He has already made all these irrational arguments against using Publisher
to build webs before. I had a protracted 'debate' with him back in February
in the general Publisher newsgroup about the suitability of using Publisher
to build websites. Though I proved how untenable and irrational his
positions and arguments are, I also created a personal enemy, and thus the
attacks in this group. Here is a link to that thread:
http://www.microsoft.com/office/com...84c7&mid=1661ac83-2fa5-40f5-b40f-bdd6bcc884c7
I won't reiterate everything that was said and 'debated' in that thread, but
suffice it to say that he has already brought up most every possible reason
and argument as to why someone should not use Publisher to build a web, and
I have refuted each and proved them all to be spurious. In the end he can
offer no facts or rational, logical reasons for not using Publisher to build
webs, and that is why he has resorted to the personal attacks and name
calling. That is why you have seen him getting increasingly more angry and
frustrated as I have followed him around and corrected his misinformation.
He is wrong and he knows it.
His primary argument is that no one should use Publisher to build webs
because Publisher does not produce 'standards compliant' html code. This is
based on the premise and assumption that unless the code is 'standards
compliant' you cannot achieve cross browser compatibility. This argument is
flawed and wrong when it comes to Publisher webs.
The bottom line is that in spite of the fact that the none of the different
versions of Publisher produce 'standards compliant' html code, you *can*
produce cross browser compatible webs with Publisher 2000, 2002, 2003 and
2007, *IF* you know how to use the program properly. He simply does not know
how to use the programs correctly and continues to show his ignorance in
most every post in this group.
Over the past 5 years or so I and others in this group have addressed the
issues of Publisher web cross browser compatibility and found most of the
issues that cause problems are usually related to print publication
formatting, layout and design techniques that are easily resolved by
tweaking the layout or design slightly. What a user needs to understand is
that Publisher cannot convert all print designs and formatting to html that
is cross browser compatible, but that is true regardless of what tool you
use. However, we have also found that if you avoid a few formatting and
layout pitfalls, and tweak your pages so that they function correctly and
look good in IE and FireFox, then they will also work in Opera and Safari
and most other browsers.
You *can* build Publisher webs that are cross browser compatible. This is
not an opinion...it is a fact, and he can scream and yell and stomp his
feet, attack me and try to scare people as much as he wants, and it won't
change it.
He has also twisted and distorted my position about the choice of using
Publisher to build webs. To set things straight, my basic position is that
the choice of whether to use Publisher for a web really depends on what the
user's goals are for that web. If all they want is a relatively small,
simple static, fixed width website, and if they already own and know how to
use Publisher for print publications, then it can be a good choice to easily
and quickly build a good looking, fully functional, relatively fast loading
and crossbrowser compatible website. I also believe strongly that suggesting
that a person *must* use a program that produces 'standards compliant'
html code is simply overkill and unnecessary for what most people want to
accomplish with Publisher.
I am not saying that it is the best choice for everybody, and in fact
frequently suggest to some people that they should use other programs when I
feel they will not be able to achieve the goals they have for their sites.
Anyone that reads this group on a regular basis knows this to be true. If
you want more dynamic functionality or are planning a large site, then you
might consider investing in a program such as Dreamweaver or Web Expression
or other code editor programs, or perhaps a server side solution. But you
will have to invest a lot of hours learning html coding, CSS and more to use
those programs effectively and not everyone has either the time or the
aptitude.
With these things said, my goal in this group is to continue to provide
people who post in this group all the information they need to make educated
decisions about using Publisher to build their webs, and to help those
people that do choose to use Publisher. When this person posts
misinformation I will follow and clean up after him, and I would appreciate
your help along with Don's, Spike's and the other regulars in the group.
However, I refuse to engage him directly...I have wasted enough of my time
with his nonsense.
DavidF