Български Deutsch Español हिन्दी Magyar Polski Português Português-BR Română
Accesskey n skips to in-page navigation. Skip to the content start.
Intended audience: users, XHTML/HTML coders (using editors or scripting), script developers (PHP, JSP, etc.), CSS coders, schema developers (DTDs, XML Schema, RelaxNG, etc.), XSLT developers, Web project managers, and anyone who is new to internationalization and needs guidance on topics to consider and ways to get into the material on the site. xxx adapt this to describe the intended reader of the article.
Updated xxxYYYY-MM-DD HH:MM
When is it appropriate, or not, to use language negotiation?
Insidenotes
All the text in this div will be displayed to the right of the main text flow, but will displace the right side of the main text flow if there is another floated item to its right. It was designed to be used only at the top of a page where sidenotes may overlap with stuff at the top of the right page column. Normally you should use a regular sidenote, illustrated below.
Level 2 headings and their related content (including any level 3 sections) should be surrounded by a div with class="section".
This FAQ addresses the question of when it is appropriate (or not) to set up language negotiation on the server.
Try to summarise the answer in the first paragraph, then go on to provide details.
When providing additional paragraphs in the answer, try to use one paragaph per point, and summarise that point in the first sentence of the paragraph. This helps people skim the article for relevant information.
The answer should be written in an easy to read style, but be as direct and simple as possible. You should also take great pains to ensure that the answer remains very focused on just directly answering the question at the beginning of the FAQ. Put tangential information in the 'by the way' section or in a different article. Of course, a similar simplicity and directness should be used for general articles, too.
Level 3 headings and their associated text should be surrounded by a div with class="section2".
Lead in. A lead in will be bolded text at the start of a paragraph. It should be used to break up long passages for the reader, so that they can read more comfortably, and also find specific information quickly on review.
The first paragraph after a level 4 heading should go inside the h4 div, like this.
Additional paragraphs related to the level 4 heading should follow here, outside the h4 div.
Here we have some additional text, blah, blah, blah...
SIDE NOTE Information at the beginning of this div with class="sidenoteGroup" is just part of the ordinary flow of the article. The div, however, marks the point at which any associated note text will occur in a voice browser or destyled page.
You can have as much content as you like here, using p, table, div or any other markup.
Content-Type: text/html; charset=utf-8 Content-Language: en
You can put any markup you like in here, though it is often best to avoid p etc for the first bit of text, so that it lines up better with the text in the main body.
Here is some more text: blah, blah, blah....
This 'by the way' section is for use in FAQs in particular. It contains interesting or useful information that is not directly relevant to answering the question posed at the beginning of the article.
Tell us what you think (English).
Content first published xxxYYYY-MM-DD. Last substantive update xxxYYYY-MM-DD HH:MM GMT. This version xxxYYYY-MM-DD HH:MM GMT
For the history of document changes, search for xxxsearch-string in the i18n blog.
Copyright © xxxYYYY W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.
New resources
@webi18n