Hi Phillip:
Around here, it's worth mentioning that the DreamWeaver "Fix Microsoft HTML"
command is a bit of a double-edged sword.
It may "Fix" your code, or it may do something else entirely that also
begins with "F"...
Because Microsoft Word does not "produce" HTML. It never has. It produces
XML.
Experienced users who know that what they really wanted was HTML can use
DreamWeaver's "Fix" command to very good effect (FrontPage 2003 has a
similar function that works just as nicely).
However, inexperienced users need to be warned that if they use this
command, they won't get their document back! This can cause them to use
rude words...
Microsoft's design goal with XML was to enable a Word document to be
perfectly expressed in XML, so you could literally "round-trip" it to a "Web
Page" and back again without losing anything. And you can.
However, if you strip the XML out (which is what the DreamWeaver command
does) the resulting file is HTML not XML. It does not contain enough
information for an application to re-assemble a Word document from the code.
For a web person, that wouldn't matter at all, and they can use the
reduction in code that results. But for office workers publishing things to
the corporate intranet, they are going to come messily unstuck when they
discover that their Excel spreadsheet lost all its formulas, their Word
document pictures and charts are no longer updateable, or their PowerPoint
presentations no longer "present".
XML is now a relatively common language on the "Web". All of the major
browsers support it. There is no law that says the "Web" must use only
HTML. XML is also a W3C standard. And you can do a hell of a lot more with
it than you can with HTML.
Interestingly, one of the character-building features of XML is that it is
designed to be decoded by a lighter-weight parser that HTML, so one thing
that is illegal in XML is implying the closing tag. You have to specify
both tags in each pair in XML
But what I am really trying to say, for users less experienced than Phillip,
is "don't strip Word's web code unless you know what you are doing: you may
end up breaking your document."
Cheers
On 10/10/04 2:09 AM, in article (e-mail address removed),
I use DreamWeaver as well for maintaining My Association's website.
I can use word documents as well just save them as html
Then open them in DreamWeaver and use command "Fix Microsoft HTML".
If I need to make minor corrections they are easy to do.
By the way you can drag and drop Images as well into Macromedia
DreamWeaver. Have Beth sit down with you and show you how.
Deamweaver is set up so you can use code window in which if your a Code
PhD you can use that window, you can WYSIWYG window (use all that Drag
and Drop stuff), or a Split view (Showing both).
By the way MS is one of the founding Corps that created W3C the very
standards it gives the one finger salute to.
While front page may be drag and drop easy. what makes it a swear word
is not easy of use. But the code is so bad that it causes problems in
"all" Browsers in Mac/Windows/Linux/UNIX except IE. which has self
healing feature that anticipates missing code or duplicate code
Elements, and either suplies the missing pieces, or ingnores the
duplicate items.
John McGhie wrote:
Phillip:
If you spend enough time with the open source browsers, you will find that
while they may be "standards compliant" they're all a little selective
about
which standards they actually comply with, and to what extent.
Much like the name brand browsers, actually
Yes, of course that particular article was created in FrontPage. The
entire
website was created in FrontPage, with the exception of the Mac section,
which Beth did using DreamWeaver. Many of the longer articles were
actually
created using Microsoft Word instead of any HTML editor.
And yes, Web designers do consider FrontPage to be a swear word, and
there's
a reason for that. It's very difficult to charge $10,000 for a site that
takes a professional web coder two weeks to make in DreamWeaver when some
klutz with a copy of FrontPage can achieve exactly the same appearance in
15
minutes by dragging and dropping stuff around in FrontPage.
Yesterday I created a 250-page subweb in 15 minutes. I used Word. The
much-revered web editors won't get anywhere near that level of
productivity.
So I am more than happy for the web designer community to hang onto its
religious convictions. Because *I* get to hang onto the customer's money
Cheers
On 6/10/04 4:51 AM, in article (e-mail address removed),
John McGhie wrote:
Phillip: That's weird. It printed perfectly here from Safari (once you
hit
RELOAD enough times to get the page to display...)
Which browser were you using?
Cheers
On 5/10/04 1:24 AM, in article (e-mail address removed),
John McGhie wrote:
Thanks Matt:
Fixed it (the article, not the user's problem...)
Cheers
John.
On 30/9/04 8:42 AM, in article
BD808853.14AA8%
[email protected],
On 9/27/04 12:28 PM, in article
BD7DB7DD.40CF7%
[email protected], "Dayo
Mitchell"
Are you on a Mac? HP is known to have issues with that, and there
are
some
beta drivers that might fix it, but I didn't realize it extended to
MacWord.
See if this helps:
http://word.mvps.org/FAQs/Formatting/BottomsDontPrint.htm
(hit refresh a few times in Safari, or use a different browser)
Does it make a difference if you use Insert | Page Number vs.
inserting
the
page number from the header/footer toolbar? (these behave
differently)
On 9/27/04 8:26 AM, "Lynne Watson" wrote:
We are unable to make page numbers print correctly at the
bottom of a page.
When I insert a page number it prints only the top half of
the digit. Changing the margin settings seems to have no
effect. The only work around is to enter the footer and put
a carriage return below the number.
I am using two HP printers a G55 and a psc 1310 with the
same result.
Any help much appreciated.
Lynne Watson
Another solution (which should be added to the MVP page) is to go to
"File
|
Page Setup" and actually choose the printer you will be printing to,
rather
than "Any Printer" and OK. Then Word will either warn you of items
outside
printable region or will just print fine.
Matt
MacWord Testing
Macintosh Business Unit
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Please do not send email directly to this e-mail address. It is for
newsgroup purposes only.
Find out everything about Microsoft Mac Newsgroups at:
[
http://www.microsoft.com/mac/community/community.aspx?pid=newsgroups]
Check out product updates and news & info at:
[
http://www.microsoft.com/mac]
Strange Thing I went to print the Page refered to in Link. All I could
get was white space about half inch wide at top rest of screen was grey.
I use Mozilla which is standards compliant. Another MS only deal guess
it was written in FrontPage. (which with about 90 percent of web
designers is a swear word.
Guess I'll have to open it with IE to print it. :-(
