| Surjeet Gill wrote
I was creating localization package for Punjabi (pa-IN) language and found "Home.Text" is in the SharedResources.resx but not used when rendering the page. Is this a bug?
I will appreciate if someone shed light on this and also how to localize user added Menu items?
I also appreciate if some one point me "How to create DNN localization package?" and sequence of steps required.
|
Dear Surjeet,
Answers to your questions:
1. I wasn't able to find where the "Home.Text" resource text is rendered. I have also checked the whole DNN source package, but didn't find a reference to this resource.
@ Sebastian: I did look thoroughly ;-) And when I use the Resource Files Verifier it does not inform any "obsolete entries" for the SharedResources.resx file. Question: ¿How does the Resource Verifier check if an entry is obsolete?
2. Sebastian pointed you to third parties solutions when it comes to localize Menu Items and Dynamic Site Content. I am quoting Sebastian's recommendations below:
For ML Module Content you need ML Modules like:
- free MLHTML from Apollo SW (www.apollo-software.nl)
- free MagicContent from DNN Forge (www.codeplex.com/MagicContent)
For ML Menus you need a Page Localization Solution like:
- free EALO from DNN Forge (www.codeplex.com/ealo)
- DSLocalizator from Locopon (dnn.tiendaboliviana.com)
- PageLocalization from Apollo SW (www.apollo-software.nl)
3. You will find a good tutorial, from Vicenç Masanas, at this Blog entry. It is the first of a good series.
HTH.
Meltoner wrote
But how is it possible ??? something so Basic (page names and titles in multiple languages) and needed implementation hasnt been implemented in the core framework of dot net nuke.... it just doesnt make any sense...
|
The core and modules of DotNetNuke do include localization features, but only for Static Text Resources. All administration menus, options, settings and messages can be localized just by installing a Language Pack.
ML support for Dynamic Text (such as Page Names, Titles and Content) is not such an easy issue to resolve. There are many approaches to this problem and as you may find listed above, there are enough links available for you to check. Some of them are even free, and AFAIK they do perform fine.
The request for including a fully ML capability to the core (and modules) of DotNetNuke has been an always returning issue on this forum and is receiving special attention by the Core Dev Team.
I am a native Spanish speaker, and my first reaction to this issue was also of impatience. However, the DotNetNuke community and the Core Dev Team are among the most participative and supportive communities around and this is a major advantage when it comes to choose a development platform for WCMSs works.
DotNetNuke is under constant development and evolution, and has the most frequent releases for updates and improvements, AFAIK.
Please remain confident that this tool will eventually meet all your needs.
Saludos,
Alejandro