- markup (52)
- xml (7)
- xslt (21)
- atom (8)
- overlapping markup (2)
- schema (9)
- creole (4)
- xforms (1)
- pipelines (7)
- coding (2)
- dtll (1)
- genealogy (3)
- gtd (1)
- hardware (1)
- legislation (1)
- ontologies (2)
- unicode (1)
- web (24)
- google (3)
- rdf (6)
- rest (3)
- wikis (1)
- work (1)
- xpath (1)
- xquery (1)
- xtech2008 (3)
- life (26)
- children (5)
- equality (6)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (7)
- xtech (6)
- blog (7)
- drupal (3)
Re: Big XSLT applications just got easier to manage
Jeni isn’t talking about standalone modules.
Let me give an example. We want to do l16n of a web form. Generally the structure is going to be all the same, but the labels will be different. So we abstract the shared elements into a separate module that will be imported by the individual localised XSL components. E.g.
layout.xsl:
<dl> <dt><xsl:call-template name='name.label'/></dt> <dd><input type='text' name='name'/></dd> <dt><xsl:call-template name='email.label'/></dt> <dd><input type='text' name='email'/></dd> </dl>form_en.xsl:
form_fr.xsl:
Then you just process using whichever version of form.xsl best fits the locale. layout.xsl isn’t a standalone module, but you still need to edit it.