Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...register locationregister location
Previous
 
Next
New Post
11/18/2010 12:24 PM
 
ha, once again Sebastian is faster than me, i don't know why i bother :)

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
11/18/2010 12:26 PM
 
lol :)

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/18/2010 4:04 PM
 
Thank you both for the help. Just a little correction on the location for DNN5... I found it in:

\desktopmodules\Admin\Security\App_LocalResources\ManageUsers.ascx.resx

Have a good day!
 
New Post
11/22/2010 12:20 AM
 
I've tried to add a suggestion to codeplex, but I don't know if it will be very popular.

The suggestion is to give each localizable static label a tool tip with the name of the resource file and the key. This popup should be enabled for translators and/or admins.

Somewhere in the rendering process of localized text it should be possible to add that tool tip for the translators.

If you are translating to create language packs for distribution, you may want to go through each key of each resource file. But if there are no language packs for your language and you want to make your portal ML, you may want to follow a different translation strategy. You would typically start with the occurences that all visitors are confronted with (login, register, copyright, privacy, terms of use, registration page etc...) You would then have a look at the occurences that all registered users are confronted with, then those for editors. Some keys would probably never be translated. Once the site is running, who does still need the error messages during installation process?

For this kind of translation strategy, DNN shows little sympathy. It is also true for the administrator that wants to change the formulation of one bit of text on his site. He can use the localization pack, but which resource file, and which key?

For an outstander, it would seem like an easy-to-implement extension, but then of course, I have no idea of the complexity of the DNN undertaking.

____________________________________
The one-eyed in the land of the blind.
 
New Post
11/22/2010 5:24 AM
 
I agree that the structure of language keys mainly follows technical aspects, which doesn't make it easy for translators - and i agree, that the language editor needs some love. Though I understand your approach, my ideal is translating all keys from the surface including errors that may occur - which can hardly be found when running the module. With some understanding of the structure of the DNN website, you may identify primary resource files, those exposed to visitors and ordinary users, which need to be translated first. Maybe we should provide a list of these resource files - what do you think, would this be helpful?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Language and In...Language and In...register locationregister location


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out