so it makes it easy to implement your own country page.
</p>
<p>
<!--p>
<imgsrc="/graphics/icons/warning.png"/>
The first system we have used, an attribute consisting of
comma-separated values, was not very adapted to the way we generate
dynamic information.
Therefore, we have opted for the hereunder defined system, a more
xml-style one.
</p>
</p-->
<h2>Basic instructions</h2>
<p>
A tag should be in <ahref="https://en.wikipedia.org/wiki/CamelCase">CamelCase</a> except for special tags like <code>front-page</code>, <code>newsletter</code>. So for instance, the tag “very important subject” should be <code>VeryImportantSubject</code>.
A tag should contain a <code>content</code> attribute except for special tags. This attribute should be translated and human readable, because it will be shown on certain pages. For instance, if you tag a page about the Windows Tax:
A tag should contain a <code>content</code> attribute except for special tags. <bold>This attribute should be translated and human readable</bold>, because it will be shown on certain pages. For instance, if you tag a page about the Windows Tax and about a ruling:
<p>In order to retrieve news items or events with a given tag, these
have of course to be tagged accordingly. To do that, add as many
<var><tag content="">...</tag></var> as necessary in the tags section.</p>
<h2>Tag pages, news and events</h2>
<p>For most pages (when your file has the <var>xhtml</var>), the tags must be added within <html></html> usually at the end.</p>
<p>
A list of tags currently in use can be found <ahref="/tags/tags.html">here</a>.
We also have a list of <ahref="/tags/tagged.html">all tagged pages, events and news</a>. <strong>Please check these pages first</strong> to avoid making duplicated tags, use existing tags if possible to keep things consistent.
</p>
<ul>
<li>For news items and newsletters, within <html></html> if your file has the <var>xhtml</var> extension:</li>
