This is the Message Centre for TRiG (Ireland) A dog, so bade in office

About your GuideML

Post 1

Traveller in Time Reporting Bugs -o-o- Broken the chain of Pliny -o-o- Hired

Traveller in Time smiley - tit beeing pedantic
"It is known the GuideML does not have to be capitalised to work, however it is preferred to use only Capitals for the Tags. (apparently the parser uses capitals only and has to translate undercasts)

And even more pedantic; use indention for nested tags smiley - smiley.


smiley - space
smiley - spacesmiley - space
smiley - spacesmiley - spacesmiley - spacelist item
smiley - spacesmiley - space
smiley - space
smiley - space
smiley - spacesmiley - space
smiley - spacesmiley - spacesmiley - spaceanother listed item
smiley - spacesmiley - space
smiley - space


smiley - cheers "


About your GuideML

Post 2

TRiG (Ireland) A dog, so bade in office

<./>TestUserPage612575</.>

I like the mixed case. Does it actually cause problems?

The indentation might make it easier to follow the coding, but it won't have any affect on the parser, will it? I would use indentation if I had any long lists or tables, but as it is, it's okay.

Actually, my PS is long overdue an update. It may change entierly, but I'll keep the basis of it: the <!-- explanation --> of what the GuideML does in each section, the filter between different sites (it currently has one version for h2g2 and another for everything else; I might do a few more versions for, say, the hub and, erm, well, nothing else).

TRiG.smiley - geek


About your GuideML

Post 3

Traveller in Time Reporting Bugs -o-o- Broken the chain of Pliny -o-o- Hired

Traveller in Time smiley - tit running a dozen browsers
"Some browsers choke in some mixed case Tags, I never bothered finding out what does work and what not.

Fact is the indention and capitalisation makes the code human readable, a fact I give more value then an obscure browser failing. "


About your GuideML

Post 4

six7s

Hi TRiG,

<< Because of the processing we currently do, we do accept lowercase tags, so nothing will break if you use lowercase, but a move to all lowercase as a policy decision would (at some stage) require a complete rewrite of all our stylesheets, and a massive job of processing all the articles in the database. >>

Jim Lynn, June 2002, A773787

Bob only knows if that is still applicable


About your GuideML

Post 5

TRiG (Ireland) A dog, so bade in office

"Some browsers choke in some mixed case Tags."

I don't think that that has much to do with it. I just looked at the source code for my userpage. It's in HTML, not the XHTML that I expected.

Now, correct me if I'm wrong, but I think that HTML is case insensitive -- you can open with and close with . But XHTML redefines HTML as an XML dialect, and XML is case sensitive. Theoretically, , , and could all mean completely different things. So, in XHTML, to prevent confusion, all tags are in lower case.

But the mixed-case HTML is older, so most browsers should cope with it, no?

In any case, my GuideML tags have been rendered not as XHTML tags but as HTML tags. (Note the lack of a closing soldus, you don't need them in HTML.)

As GuideML is an XML dialect, an opening tag must be closed with a tag, not a tag. These are, essentially, different tags with the same meaning.

Since the case of the HTML output has, seemingly, nothing to do with the case of the GuideML input, I don't think we need to worry about browser compatibility.

TRiG.smiley - geek


About your GuideML

Post 6

TRiG (Ireland) A dog, so bade in office

Anyway, http://validator.w3.org/check?uri=http%3A%2F%2Fwww.bbc.co.uk%2Fdna%2Fh2g2%2Fbrunel%2FU612575&charset=%28detect+automatically%29&doctype=Inline&ss=1&outline=1&verbose=1

And it applies just as much to proper Edited Entries:

http://validator.w3.org/check?uri=http%3A%2F%2Fwww.bbc.co.uk%2Fdna%2Fh2g2%2Fbrunel%2FA218882&charset=%28detect+automatically%29&doctype=Inline&ss=1&outline=1&verbose=1

http://validator.w3.org/check?uri=http%3A%2F%2Fwww.bbc.co.uk%2Fdna%2Fh2g2%2Fbrunel%2Ftest218882&charset=%28detect+automatically%29&doctype=Inline&ss=1&outline=1&verbose=1

TRiG.smiley - geek


On the other hand,

Post 7

TRiG (Ireland) A dog, so bade in office

http://validator.w3.org/check?uri=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FH2g2&charset=%28detect+automatically%29&doctype=Inline&outline=1&verbose=1

http://validator.w3.org/check?uri=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FMain_Page&charset=%28detect+automatically%29&doctype=Inline&outline=1&verbose=1


On the other hand,

Post 8

Traveller in Time Reporting Bugs -o-o- Broken the chain of Pliny -o-o- Hired

Traveller in Time smiley - tit browsing html manual
"Reading many interesting things."

Throws manual out of windows

"Any site useable in 'all browsers' must be smiley - oksmiley - biggrin.

Hmm, ok, wiki does work smiley - ok on most browsers as well smiley - cheers.
By the way: < F656?thread=533179 >. Where did I keep this wiki password . . . . "


On the other hand,

Post 9

TRiG (Ireland) A dog, so bade in office

Yes. Wikipedia and W3 pages are the only ones I've found so far that pass the test. I don't think anything on the BBC does. It seems that most hootoo pages are missing their DOCTYPE declaration.

Do you know any handy resource to the correct writing of XHTML from scratch? I do know a tiny bit of HTML, but I've forgotten a lot of it. The GuideML I use here is handy in keeping my memory alive.

TRiG.smiley - geek


Key: Complain about this post