Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 8 of 8
  1. #1
    New to the CF scene
    Join Date
    Apr 2003
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Frontpage 2002 No Doctype statement

    Hi all, can anyone advise me why Frontpage 2002 does not insert a doctype statement at the top of a page.?

    Can I insert one myself and if so which doctype would frontpage use?

    I realise that it may not conform to wc3 standards but if one where to use a doctype statment what would it be?

    I dont want to get into the Frontpage Dreamwearver, handcoder disucssion here if possible, Frontpage is what I use for better or worse


    Regards
    AndyD

  • #2
    Senior Coder Mhtml's Avatar
    Join Date
    Jun 2002
    Location
    Sydney, Australia
    Posts
    3,531
    Thanks
    0
    Thanked 1 Time in 1 Post
    Why u usin' frontpage? Dreamweaver is sooo much.... joke

    Well i'm not sure exactly how frontpage 2002 codes html but I can tell you that meerly inserting a doctype declaration will not make it conform to the standard unless the rest of the code does.

    You can always validate it @ w3c.org!
    Omnis mico antequam dominus Spookster!

  • #3
    Senior Coder
    Join Date
    Jun 2002
    Location
    near Oswestry
    Posts
    4,508
    Thanks
    0
    Thanked 0 Times in 0 Posts
    A doctype won't really help you, as Mhtml said - a doctype simply tells you which version of (HTML in this case) the document is supposed to comply with.

    But since FP can only generate non-compliant coding, you may as well not bother having a doctype at all.
    Last edited by brothercake; 04-15-2003 at 03:32 PM.
    "Why bother with accessibility? ... Because deep down you know that the web is attractive to people who aren't exactly like you." - Joe Clark

  • #4
    Regular Coder
    Join Date
    Jun 2002
    Location
    Canada
    Posts
    253
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Frontpage 2002 No Doctype statement

    Hi all, can anyone advise me why Frontpage 2002 does not insert a doctype statement at the top of a page.?
    probably... just because.


    Can I insert one myself and if so which doctype would frontpage use?
    yes you can. the frontpage factor has nothing to do with which doctype to enter, but your coding does. depends on what version/style of coding you are wanting to conform to.

  • #5
    New to the CF scene
    Join Date
    Apr 2003
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Whoops silly me.Of course now you've all explained it to me bit of a daft question, if Frontpage does not conform a doctype is irrelevant.

    I just wanted the code to conform to wc3 standards but if it means testing every page its impracticale, why cant MS go with the standards.... No I dident ask that ignore that or well have a thread a mile long ...lol


    Thanks Guys
    AndyD

  • #6
    Senior Coder
    Join Date
    Jun 2002
    Location
    Wichita
    Posts
    3,880
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Using FrontPage's gui interface is a sure way of getting a non-conforming document but if you simply use it to edit the html there's no reason you can't create conforming documents but then the question is why use it instead of a text editor.

  • #7
    Senior Coder Mhtml's Avatar
    Join Date
    Jun 2002
    Location
    Sydney, Australia
    Posts
    3,531
    Thanks
    0
    Thanked 1 Time in 1 Post
    I imagine that Microsoft believes they are "above" the standards, and should set their own. . . I'm sure some people will share this opinion.
    Omnis mico antequam dominus Spookster!

  • #8
    Senior Coder
    Join Date
    Jun 2002
    Location
    near Oswestry
    Posts
    4,508
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Originally posted by Mhtml
    I imagine that Microsoft believes they are "above" the standards, and should set their own. . . I'm sure some people will share this opinion.
    Mostly agree. But you have to consider the business case - it's arguably more important (commercially) to have a browser in which 99% of the world's websites work as expected, even the really crappy ones.

    Unfortunately that creates a vicious circle - because IE supports crappy coding, people continue to do it, usually because they don't even know what's wrong with it; because they, like almost everyone else, use IE.

    What you end up with is "de-facto" standards - what IE does is the de-facto standard. MS don't care how closely that conforms to the proscribed (w3c) standards - and why should they? The real benefit of standards compliance is interoperability - but as far as MS is concerned, progress is a timeline leading to the point where all architecture is MS; MS products have fantastic interoperability with other MS products, so MS don't give a rat's. Standards-compliance is like "well yeah, we 'll aim for it, but we have no qualms about abanding or reinterpreting it if it suits us".

    It's quite dark really; but there you go. It's the world.
    Last edited by brothercake; 04-15-2003 at 08:24 PM.
    "Why bother with accessibility? ... Because deep down you know that the web is attractive to people who aren't exactly like you." - Joe Clark


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •