Ray_Net wrote:
Ed Mullen wrote:
Ray_Net wrote:
Ed Mullen wrote:
John wrote:
I am composing a webpage in the composer app (which it had a way to
publish files to the FTP server without me using a FTP app) but
anyways
I did a copy and paste form Word and this is what I got.
Version:1.0 StartHTML:0000000273 EndHTML:0000024343
StartFragment:0000003103 EndFragment:0000024307
SourceURL:file://localhost/Users/jwolf6589/Documents/Microsoft%20User%20D
ata/Saved%20Attachments/What%20does%20the%20Bible%20say%20about%20the%20L
ord%C2%B9s%20Day.doc
Honoring the Sabbath or Lord¹s Day
What is that?
If you do Edit - Paste Without Formatting in the Normal tab of Composer
you'll just get plain text. Word produces non-standard HTML and should
/never/ be used to create Web pages.
If the page in Word is simple ... Word can be used to save the file if
you choose the (page web(.htm) filtered) format.
It still produces non-standard HTML and won't validate. Try it yourself:
http://validator.w3.org/
yes .... but http://home.scarlet.be/~pin10521/TESTPAGE.HTM works
correctly with all browsers ....
"... works correctly ..." is almost meaningless to the conversation
which is about creating reliable valid HTML (and CSS).
Yes, that simple (non-compliant) page will display the same in the five
major browsers I just looked at. However, it's not valid or compliant
HTML markup.
http://validator.w3.org/check?uri=http%3A//home.scarlet.be/~pin10521/TESTPAGE.HTM
http://tinyurl.com/28ydmrr
This one only contains compliant HTML, validates and is far simpler coding.
http://edmullen.net/temp/test02.html
Further, it contains no such following nonsense as yours does:
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
While that simple example may "work correctly," more complicated pages
generated by an MS Office product are un-likely to look the same across
browsers.
Just an idea ... How many web pages in percent are W3C compliants
without any error or warning in the world ? :-)
No idea. So what? If some large percentage of people designing Web
pages are using invalid code why should you?
Virtually all of the several hundred pages on my sites *are*.
My point is not that validation is some holy grail. But it is a
starting point for design. And it's a great tool for quickly catching
inevitable typos and other lapses instead of visually pouring over
source code. If you design to the standard the chances of a Web page
looking essentially the same on the major browsing platforms is greatly
enhanced.
If you rely on WYSIWYG tools you're just asking for trouble.
And, by the way, it's not just purists or hobbyists who design to be
compliant with the W3C recommended standards:
http://validator.w3.org/check?uri=http%3A//www.ibm.com/us/en/
Anyway, this is drifting off-topic from answering the OP's issue. Which
I did. It's not a SeaMonkey issue it's a user issue.
--
Ed Mullen
http://edmullen.net
Deja Loo: I've heard this flush before!
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
