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...Localisation problem in 4.6.0Localisation problem in 4.6.0
Previous
 
Next
New Post
9/19/2007 7:35 AM
 

Hi,

I translate for you a topics post in dotenetnuke.fr, community of French users of dnn.

 
The “reason to be” of our community is to share localised resources for using DotNetNuke in our prefered language. In our case, French.

We know that a new release come usually with some localisation bug and we know also that those bug impact in the skinning of our website.

But this time, it seem that the Core Team goes to far… I’m talking about the “AuthentificationServices”. Does somebody can explain me why you choose to force the placement of the form in a 160 px width tabs? That’s not a big problem for us but tell me why you put a input cell just next the button???

 In the new authentification module that’s coming with the release 4.6.0 you put the password in the same line of the “login” button. There is no problem with your website when you use english as default language but when you translate “Login” by “Connexion” the word “Connexion” is too long and the “Login” button goe’s to the next line…

It was easier to fix the width of the “password input” in the same value of the “username” and put the “damned” button just under it… No????

 The solution? Modify the “DesktopModules\AuthentificationServices\DNN\Login.ascx” and change the structure of the tab or modify the CSS value linked to the button and then add a value to your stylesheet for not impacting all the button of the website (cssclass= “StandardButton” by default).

 And everybody know that’s NOT THE SOLUTION to modify the code because when you upgrading your instance of DNN everything is susceptible to change again and again.

 So, Mister of the Core Team, don’t forget the localisation in your futur release and, please, correct this bug for making our website more efficient.

 
Appologies to all of you for my English translation. Thank’s.

 
New Post
10/10/2007 10:05 AM
 

This was a minor issue tough, and the bitterness of this post does not reflect the true feelings of the poster. I have suggested in the french forums that this kind of translation should  keep the facts, and leave out  attempts to translate  humour or irony from the original message. Feelings are difficult to render in another language.

Moreover, forums are not the right place to report issues - it has been said many times.

I apologize for the unecessary and unfriendly comments in the message above, which are not those of our user group.

 

  


Benoît Sarton
www.bsi.fr
www.dotnetnuke.fr
 
New Post
10/10/2007 10:08 AM
 

Benoît,

thank you for this clarification.


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...Localisation problem in 4.6.0Localisation problem in 4.6.0


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