You're wrong, only fonts that the viewer has installed on their machine will
display, if they don't have a font that you used a default font will
display. Google: " web safe fonts"

You can use special fonts if you convert them to images, but you'd not want
to do this for anything but headings or something special because search
engines can't read text in an image...not to mention server overhead.

Designing for print is a world away from designing for the web!...maybe a
universe away.

Karin,

In addition to what Rob said about web fonts, Publisher will either convert
non-web fonts to an image automatically, or may substitute in a web font
when viewed. There are 11 web fonts. Reference:
About Web fonts and font schemes:
http://office.microsoft.com/en-us/publisher/HP010174931033.aspx?pid=CH063575481033
The point is that no matter what program you use to build your site, if you
use non-web fonts on your page, the results will be the same.

Animated GIFS are supported in newer versions of Publisher, and you can
overlap text boxes and other design elements without converting all the
elements to a new non-animated GIF. You can layer images on top of text
boxes in 2007, where in Pub 98 through 2000, this would be converted to a
common GIF.

However, you cannot use "word wrap" in a web publication. This is an example
of a print format, that doesn't convert correctly to html. In Pub 98, if you
wrapped an image with text, you would get a combined image of the text and
the original image with the text wrapped around the image. In 2007, you get
an image on top of the text, and the text remains text.

Other examples of print formatting that chokes Publisher when you convert to
html would include most paragraph spacing and special formatting, tables are
converted to an image, some bulleted lists, some odd sized fonts, some
columns, some gradient fills, some custom borders, and... You also will find
that some things work when your website is viewed in IE, but don't work in
FireFox and other browsers, so you also have to modify your design so that
it has cross browser support. I can't provide a complete list, nor can I say
that other programs might not be able to workaround these formatting issues,
but in general some "print formatting" will cause problems and require you
to design around what you can and cannot do....and what you should and
should not do.

You could use underlines for emphasis in a print document, but in a web
document that would tell the viewer that is supposed to be a hyperlink. You
would probably layout a print document 8.5 inches wide...or paper width
wide, but you don't want your web pages so wide that it requires the viewer
to scroll side to side. Publisher produces a fixed width, left justified
page, while other programs can produce variable widths and self centering
pages. You can use a high resolution image in a print document, but need a
lower resolution image that loads quickly in a web document. You can use
shadows, embossing, etc. in a print doc, but will not get the same effect in
a web doc. Look at your local newspaper, and then look at the online
version...that is a good example of formatting and designing for print vs.
web media. Part of it is not being able to convert to html, and part of it
is simply the different mediums, but less to do with the program you use to
build your web site.

Publisher is primarily a DTP, with limited web building capability and is
intended for relatively small, simple, static web sites. If you work within
its limitations you can produce an effective and attractive web site, but it
will never have the capability of a program that is designed specifically
for web building. It all depends on the goals and the scope of what you want
out of a web site as to whether Publisher is an acceptable choice.

DavidF