Localization not working??

Posted by Community Admin on 04-Aug-2018 08:27

Localization not working??

All Replies

Posted by Community Admin on 19-Apr-2011 00:00

Look at this screencast


a) English seems to be missing (would be have to import english as well)
b) even though german is there it still shows english in page


Posted by Community Admin on 19-Apr-2011 00:00

It might has been a chaching issue, because now I see the translations.

However, Importing French results in error.


Posted by Community Admin on 20-Apr-2011 00:00

Hi Markus ,

Issue is fixed. You can get fixed localization from http://www.sitefinity.com/marketplace/localizations/details/backend-localization-french.aspx
Please check that the xlsx file in the archive has today's version, because browsers tends to cache and it may trick you by saving the old zip.

All the best,
the Telerik team

Posted by Community Admin on 21-Apr-2011 00:00

Dear Telerik

Yes the import of the french now worked.

a) could it be that some stuff of the UI is cached. Switching a languae in profile translates some stuff imediately other stuff seems to be translated later

b) I thinks this is one of the big things for end user in 4.1 which is realy nice to have now. Since you know how much time it took to translate this into other languages (8000 lines), you can imagine how little sense it would have made that very user would have to do this again and again.

So a big thanks for including this in 4.1.

c) next moves
 1) Include the languages by default maybe (they are small so why not)
  2) Add radspell .tdf for all supported languages
  3) Add all radspell options to radeditor out of the box (maybe set EN default) or Administration - Advanced settings

So thanks for all the work and making SF better and better. 4.1 is finally a product we can use and sell. Looking forward to an exiting 2011 and many features to come, or make a comeback.


Posted by Community Admin on 27-Apr-2011 00:00

Hello Markus Berchtold,

We are glad that you are noticing improvements in that area. Most probably it's caching issue as you suggested. We further look to optimize this.

Kind regards,
the Telerik team

This thread is closed