Generated Text NormanWalsh Sunday, 08 Apr 2001 XSLTUK-01 08 Apr - 09 Apr 2001 Keble College, Oxford, UK 1 Version TEST 2001 Sun Microsystems, Inc. Say something pithy in the introduction This is the introductory slide This is on the foilgroup slide. Remember to describe the use-caess Semantic markup often omits text that can be generated automatically Different contexts require different generated text, naturally Generated text is locale-specific An obvious, common example is chapter title markup. Consider: <chapter label="3"><title>Some Title</title> ... The title page for a chapter varies by location: English: Chapter 3. Some Title French: Chapitre 3. Some Title Replace this

]]> ]]> ]]>

]]> with this

]]> Chapter ]]>]]> ]]>]]>

]]> L10N Data Where the generated text for words like Chapter is taken from an independently maintained lookup table: ... ...]]> Single-word localization (doesn't support Japanese) Hard-coded presentation elements (number and title) Hard-coded presentation order (gentext, number, title) Hard-coded number format Use a lookup function to determine the markup template in addition to the keywords. For example, the markup template lookup table for a chapter title looks something like this: LocalizationTemplate Returned EnglishChapter %n. %t FrenchChapitre %n. %t The markers, %n, %t, and %s (not shown) are replaced by the lable, title, and subtitle of the component, respectively. Find the template and fill it in: ]]> L10N Data In order to make this work, the localization data is extended: ... ]]>