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/22/2010 10:35 AM
 
Marc, please log enhancement requests to support.dotnetnuke.com,not codeplex. As to your idea I think it's good, i suggested something similar before and the 2 suggestions that came up were to create a static language searcher (to avoid it iterating all resx files it would only iterate cache copies) or to alter the[L] to become a link to the language editor passing in a querystring value of the resx file and update the language editor to select the relevant tree node.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
11/23/2010 9:12 AM
 
Sebastian Leupold wrote:
 Maybe we should provide a list of these resource files - what do you think, would this be helpful?

 I had made such a list for myself.

Under DNN 5.4, I had a translater translating to a portal0 resouce file. I then had a windows forms app that went through all the portal0 resource files and copied its entries to the host resource file, at which point the translation became available to all portals. I made a list like that, but once it was clear where to find those files, I switched my approach and scanned the appropriate folders for resource files, keeping a list of resource files to exclude from the process.

This is not really the problem. Too much of DNN is built around developpers experience, rather than around user experience. All elements are grouped around developers concepts, not where the user would want to use it. Your suggestion to work with two windows, one for the resource editor and one for the output was a good one, and I will try it, but it is very much a work-around, and linking a text to its resource would be much better in terms of user experience.

I was contemplating making a document connecting each key for a static label in the resource file to a screen shot of where it applies. When finished, I would reorganize the screenshots with their keys into a logical system for the translator. But I think the tool tip idea is better.

Ask you marketing department: the more translations, the bigger the potential market. There will never be a large group of users involved in translation, therefore, as such, translation will not be a popular improvement. But as every new translation opens a new potential market, it should be a priority for your marketing.

Also, think of the other concept for translation: the idea is to translate that 20% of the entries that account for 80% of the occurences... Think of solutions that facilitate this approach.

This solution would not solve all problems. Indeed, for error messages, we may have to come up with a different idea. Idem for emails etc. You would still have to go through the resource files. But error messages and emails offer a little more clues as to what they relate to.


____________________________________
The one-eyed in the land of the blind.
 
New Post
11/23/2010 10:15 AM
 
cathal connolly wrote:
Marc, please log enhancement requests to support.dotnetnuke.com,not codeplex. 
done! http://support.dotnetnuke.com/issue/V...

After I posted on codeplex, it came to me that - if you are able to insert a tooltip, you might just as wel create a popup that allows translation on the fly. It's similar to your idea, no? Would that not be too much user friendliness all at once for DNN? ;-)

____________________________________
The one-eyed in the land of the blind.
 
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