change [UPDATED] syntax...

I’m currently working on creating an xhmtl interface and noticed one issue. The [UPDATED] token outputs the following

Observed Saturday, February 19 @ 11:54 PM EST at Logan Airport, MA<BR> Downloaded Sunday, February 20 @ 12:03 AM
and in xhtml all tags must be closed… so a
causes the page to be invalid. It’d be nice if one could either control the syntax or if the break could be changed to
as that would allow the xhtml design to be valid and it wouldn’t cause any issues at all with html designs.

ewelin, I’ll make this change for the next beta release.

Boy, that’s the great thing about standards … there are so many to choose from!

Hmmm, the HTML standard has been that
is a break in and of itself. There is no beginning and end because it is just a line break. You can’t really degine the beginning and end of a singular event like a newline. I’m surprised if xhmtl does not take that into account.

Even on the W3C HTML website,
is shown as a stand-alone tag:
http://www.w3.org/MarkUp/Guide/Advanced.html

I’m not an expert, just an occasional user of HTML code. Oh well, as long as the browsers all properly interpret

, I guess it wont’ matter to me.

– PatrickB

PatrickB, Weather Watcher uses IE, and IE understands , so that change should not cause a problem.

XML coding standards are based on the HTML 4 standards but are an extention to the standards. See http://www.w3.org/TR/xhtml1/ for a write up of the differences between the two.

While XML supports
(http://www.w3.org/TR/xhtml1/#h-4.6[/url]) it is best to use
rather than
. See [url=http://www.w3.org/TR/xhtml1/#C_2]http://www.w3.org/TR/xhtml1/#C_2
.

Note the “/follows the “br” not preceeds it as in standard HTML closing tags.

Ed

EdP, right. IE understands both.

Mike true, but the "xhmtl interface’ ewelin is working on may not nor is there any quarantee it will be viewed in IE.

Ed

EdP, let’s try this then… which browsers do not support
?

As quoted on the http://www.w3.org/TR/xhtml1/#C_2 page:

“the alternative syntax
allowed by XML gives uncertain results in many existing user agents.”

It’s not a question of
not working but rather the format you mentioned here:

quote:
"IE understands "
</font id=“quote”></blockquote id=“quote”>

From my own recent experience I can assure you that slashes, their direction and their number, are handled differently in Netscape than IE. Things that work fine in IE may not work at all in Netscape/Mozilla/Firefox thus my cautious approach.

Ed

quote:
It's not a question of
not working but rather the format you mentioned here
[b]EdP[/b], right. I meant to make it more clear that I was agreeing that the correct XML syntax is [i]
[/i], rather than [i][/i].

This time you did. [:)] Last time, not so much. [;)]

[:p]

Ed

quote:
[i]Originally posted by Mike Singer[/i] [b]EdP[/b], right. I meant to make it more clear that I was agreeing that the correct XML syntax is [i]
[/i], rather than [i][/i].
If i remember correctly it actually has to be lower case as well... i do beleve that upper case will cause an error. so it should be
i sometimes forget to leave the space in there but it should be there for good practice.

I have designed several xhmtl pages and have had no issues with browser compliance. It is a pain to get everything to match exactly on all browsers but it can be done. Just takes some times. Whats nice about xhtml is that one can control so much by just editing the CSS file[:D]