• Ok, here is the question.
    As I can see almost 90% of WP blogs use 1.0 Transitional, but wp.org uses 1.1 (strict?), moreover, some themes, including the one I use (Blix) have 1.0 Strict by default.
    Thus My question stands – which one should I use?

    I want it to be as future-proof as possible (it’s a new blog, so I dont need to convert any old posts whatsoever), at the same time I do want to use the WYSIWYG in the upcoming 1.6 and of course I want my site to be XTML valid 😉

    Thanks in advance

Viewing 15 replies - 1 through 15 (of 22 total)
  • Transitional will be fine for a looooooog time yet.
    It’s more forgiving that Strict (obviously) but Strict confers nothing in terms of performance / presentation but it does add to maintenance if you wish to stay valid all the time.

    I’d stay with transitional.

    Thread Starter resist

    (@resist)

    So should it be 1.1 by any chance? I mean whats the difference and whats the reasoning behind using it at wp.org? (just wondering 😉 )

    And if I use 1.0 strict or 1.1 strict, well… as I presume – WYSIWYG in 1.6 would give me some trouble right?

    Tnanks

    wysiwyg ? No clue.

    HTML is being superceded – in the very very end – by XML. But given that there are millions and millions of pages that have horrendous markup, that use tags and tables as if they were confetti and the wedding of the century and that will never be changed, and given that browsers will always support those pages so you can see them, then right now the differences really come down to a desire to push Web Standards, with a dash of geekiness 🙂

    If you are after a blog that will behave predictably, then stick with transitional. The flavour makes no odds really but the higher the number, the closer to xml you will get.

    transitional / strict – it’s a geek thing. No more, no less.

    XHTML 1.1 should probably be avoided until a browser that can handle it is the market leader. IE, which still (unfortunately) holds a great deal of market share completely barfs if you are truely XHTML 1.1 compliant (sending the proper headers as application/xhtml+xml iirc).

    Thread Starter resist

    (@resist)

    Well, but you think that 1.1 or 1.0 strict will be THE standard anytime soon? As podz pointed out transitional should be fine for a long, besides I found even 1.0 strict a bit confusing, for an example, I used HTML to XHTML 1.0 strict converter to convert very primitive code: <img src=”http://website.info/avatar.gif&#8221; alt=”My Avatar” align=”right” vspace=”2″ hspace=”2″> so I got this <img src=”http://website.info/avatar.gif&#8221; alt=”avatar” align=”right” vspace=”2″ hspace=”2″ /> not a big difference eh? But the funny thing, it does not validate heh. The code seems to me perfectly fine…

    resist
    the code you are using is depricated
    for strict!

    transitional is for those they wouldn’t learn correct xhtml 😉

    and so you see I’m not a friend of transitional 😉
    like podz

    strict is not a gimmik and not geeky it is simply correct modern standard;)

    you see there are two very different views

    but you have to know I’m a preofessional designer
    I can’t use transitional —
    I have to show that I master strict;)

    if you would like to use the code for images above use the doctype of transitional and your site is valid.

    I’m so happy of valid websites (transitional or strict –valid is the option…)
    -because they offer a chance for people with disabilities – and I agree with podz most of * web master* using html tags like confetti

    kindly regards
    Monika

    Thread Starter resist

    (@resist)

    it’s hard to decide because I CAN handle strict but, at the same time the majority of Wp powered blogs use transitional. Besides Im not a professional designer, thus if there is a converter of some kind that would help me with strict i would go with strict. However, I still have the concern regarding wp’s future and WYSIWYG editor in 1.6. I bet at least some tags it generates are not 1.0 strict valid, Im more than sure. Does this mean WP goes Transitionl officially?

    Strict is for geeks like me. 1.1 is for people whose userbase is less than 1% IE users. That’s about it….

    [If you looking for tidbits here about 1.6, I don’t think you’re going to get them….]

    Thread Starter resist

    (@resist)

    1.6? well 1.6-ALPHA-2-still-dont-use is out there, so that’s not my point. All I’m trying to do is to find a solution to the problem I face, isn’t that the purpose of this forum?

    But back to the topic, can you advise me an “easy” way to keep up with strict without spending days to learn it like I know html for instance?

    I know transitional is the way to go for now, but it’s like high way and low way, if you know what I mean…
    thanks

    PS. the illustration of what Im saying is right here http://validator.w3.org/check?uri=http%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2F42408%23post-238230 try to validate the page you are viewing right now and see what happens.

    I think podz said it best, but the main point is to be valid. Valid code = happiness all around. And being blind, it’s just so wonderful to go to sites that I don’t have to fight with to find/read/etc. the content.

    Personally I’m using 1.0 transitional on my blog, but it’s been as high as 1.1 and I’ve used 1.1 on other sites (I’m actually in the process of converting a site to it, fun fun fun), but it really comes down to what you feel is comfortable. 1.0 transitional is absolutely fine, especially if you’re not familiar with the code to make sure it validates. It works in pretty much every browser – and you still get the geek cred for validating your site.

    As for 1.6, well this isn’t a forum for that, so you probably won’t get much of an answer. But WP has always been out of the box 1.0 transitional valid, so I’m sure it’ll be at least that. And probably higher because there are a good handful of WP users that stay at higher code.

    I don’t have any problem validating my blogs to 1.0 Strict. I never have had.

    [Edit: really the only key is to NOT use stuff like js calls to “name” etc. – that’s the only things I’ve ever had to work around.]

    Thread Starter resist

    (@resist)

    But WP has always been out of the box 1.0 transitional valid, so I’m sure it’ll be at least that. – Probably that’s the key. I mean, it’s clear that an ordinary user of WP will not keep up with strict in any instance, so basically I understand this as WP developers want it be transitional and not planning to move to strict anytime soon, considering the logical fact of WYSIWYG editor in 1.6 (yes, yes I know it’s not a place and a time to talk about it 😉 )

    There’s a respected school of thought that says XHTML offers no advantages over HTML for the forseeable future. At present, time spent converting valid XHTML Transitional to valid XHTML Strict could well be time wasted.

    But it doesn’t really take any time. At least, it doesn’t take me any time to speak of. I convert every theme I use to strict. I write my own in strict. The last time I converted one, I had to change TWO closing tags. That was it. Once you’ve done it a few times, it’s a piece of cake….

    I have 8 blogs right now, with a total of 30-40 themes (lost track, wasn’t worth going right now to count). It’s just not really a big deal….

    vkaryl
    you are right, but I know that most of the blogger can’t handle the quicktags and so they are using one of the WYSIWYG editor-
    and the editors can’t (or wouldn’t) handle strict . If I share a theme I change the Doctype to transitional, although the theme is valid strict.
    Because I agree to ceo’s arguments.
    **And being blind, it’s just so wonderful to go to sites that I don’t have to fight with to find/read/etc. the content.**
    and hope you haven’t to fight with the content of my blogs,–if -then with the language 😉
    regards
    Monika

Viewing 15 replies - 1 through 15 (of 22 total)
  • The topic ‘XHTML 1.1 vs 1.o Strict/Transitional’ is closed to new replies.