To determine the feasibility of integrating the translation/i18n functionality, an investigation must be conducted #4
Description
One major aspect of ZPT which ZptSharp has yet to implement is the internationalisation (AKA i18n) functionality. The intention of this is to provide a first-class mechanism by which markup indicating translation may be integrated directly into the template files. The actual translation should then occur automatically using 'infrastructure' which is part of the underlying application framework.
This is a 'spike' ticket to conduct an investigation into this functionality and devise a plan to proceed (or not). Questions which need to be answered are:
- What functionality does the ZPT spec for i18n provide?
- How could this integrate with dotnet resources & satellite assemblies (which is the standard way of doing i18n in dotnet)?
- Can those two separate functionalities 'line up' with one another?
- What the realistic next steps should be, toward implementing this logic
The original documentation to this functionality has since become a dead link, but there's some replacement documentation on the Chameleon website which should be suitable.
What we know so far
This is the i18n namespace of attributes, operating in a similar manner to TAL and METAL attributes.