Hi Dave et al,
I haven't tried emails etc. But at least it starts in French now with "A partir de" for the prices. So some stuff definitely got translated.
What is somewhat confusing to me is the way the language has found itself in templates that are then no longer accessible in resx files. This hides them from resource editors. Xml to me sounds like "configuration" which is separate from "templates" for me as the latter usually go to resource files. The huge advantage of resource files is that the cascading mechanism for getting the language of choice is already taken care of. Plus: you can leverage the core installer and future language distribution system (which as you may know I'm working on). Thoughts?
Alternatively I've developed a system to use resx files in templates. If you look at the codebase of DNNBlog (the new blog6 branch) you'll find a folder "templating" with a "resource" class which does this. It implements IPropertyAccess and takes a resource file as an argument. This is an alternative which allows the user to preserve the structure of the template throughout all languages. The drawback is that it doesn't allow for the variations of "User X did Y" to "Y werd door X gedaan". This is where the order of texts gets changed per language.
Best,
Peter
I haven't tried emails etc. But at least it starts in French now with "A partir de" for the prices. So some stuff definitely got translated.
What is somewhat confusing to me is the way the language has found itself in templates that are then no longer accessible in resx files. This hides them from resource editors. Xml to me sounds like "configuration" which is separate from "templates" for me as the latter usually go to resource files. The huge advantage of resource files is that the cascading mechanism for getting the language of choice is already taken care of. Plus: you can leverage the core installer and future language distribution system (which as you may know I'm working on). Thoughts?
Alternatively I've developed a system to use resx files in templates. If you look at the codebase of DNNBlog (the new blog6 branch) you'll find a folder "templating" with a "resource" class which does this. It implements IPropertyAccess and takes a resource file as an argument. This is an alternative which allows the user to preserve the structure of the template throughout all languages. The drawback is that it doesn't allow for the variations of "User X did Y" to "Y werd door X gedaan". This is where the order of texts gets changed per language.
Best,
Peter