XHTML 1.1 vs 1.o Strict/Transitional

  • 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 7 replies - 16 through 22 (of 22 total)

  • Yeah, I think this is very true Monika, and if you aren’t familiar with what you can and can’t do in the stricter languages, then validating can be a really big pain in the neck. And I do really think it’s more important to be valid, than it is to be at a higher code. If you can’t get your lowest validation of HTML, then you just don’t need to be playing with stuff that’s sometimes a bit more complicated.

    resist, my point above about 1.6 was that if it’s out of the box compliant with 1.0 transitional, I’m sure that the built in editor won’t be creating invalid code. And what’s valid for 1.0 transitional that it’d output will most likely validate at a higher level, with few exceptions if any.

    Thread Starter resist

    (@resist)

    I just tried the latest build of 1.6 and the editor does use align= for images, so no wonder it’s not valid 1.0 strict or 1.1…
    So I think transitional is the future of WP, thus I guess I would go with it.

    I’m 1.0 Transitional, but just a few <BR />‘s and target="_blank"‘s short of Strict. ??

    Joebar, you can use a nifty li’l piece of inline js to fix the “target” problem:

    onclick=”window.open(this.href);return false;”

    Insert where you would normally have your target attribute. Validates just fine….

    Thread Starter resist

    (@resist)

    a valid js? interesting… how come?

    JavaScript “fix”? I suppose it depends on whether valid code is being produced simply for its own sake, or whether there’s actually a useful purpose behind it.

    I’ve just been through my site this morning & updated a few tags so that it validates as 1.1
    It didn’t really take that long (& was the first time I had tried to get anything to validate as 1.0 strict or 1.1)
    Mainly it was moving a few deprecated tags & updating some tags that occurred in the wrong place – they needed to be inside other tags for instance.

    Most of the code that gave problems was produced by plugins in the first place, but I also took the oportunity of going through the code to generally update a few bits of PHP, based on what I know now, but didn’t know when they were originally written.

    It would be interesting if (instead of sites popping up messages saying – best viewed in MSIE) browsers would show a message in the title bar, or status bar whenever sites did not validate as the DTD that they were using & also made it clear which DTD was being used. (Would this help to get rid of any of the bad coding any quicker.)

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