6) Replace “hardcoded” text with dictionary calls.

How-to
How to create multilingual sites with only a single navigation-tree, > using 'tabbed translation' and the dictionary.

Chapters

• Chapter 1: Summary of the Multilingual 1:1 site system
• Chapter 2: 1) Create languages
• Chapter 3: 2) Add language tabs to document types
• Chapter 4: 3) XSLT library function
• Chapter 5: 4) Alter all field references
• Chapter 6: 5) Use the dictionary with an XSLT extension
• Chapter 7: 6) Replace “hardcoded” text with dictionary calls.
• Chapter 8: 7) Adding language-selector - You're done!

6) Replace “hardcoded” text with dictionary calls.

Now, we can add this extension in all XSLT files where we need dictionary translations.

First we need to add the namespace declaration in the stylesheet element:

<xsl:stylesheet
    version="1.0"
    xmlns:xsl=http://www.w3.org/1999/XSL/Transform
    xmlns:msxml="urn:schemas-microsoft-com:xslt"
    xmlns:umbraco.library="urn:umbraco.library"
    xmlns:kv_trans ="urn:kv_trans"
    exclude-result-prefixes="msxml umbraco.library kv_trans">
...  

(The added code is highlighted.)

Then we can use it this way anywhere in our XSLT file:

<xsl:value-of select="kv_trans:translate('KEY',string($dlang))" />

Where the ‘KEY’ is the dictionary key for the entry, as explained in step 5.

Again, change the namespace and aliasname to what you used above, in step 5.