First let me say, that you did a great job, preparing AS for translation to another language, but I have a few issues:

1. I can´t figure out how to translate popup messages. There is no template and nothing in the ressource files. There are other posts in this forum related to this, but unfortunately no (correct) answer.
2. When I use the token [AS:CONTROL:SENDTO] (like in Template MessageCompose), I get an AJAX enabled search textbox, which works great, but I have no chance to translate the words "type in search term". Also this template uses two asp:Dropdownlists with the words "*DefinedUser(s)" and "*Select Group(s)" as default values. (see attached image). Do I have a chance to localize these words ?
3. In a few controls I have an encoding issue. When users type in special german characters like ä,ü,ö or ß (like in my lastname under my avatar on the left ;-) the typed in words are later displayed incorrectly on other forms.

David

No one on this one ?
Espacially popup messages in local language are important for me, since the only option would be to deactivate popup notifacations on my site. Unfortunately my customer insists on this feature :-/

David

Hi David,
Sorry for the delay. We will have the localization strings fixed for Active Social 1.9. I've added this item to our tracker.
http://www.activemodules.com/active...messaging/

Will,

I really appreciate your effort in this case. I already installed your new version and I can confirm that all resources in the messaging subsystem are now configurable with resource files.Thanks !!
Unfortunately there are still some popup notifications which are still not translatable. (Resource keys, starting with RESX:Notifications) You can find an example popup notification attached to this post.

David

Hi David, I have a question for you!

It seems that we are about to start a aproject very similar to what you just did (or about to complete) .  In our case we plan to translate AS in French, totally, including pop-ups and every hidden corners or pop-up...

what would be your estimate (in terms of hours) for such a project? that would be helpful for us...

Thank you in advance,

François

Hi David,

Your post and this exchange with Will is very useful thank you. 

I have a question related to this for you (both of you actually).  I'm about to get my own AS and I need to plan for a complete translation in French.  Just like you did David (in german in your case), I will need to reach each and every strings of text including the pop-ups... 

• what would be a fair estimate of such a translation task (high and low...  it don't have to be that precise...)
  • right now my estimate could be about 20-40 hours of pure translation job with an additional 10 to 20 hours of review and making sure that we addressed contextual sense and meaning.

Your advices and suggesitons would be very helpful!

Thank you in advance

François

Hi François,

well it's not easy to estimate, but if i had to start translation from scratch I would estimate closer to 40 hours.Reviewing is a must and takes additional time. You (Better: a QA team) must ckeck all translations by going through each use case of AS. And believe me, it´s look and feel is quite simple but under the hood there are lots of forms ;-)
You must take design work into account because you need more white space in our languages. I did not start my translation from scratch. I would check the french dnn Community sites. Probably someone already translated AS to french.

David

Posted By David Voß on 17 Jan 2011 06:01 PM
Will,

I really appreciate your effort in this case. I already installed your new version and I can confirm that all resources in the messaging subsystem are now configurable with resource files.Thanks !!
Unfortunately there are still some popup notifications which are still not translatable. (Resource keys, starting with RESX:Notifications) You can find an example popup notification attached to this post.

David

David,
Those items can be translated.  Here are the keys:
[RESX:NewMessage]
[RESX:NewMessages]
[RESX:Alert]
[RESX:Alerts]

Hi Will,

that was my first try ;-)

I´m not going to bother you if I am not sure that something is not working as it should :-)

I translated those resource keys right in the beginning , but I assume that these keys are only used for regular messages somewhere in your modules (welcome center for instance). I studied your ressource file closer and found some RESX:Notifications entries. It came out that [RESX:Notifications].Text stands for the header of the popup messages, but all other strings are not localized.

Yours,
David

Thank you David, these are great advices and suggestions.

I will check and continue my evaluation and report back since it might be helpful to a few of us...

Please feel free to add any additional remarks :-)

Take care

François

Will,

time is flying, my project is supposed to be online at the 1st of march.
I dig a little deeper into this popup issue and found the MessagePopup.ascx file in the templates/Other Folder. This is it´s content:


..hmmm, how to paste html code here ? please check the jpg instead...


As one can see here, there is only the title translated through ressource files. I guess the rest of the popup message will be dynamically inserted through some CodeBehind in your dll. Probably this piece of code doesn´t use ressources correctly.

Could you please double check this by searching in your code (look for id asNotifierText) , Thanks !

David

Update:
I took the EN Ressource file and translated the approp. values in this file. Voila, my popups are in german language now.

Conclusion:
- you are using ressources in your code, which is good ;-)
- for some reason AS is loading the wrong resource file with popups.
- there is probably a bug in your GetInbox Method of cbhandler class.

For now I have a workaround but it would be interesting to investigate this behaviour further....

David