Thanks Tony, that was quite helpful. I've read up on XHTML and will bring my code up to scratch. It makes sense. I've also solved my language problem.=20 Cheers, Robbie Sandberg -----Original Message----- From: vicsireland-bounce@xxxxxxxxxxxxx [mailto:vicsireland-bounce@xxxxxxxxxxxxx] On Behalf Of Tony.G.Murray@xxxxxx Sent: Friday, June 27, 2008 9:22 AM To: vicsireland@xxxxxxxxxxxxx Subject: [vicsireland] Re: Language recognition on websites - follow up question Hi Robbie, It could do. TBH, I'm a little rusty on this stuff, but here is a possible theory. Perhaps we're dealing with a combination of versioning and malformed page=20 issues here. As you probably know, the way of specifying the language on a page is=20 slightly different... depending on whether you are using HTML 4.x or=20 XHTML. Assuming that this is all fine.. and your different types of pages=20 have the correct kinds of lang definitions... I understand that the lang attribute was adopted in HTML 4.x. Now, the=20 problem is, it is very easy to break an HTML 4.x page (especially HTML 4.x=20 Strict). Could it be, that a module defined as an HTML 4.x (transitional=20 or strict) has it's lang attribute correctly specified... but somewhere=20 down the page, there is markup present (or not present) which breaks the version's guidelines... Thus producing a malformed HTML 4.x document? Shot=20 in the dark, that one! It is understandable that the XHTML pages you are viewing work each time with the correct lang specifications, as by it's nature... XHTML either=20 works or it doesn't. Any error in an XML module renders the document=20 'malformed' (or broken), and given that XHTML is XML that browsers can=20 interpret, well, the same rules apply. HTML 4.x transitional and then strict attempted to standardise HTML, as it=20 completely spun out of control soon after it was born. New elements were=20 introduced on the fly, some browsers became incompatible with the newer=20 inventions... Versions of different browsers interpreted and rendered=20 content in different wild and wonderful ways... It was a mess. The next step on the road to standardisation was XHTML, which brings the whole ball=20 game back in line with what HTML started out as... that is, SGML. So, as a developer of the stuff, I'd recommend you use XHTML, it will be best for you and for your users. Using XHTML will not require you to=20 learn a new fancy language... once you know one markup language, the rest=20 of them look familiar... You just have to be more careful developing with=20 XHTML. Best wishes, Tony "Sandberg, Robert" <robert.sandberg@xxxxxxx> Sent by: vicsireland-bounce@xxxxxxxxxxxxx 26/06/2008 13:59 Please respond to vicsireland =20 To: <vicsireland@xxxxxxxxxxxxx> cc:=20 Subject: [vicsireland] Re: Language recognition on websites=20 - follow up question Hi Tony! Few! I now know that the language of a web page can be declared using either the meta tag, of which there are 2 variations, or using the http header function, or using the lang tag. Unfortunately none of these work for me. I have compared the code of a couple of websites where the language declaration does not work, with ones where it does work, and I can't find anything that would explain the different behaviour. Except that the sites where it did work were all xml, whereas the ones where it didn't work were pure html. Does that have any baring on the matter? Or does something else need configuring for the language declaration to work? Cheers, Robbie -----Original Message----- From: vicsireland-bounce@xxxxxxxxxxxxx [mailto:vicsireland-bounce@xxxxxxxxxxxxx] On Behalf Of Tony.G.Murray@xxxxxx Sent: Thursday, June 26, 2008 11:42 AM To: vicsireland@xxxxxxxxxxxxx Subject: [vicsireland] Re: Language recognition on websites Hi Robbie, See section 4 on the following page: http://www.w3.org/TR/i18n-html-tech-lang/ Cheers, Tony =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D The vicsireland mailing list To unsubscribe at any time send a mail to: vicsireland-request@xxxxxxxxxxxxx with the word "unsubscribe", without the quotes in the subject of the message.=20 To contact the moderator send mail to: tim.j.culhane@xxxxxxxxx For mor information on the Visually Impaired Computer Society visit: http://www.vicsireland.org =========================================================== The vicsireland mailing list To unsubscribe at any time send a mail to: vicsireland-request@xxxxxxxxxxxxx with the word "unsubscribe", without the quotes in the subject of the message. To contact the moderator send mail to: tim.j.culhane@xxxxxxxxx For mor information on the Visually Impaired Computer Society visit: http://www.vicsireland.org