This document is a mockup to illustrate the concept of overlays/templates interacting with the i18n techniques document.
This document is an editors' copy that has no official standing.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this series of documents is maintained at the W3C.
This is only a mockup and has no value other than to illustrate a concept. Note that this is the very first exploration of these ideas, so there are likely to be many issues, and the end result is likely to be substantially different.
The (red) xml code you see exposes possible underlying xml for the purpose of making this illustration clearer. Note that this document DOES NOT represent what an overlay/template would actually look like, but presents to you a picture to help you grasp the concept. It needs explaining.
mode attribute on the
include-text elements helps the associated xsl file choose the appropriate information from the node pointed to by the value of the
id attribute. (Maybe
id should be replaced with a
path attribute that uses xpath expressions as its value.?) In this example, assume perhaps the following results for mode settings:
technique: extracts the rule and description, but nothing else
rule: extracts the rule only
source: extracts the resources items relating to sources only, and filters out duplicates.
Note that the order of the first two sections is different from that in the current i18n techniques master xml file, and so is the order of the techniques information in section 2. Also, of course, only a few select techniques have been drawn on.
Note also that the same information items extracted multiple times from the master file to appear in this document.
This can help choose the appropriate styling and screen reader voice, etc.<include-text desc="declare in html" document="html-tech.xml" id="ri20030115.105511247" path="." mode="technique"/>
It is very important to declare the character encoding used in your document, otherwise there is no guarrantee that the reader will see sensible stuff. [note that the xsl file associated with this may be set up to not extract resource information
<include-text desc="use the meta statement" document="html-tech.xml" id="ri20030115.105511247" path="." mode="technique"/>
<include-text desc="use meta statements as early as poss" document="html-tech.xml" id="ri20030115.105725169" path="." mode="technique"/>
<include-text desc="use ascii at top of file" document="html-tech.xml" id="ri20030115.105837934" path="." mode="technique"/>