About hard-coded text in TC/TE

About hard-coded text in TC/TE

This question is not answered

Dear Telligent,

With new releases of Telligent.Community and Telligent.Enterprise we still have lots of issues with hard-coded text resources. As a result it takes a lot of efforts to do localization of these great products. While there is this adhoc process to find such bugs, we decided to approach this issue with more systematical way.

Speaking generally there could be a few hard-coded text cases that include:

  1.    
    1. Text in between html tags in aspx code e.g. <p>Blah-Blah</p>
    2. Text attribute values in aspx code e.g. <CSControl Text="Blah-Blah"/>
    3. Strings in javascript code that eventually being presented to the user e.g var a = "Do you speak English?"
    4. Strings in C# code that being presented to the user e.g. throw new CSException(CSExceptionType.BlogFileQuotaExceeded, "The size of this blog file exceeds the maximum limit for this site.");

 

You can read the rest of method description here, I just post here our findings.

At this point in both Telligent.Community and Telligent.Enterprise there are  about 463 hard-coded text strings which need to be fixed. For the future builds/service packs I think it make sense for you guys to implement some automated method to check for such issues. And the last thing. For us, being a partner with Telligent which works in non-English speaking region is crucial to have language-independent products to sell.

I sincerely hope issues I mentioned in this post will get a priority for you. 3108.to_localize.zip

 

All Replies
  • Thanks for the detailed information.  I can assure you this is something we'll be taking VERY seriously and are looking into for the first service pack release.  

    Josh Ledgard - Vice President of Engineering - Telligent

  • Thanks for reply, Josh. Do you have any ETA for this service pack? I think you do understand that for non-English customers the only way to use Telligent Community or Telligent Enterprise is get somebody who can fix those 460+ bugs with multi-language support. We have customers who postponed decision to buy licenses until that, because they expect OOTB experience with new Telligent products and do not want to spend additional money to fix issues I mentioned.

  • I'm sorry that I do not have a date I can share publicly for the first service pack.  We're still collecting feedback like this to be included in the release as well as working on the SP itself.  

    Josh Ledgard - Vice President of Engineering - Telligent