Hi,
We are creating a new Finnish language pack following the instructions in Telerik's documentation (1, 2). The English localization files were copied from App_GlobalResources on the installation folder.
The (so far) localized strings works fine on the editor UI but not so well on the Image manager. Note that the image manager strings were not yet localized, so the original English values should be shown (from our localized fi-FI files). Instead, we get an error. For instance, all the top menubar buttons on the left pane of the image manager shows 'Not loaded (error)' as well as the Filename and Size column headers. Though, on the Preview pane the localization works fine for the top menubar. On the 'Properties' tab, only the 'Long Description' and Image alignment' labels shows as 'Not loaded (error)', while all the other labels are localized (currently in English).
Telerik's dll version is 2009.2.826.35
We also use the web.config Globalization , where we define our own resource provider factory that retrieves localization strings from database for the application. Could that be the problem?! But then again, on the main editor UI the localized strings works fine.
Any ideas would be highly appreciated.
Eyal
UPDATE: The issue seems to derive from the conflict with the ResourceProviderFactory that is defined in web.config. When I remove the ResourceProviderFactory and instead retrieve the application strings from a local resource file, the image manager shows all localization strings correctly. I think it may be worthwhile to check this resources' conflict more thoroughly, because in some projects it is required to use resources retrieved from database.
We are creating a new Finnish language pack following the instructions in Telerik's documentation (1, 2). The English localization files were copied from App_GlobalResources on the installation folder.
The (so far) localized strings works fine on the editor UI but not so well on the Image manager. Note that the image manager strings were not yet localized, so the original English values should be shown (from our localized fi-FI files). Instead, we get an error. For instance, all the top menubar buttons on the left pane of the image manager shows 'Not loaded (error)' as well as the Filename and Size column headers. Though, on the Preview pane the localization works fine for the top menubar. On the 'Properties' tab, only the 'Long Description' and Image alignment' labels shows as 'Not loaded (error)', while all the other labels are localized (currently in English).
Telerik's dll version is 2009.2.826.35
We also use the web.config Globalization , where we define our own resource provider factory that retrieves localization strings from database for the application. Could that be the problem?! But then again, on the main editor UI the localized strings works fine.
Any ideas would be highly appreciated.
Eyal
UPDATE: The issue seems to derive from the conflict with the ResourceProviderFactory that is defined in web.config. When I remove the ResourceProviderFactory and instead retrieve the application strings from a local resource file, the image manager shows all localization strings correctly. I think it may be worthwhile to check this resources' conflict more thoroughly, because in some projects it is required to use resources retrieved from database.
14 Answers, 1 is accepted
0
Hi Eyal,
To fix the problem put the resx files in another folder and set the LocalizationPath property to point to it. Therefore the editor will load the resx files using its own provider and wont use the .NET ResourceProviderFactory provider.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
To fix the problem put the resx files in another folder and set the LocalizationPath property to point to it. Therefore the editor will load the resx files using its own provider and wont use the .NET ResourceProviderFactory provider.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
eyal
Top achievements
Rank 1
answered on 07 Oct 2009, 07:34 AM
Thanks for the reply!
Just to make sure - do you mean relocating the editor's resx files from the ASP.NET App_GlobalResources folder into a normal folder?
Eyal
Just to make sure - do you mean relocating the editor's resx files from the ASP.NET App_GlobalResources folder into a normal folder?
Eyal
0
Hello Eyal,
This is the general idea behind the LocalizationPath property - if you are using a custom localization provider and the editor cannot display its resources from the App_GlobalResources folder. It tells the editor to load the .resx files like normal XML documents and read the strings directly, which bypasses the localization provider and will work in all scenarios.
Kind regards,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
This is the general idea behind the LocalizationPath property - if you are using a custom localization provider and the editor cannot display its resources from the App_GlobalResources folder. It tells the editor to load the .resx files like normal XML documents and read the strings directly, which bypasses the localization provider and will work in all scenarios.
Kind regards,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
eyal
Top achievements
Rank 1
answered on 27 Oct 2009, 07:30 AM
Hi again.
So I located all the localization .resx files in another folder, set the editor's LocalizationPath property to point to this folder, and ... almost all the localization strings are shown as expected. But not all.
As you can see in the attached screenshot, all the strings on the left pane of the image manager are not found as well as two strings on the image properties tab. If I insert an image and right-click to show its properties, all strings are in place. All the other dialogs that I have tested so far works well (incl. table wizard and hyperlink manager). We are currently not using document or flash manager so I did not test them.
In fact, your solution works well in another project. In this project however, we use the Resource Provider Factory (defined in web.config). can it still have conflicts with the editor resources?
Thanks for your assistance.
eyal
Off-topic - I clicked on the "Unmark answer" of your last reply but nothing happened. The forum page was loaded showing the title of the post. that's it. Loading the post again, I realized that the answer is still marked.
So I located all the localization .resx files in another folder, set the editor's LocalizationPath property to point to this folder, and ... almost all the localization strings are shown as expected. But not all.
As you can see in the attached screenshot, all the strings on the left pane of the image manager are not found as well as two strings on the image properties tab. If I insert an image and right-click to show its properties, all strings are in place. All the other dialogs that I have tested so far works well (incl. table wizard and hyperlink manager). We are currently not using document or flash manager so I did not test them.
In fact, your solution works well in another project. In this project however, we use the Resource Provider Factory (defined in web.config). can it still have conflicts with the editor resources?
Thanks for your assistance.
eyal
Off-topic - I clicked on the "Unmark answer" of your last reply but nothing happened. The forum page was loaded showing the title of the post. that's it. Loading the post again, I realized that the answer is still marked.
0
Hi Eyal,
I can see that the upcoming RadControls Q3 2009 release has a fix for the LocalizationPath property and file browser dialogs. The symptoms are the same as what you see (file explorer is not localized while the rest of the editor dialogs work as expected). The release should be available a week. I apologize for the inconvenience this has caused you.
Greetings,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
I can see that the upcoming RadControls Q3 2009 release has a fix for the LocalizationPath property and file browser dialogs. The symptoms are the same as what you see (file explorer is not localized while the rest of the editor dialogs work as expected). The release should be available a week. I apologize for the inconvenience this has caused you.
Greetings,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
eyal
Top achievements
Rank 1
answered on 30 Oct 2009, 07:29 AM
Thanks for your answer.
The bug affects also the file upload UI (which I believe is part of the file explorer dialog). As seen in the screenshot attached to my last post, there are also two strings on the image properties tab of the image manager that have the same symptoms. However, when I insert an image to the editor, right click on it and select properties, there are no missing localized strings. Is that also related to the file explorer dialog bug?
Is there a way to manually patch this issue in the meantime (until Q3 is released)?
I think this issue worth opening a ticket to inform other developers.
Eyal
The bug affects also the file upload UI (which I believe is part of the file explorer dialog). As seen in the screenshot attached to my last post, there are also two strings on the image properties tab of the image manager that have the same symptoms. However, when I insert an image to the editor, right click on it and select properties, there are no missing localized strings. Is that also related to the file explorer dialog bug?
Is there a way to manually patch this issue in the meantime (until Q3 is released)?
I think this issue worth opening a ticket to inform other developers.
Eyal
0
Hi,
Unfortunately, there is no way to update the build that you have since the fix is in the editor server code. The upload part of the dialogs is part of the file explorer control and it will be affected by the fix as well.
Kind regards,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Unfortunately, there is no way to update the build that you have since the fix is in the editor server code. The upload part of the dialogs is part of the file explorer control and it will be affected by the fix as well.
Kind regards,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
eyal
Top achievements
Rank 1
answered on 01 Nov 2009, 05:01 PM
Thanks. Waiting for the release of Q3.
Eyal
Eyal
0
sean
Top achievements
Rank 1
answered on 06 Nov 2009, 02:39 PM
Hi,
it seems that two of the dialog texts are still not loaded right with the newest Q3 release. See the attached image.
it seems that two of the dialog texts are still not loaded right with the newest Q3 release. See the attached image.
0
Hi,
I apologize for the delay in our answer. We did reproduce the problem and fixed it in our code. The fix will be uploaded by the end of the week on our internal builds page - http://www.telerik.com/account/downloads/internal-builds.aspx. Note the build number and make sure it is for the 2009.3 ASP.NET AJAX controls.
Greetings,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
I apologize for the delay in our answer. We did reproduce the problem and fixed it in our code. The fix will be uploaded by the end of the week on our internal builds page - http://www.telerik.com/account/downloads/internal-builds.aspx. Note the build number and make sure it is for the 2009.3 ASP.NET AJAX controls.
Greetings,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
eyal
Top achievements
Rank 1
answered on 23 Nov 2009, 09:53 AM
Hi again,
A minor UI localization issue.
On the Link Manager dialog, next to the URL field, there is a button that opens the Document Manager. The ALT-text for this button uses the same localization string as the one for the hyperlink tab title (LinkManager_HyperlinkTab). When the LinkManager_HyperlinkTab string is altered, changes apply also to the button's ALT-text (text should be 'Document manager')
Markup for the button in LinkManager.ascx (line 523):
Telerik.Web.UI version: 2009.3.1111.35
br,
eyal
A minor UI localization issue.
On the Link Manager dialog, next to the URL field, there is a button that opens the Document Manager. The ALT-text for this button uses the same localization string as the one for the hyperlink tab title (LinkManager_HyperlinkTab). When the LinkManager_HyperlinkTab string is altered, changes apply also to the button's ALT-text (text should be 'Document manager')
Markup for the button in LinkManager.ascx (line 523):
| <td style="padding-left: 4px;"> |
| <tools:StandardButton runat="server" ToolName="DocumentManager" id="DocumentManagerCaller" /> |
| </td> |
Telerik.Web.UI version: 2009.3.1111.35
br,
eyal
0
Hello Eyal,
Thanks for your report! The localization issue will be fixed in the next internal build. The tooltip of the button will correctly show "Document Manager".
Sincerely yours,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Thanks for your report! The localization issue will be fixed in the next internal build. The tooltip of the button will correctly show "Document Manager".
Sincerely yours,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
eyal
Top achievements
Rank 1
answered on 27 Nov 2009, 10:18 AM
Thanks Lini!
Another UI localization issue:
The Style Builder (StyleBuilder.ascx) does not allow localization. All the labels are hard-coded.
br,
eyal
Another UI localization issue:
The Style Builder (StyleBuilder.ascx) does not allow localization. All the labels are hard-coded.
br,
eyal
0
Hi Eyal,
We are aware of this issue and we will provide localization for the StyleBuilder dialog too.
I updated your Telerik points for your valuable feedback!
Kind regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
We are aware of this issue and we will provide localization for the StyleBuilder dialog too.
I updated your Telerik points for your valuable feedback!
Kind regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
