Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

AspDotNetStoreFront
  Ads  
Biz Modules provides professional business modules and solutions for DotNetNuke
 


  Sponsors  

Meet Our Sponsors

The best choice for your web site host, email hosting, and domain registration.
CrystalTech Web Hosting™
Webhost4life, specialists in DNN hosting
Mad Development is a full service interactive agency focusing on the merge of design, technology, e-commerce, and affiliate marketing by providing total website solutions.
AspDotNetStoreFront - E-Commerce by Design - The Leading ASP.NET shopping cart platform for developers!
SteadyRain
 


DotNetNuke Forums
 
  Forum  DotNetNuke® Pro...  Language Packs ...  Module Localizer
Previous Previous
 
Next Next
New Post 1/13/2006 4:26 AM
User is offline Vicenç Masanas
1402 posts
www.disgrafic.com
6th Ranked








Re: Module Localizer 
Jessy (it's that your name?),
I see you point, but again:
- we cannot rely on any external services for translation: this will tied dnn to a specific provider and this is completely oposite of what we want. Even if we got it configurable and independent from the translation provider, we cannot base it on a third party resource.
- when developing modules you usually use vs.net which cames with a wonderfull editor for xml files. So I still don't see any advantage on your option. And saying that it will handle 50% of the work...I think you're quite optimist... We usually then to use "compact" control names (say "lblUserName") but the actual next in most cases is not the same as the control name (say "Enter the user name").

You can think this as separate helper for translators or module developers but I don't really see this being added onto the core. If it works for you great! I (as a developer) for myself wouldn't use that approach (automatically adding resx keys) since I don't like that approach. I prefer to control the whole process when I'm creating the module on vs.net, and not having to go to the run the app in order to have the keys added.


Disgrafic.com
 
New Post 1/16/2006 3:15 AM
User is offline Aricie
112 posts
www.aricie.com
9th Ranked






Re: Module Localizer 

Ok, I understand you point of view, nevermind.

Anyway, the module is there for those who want to try it.

Cheers


Jesse
www.aricie.com
www.aricie.net

 
New Post 12/24/2006 7:49 AM
User is offline Jonathan Palmer
31 posts
www.wcs.org
10th Ranked


Re: Module Localizer 

We have a database with around 80 tables, each table with around 5 different ascx controls.  We want to create a database based data dictionary for these terms so that we can automatically create resources files in different languages based on:

i) The English resource files we have created.

ii) The data dictionary

A great solution for DNN would be an automated translation that works by using an internal data dictionary (as above). 

A second phase of this project could be the facility to use a "Translator Provider" to populate (translate) terms in the dictionary that were currently without translations.

We may have some funds to implement this and it would be great to do this in a way that feeds back into the core. 

Would either of you be able to estimate the work involved here?

 
New Post 12/28/2006 2:05 AM
User is offline Jonathan Palmer
31 posts
www.wcs.org
10th Ranked


Re: Module Localizer 

I realize I posted this over the Holiday Season.  Were there any thoughts/comments on this?

 

 palmernet wrote

We have a database with around 80 tables, each table with around 5 different ascx controls.  We want to create a database based data dictionary for these terms so that we can automatically create resources files in different languages based on:

i) The English resource files we have created.

ii) The data dictionary

A great solution for DNN would be an automated translation that works by using an internal data dictionary (as above). 

A second phase of this project could be the facility to use a "Translator Provider" to populate (translate) terms in the dictionary that were currently without translations.

We may have some funds to implement this and it would be great to do this in a way that feeds back into the core. 

Would either of you be able to estimate the work involved here?

 
New Post 12/28/2006 3:16 AM
User is offline Aricie
112 posts
www.aricie.com
9th Ranked






Re: Module Localizer 
Modified By Aricie  on 12/28/2006 6:18:17 AM)

Hi,

as far as I understand, you're looking for a resource file maker in the form of a module with an engine that binds to a translation dictionary in the database.

Vicenç can probably confirm that, but I don't think that's what the next steps of dnn loclization will aim for, since content localization and validation workflow will rather base on duplicating the structured data through foreign keys than tapping into a non structured data source.

On the other hand, such an engine is pretty much what our module does, except than it taps into a translation web service rather than a dictionary table.

Can you precise the kind of interface you'd like to see?

Maybe something like:

  • An alphabetical view grid / tree view for browsing the dictionary
  • An edit form for adding / editing translation entries
  • A form to configure / launch the engine that creates / updates the resource file

 just a few days of programming it seems to me.


Jesse
www.aricie.com
www.aricie.net

 
Previous Previous
 
Next Next
  Forum  DotNetNuke® Pro...  Language Packs ...  Module Localizer
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

 


DNNMasters - modules, consulting, development
DNNMasters developers are involved in DNN development since DNN 1.0.9 and today we offer a broad range of DNN related products and services including custom development of modules, help with ing third party modules for specific needs, general DNN technical support and administrative services.
www.dnnmasters.com
Cygnusoft Custom Software
Cygnusoft has been providing cutting-edge custom software solutions for 20 years. Cygnusoft is also a leading start-up incubator, helping our partners build successful new businesses.
www.cygnusoft.com
Digicon: DotNetNuke design and development
Digicon is based in Brisbane, Queensland, Australia
digicon.com.au

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP