28 Answers, 1 is accepted
0
Hi Sébastien FLEURIET,
Current version of Telerik Reporting does not allow localizing of both Windows Forms and Web Report Viewers.
However, this seems to be a serious gap, for which we are looking for possible solutions.
Thank you for your understanding.
Greetings,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Current version of Telerik Reporting does not allow localizing of both Windows Forms and Web Report Viewers.
However, this seems to be a serious gap, for which we are looking for possible solutions.
Thank you for your understanding.
Greetings,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Tom
Top achievements
Rank 2
Rank 2
answered on 23 Feb 2008, 07:08 PM
Hello,
when will this feature be available?
Greetings!
Tom
when will this feature be available?
Greetings!
Tom
0
Hello Tom,
I am afraid that I cannot give you any valid time frame for this task. As soon as we finish the more prioritized tasks we will include the viewer's localization in the product roadmap.
Regards,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I am afraid that I cannot give you any valid time frame for this task. As soon as we finish the more prioritized tasks we will include the viewer's localization in the product roadmap.
Regards,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Tom
Top achievements
Rank 2
Rank 2
answered on 25 Feb 2008, 08:58 AM
Hello,
thank you! I think it is important as my customers now have an interface half german and half english. Do I have to start a new feature request?
Greetings!
Tom
thank you! I think it is important as my customers now have an interface half german and half english. Do I have to start a new feature request?
Greetings!
Tom
0
There is no need to do this, Tom. We have already logged your request.
Best wishes,
Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Best wishes,
Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Henrik Brinch
Top achievements
Rank 2
Rank 2
answered on 29 Feb 2008, 11:02 AM
Could we get a time-frame on when this will be available? Are we talking Q1 2008 or ...?
Indeed this is a serious limitation for non-english customers!
Indeed this is a serious limitation for non-english customers!
0
Hello Henrik Brinch,
To be honest the report viewers' localization is not in the Q1 2008 road map as we are working on much more important tasks. Anyway, we will try push it forward and do something for the upcoming release.
Best wishes,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
To be honest the report viewers' localization is not in the Q1 2008 road map as we are working on much more important tasks. Anyway, we will try push it forward and do something for the upcoming release.
Best wishes,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Tom
Top achievements
Rank 2
Rank 2
answered on 10 Mar 2008, 09:04 AM
Good morning!
I am sure, that you will add brilliant new features. We all appreciate your work. But I would not say that localisation is not so important. I think it would be OK for us, if we just have the possibility to translate the captions etc. in our code. Thank you for your efforts!
Greetings!
Tom
I am sure, that you will add brilliant new features. We all appreciate your work. But I would not say that localisation is not so important. I think it would be OK for us, if we just have the possibility to translate the captions etc. in our code. Thank you for your efforts!
Greetings!
Tom
0
Tree
Top achievements
Rank 1
Rank 1
answered on 27 Mar 2008, 02:02 AM
Is there ANY workaround for this? If I cannot localize the web report viewer, the Telerik Reportin product will be a total non-starter for my next project.
I need English / French
I need English / French
0
Hi guys,
Thank you for pushing us further on the localization support.
We are about to offer a localization mechanism through XML and I am confident this will be done no later than the upcoming Q1 2008 release, which is three weeks away. The localization mechanism will allow our clients to translate the internal string resources for the viewers (total of 12 tooltips and a "Generating report" message currently) to the language of their choice.
Emmanuel, how far off is your next project? Will you be able to wait another three weeks?
Best wishes,
Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Thank you for pushing us further on the localization support.
We are about to offer a localization mechanism through XML and I am confident this will be done no later than the upcoming Q1 2008 release, which is three weeks away. The localization mechanism will allow our clients to translate the internal string resources for the viewers (total of 12 tooltips and a "Generating report" message currently) to the language of their choice.
Emmanuel, how far off is your next project? Will you be able to wait another three weeks?
Best wishes,
Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Tree
Top achievements
Rank 1
Rank 1
answered on 28 Mar 2008, 06:46 PM
This is good news. I need to prepare a prototype for April 10th but I can get away with having it just in unilingual English for that date. I would need full localization support for mid-May as the first fully-functional version of the project needs to be delivered by end of May.
I can't afford to start with Telerik Reporting and then have to switch to another solution if localization doesn't materialize fully by mid-May. Please let me (us) know by April 2 if there is a chance, however small, that localization won't exist by end of May.
I can't afford to start with Telerik Reporting and then have to switch to another solution if localization doesn't materialize fully by mid-May. Please let me (us) know by April 2 if there is a chance, however small, that localization won't exist by end of May.
0
Hi Eriksson,
The localization will be part of the Q1 2008 release, due in about 3 weeks. I will update this thread as soon as the Telerik Reporting Q1 2008 is out.
Sincerely yours,
Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
The localization will be part of the Q1 2008 release, due in about 3 weeks. I will update this thread as soon as the Telerik Reporting Q1 2008 is out.
Sincerely yours,
Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Tree
Top achievements
Rank 1
Rank 1
answered on 31 Mar 2008, 07:16 PM
Thanks Svetoslav. I'm going with Telerik Reporting then!
0
You are welcome! I will let you know when we have further information on the topic.
Regards,
Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Regards,
Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Hello guys,
We are pleased to announce that we have localized the Report Viewer in the Q1 2008 version of Telerik Reporting. The new version should be available for download in your Client.net accounts. In case you do not see the DEV versions yet, please be patient - we are updating our client's accounts with the latest versions as we speak.
For more information on the new version, please see
What's New in Telerik Reporting
Release History
Kind regards,
Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We are pleased to announce that we have localized the Report Viewer in the Q1 2008 version of Telerik Reporting. The new version should be available for download in your Client.net accounts. In case you do not see the DEV versions yet, please be patient - we are updating our client's accounts with the latest versions as we speak.
For more information on the new version, please see
What's New in Telerik Reporting
Release History
Kind regards,
Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Tom
Top achievements
Rank 2
Rank 2
answered on 16 Apr 2008, 08:02 PM
Hello!
I did not install it until now. But thank you very much in advance! :-)
Greetings!
Tom
I did not install it until now. But thank you very much in advance! :-)
Greetings!
Tom
0
Henrik Brinch
Top achievements
Rank 2
Rank 2
answered on 20 Apr 2008, 04:10 PM
Ok it seems that you've done some thoughts on localizing the reportviewer in the new release. But I can't understand that you haven't provided us with an example .resx file ready for localization ?
I had to download the source and locate the appropriate resource.resx file ((web report viewer) - but to my greatest fear I discovered that it looks as if it is only a partial localization - that is the content of the drop-down export (the format list) isn't part of the resource file. So even if I will be able to localize everything else I still have the "TIFF file", "CSV (comma delimited)" etc. in the list :-(
Please tell my I'm wrong here! (I'm not very keen on having to wait for Q2 for complete localization of the reportviewer).
I had to download the source and locate the appropriate resource.resx file ((web report viewer) - but to my greatest fear I discovered that it looks as if it is only a partial localization - that is the content of the drop-down export (the format list) isn't part of the resource file. So even if I will be able to localize everything else I still have the "TIFF file", "CSV (comma delimited)" etc. in the list :-(
Please tell my I'm wrong here! (I'm not very keen on having to wait for Q2 for complete localization of the reportviewer).
0
Hello Henrik,
Please see this KB article for complete instructions on localizing the report viewer controls and access to the default resource files.
Regarding the export format names - actually the rendering extensions are part of the reporting engine but not of the viewers so you won't find any resource for them. Anyway there is valid way to localize their descriptions. You can register your own rendering extensions based on the default but with different description texts. For more information please see Configuring Telerik Reporting.
Best wishes,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Please see this KB article for complete instructions on localizing the report viewer controls and access to the default resource files.
Regarding the export format names - actually the rendering extensions are part of the reporting engine but not of the viewers so you won't find any resource for them. Anyway there is valid way to localize their descriptions. You can register your own rendering extensions based on the default but with different description texts. For more information please see Configuring Telerik Reporting.
Best wishes,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Henrik Brinch
Top achievements
Rank 2
Rank 2
answered on 22 Apr 2008, 09:46 AM
The KB article is the same as the documentation and doesn't give an example (outline) of the contents of the .resx file. This still has to be extracted from the source files (?) - which of course is no problem for us who have the subscription that includes the source :)
However why not include an example .resx file for localizing the reportviewer?
However why not include an example .resx file for localizing the reportviewer?
0
Hello Henrik,
The resource files are attached at the bottom of the KB article (please see attached screenshot).
Kind regards,
Steve
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
The resource files are attached at the bottom of the KB article (please see attached screenshot).
Kind regards,
Steve
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Henrik Brinch
Top achievements
Rank 2
Rank 2
answered on 22 Apr 2008, 12:35 PM
Thanks ... and sorry I was a little blind there :)
0
Henrik Brinch
Top achievements
Rank 2
Rank 2
answered on 22 Apr 2008, 07:21 PM
It would be nice with an example for both Web and Winforms viewer.
I've tried following the steps you describe in the documentation. The .resx file is correctly named ("Telerik.ReportViewer.WebForms.da-DK.Resources.resx") and placed in App_GlobalResources of the site (double checked that is it in the correct location).
I've added globalization to the web.config
and even tried directly on the page
but yet without any luck :( What can I be doing wrong?
Brgds.
- Henrik
I've tried following the steps you describe in the documentation. The .resx file is correctly named ("Telerik.ReportViewer.WebForms.da-DK.Resources.resx") and placed in App_GlobalResources of the site (double checked that is it in the correct location).
I've added globalization to the web.config
| <system.web> |
| <globalization uiCulture="da" culture="da-DK"/> |
| .... |
| .... |
and even tried directly on the page
| <%@Page Language="C#" AutoEventWireup="true" CodeFile="Reports.aspx.cs" Inherits="Reports" MasterPageFile="~/Main.master" UICulture="da" Culture="da-DK" %> |
but yet without any luck :( What can I be doing wrong?
Brgds.
- Henrik
0
Hi Henrik Brinch,
The localization of the ReportViewer was a last-minute feature, due to customer pressure, and was not part of the original Q1 2008 release roadmap. Unfortunately, in the haste, we have made a small misleading error in the documentation. The proper naming convention for the resource files should be as follows:
Telerik.ReportViewer.WebForms.Resources.[culture].resx
So, for the "da-DK" specific UI culture you should name the file:
Telerik.ReportViewer.WebForms.Resources.da-DK.resx
Make sure that the "Copy to Output Directory" property is set to "Copy if newer" or "Copy always" for the RESX file.
Also, you have created a RESX file for the "da-DK" specific UI culture, but you have specified the "da" neutral UI culture in your web.config file. The default .NET resource fallback strategy is as follows: "da-DK" -> "da" - > "neutral", so in order to make the localization for the "da-DK" specific UI culture work, you should put the following line in your web.config file instead:
Please accept our apologies for the inconvenience this documentation error has caused you! The KB article on our web site would be fixed shortly and the help documentation will be updated for the upcoming Q1 2008 SP1 release too.
Greetings,
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
The localization of the ReportViewer was a last-minute feature, due to customer pressure, and was not part of the original Q1 2008 release roadmap. Unfortunately, in the haste, we have made a small misleading error in the documentation. The proper naming convention for the resource files should be as follows:
Telerik.ReportViewer.WebForms.Resources.[culture].resx
So, for the "da-DK" specific UI culture you should name the file:
Telerik.ReportViewer.WebForms.Resources.da-DK.resx
Make sure that the "Copy to Output Directory" property is set to "Copy if newer" or "Copy always" for the RESX file.
Also, you have created a RESX file for the "da-DK" specific UI culture, but you have specified the "da" neutral UI culture in your web.config file. The default .NET resource fallback strategy is as follows: "da-DK" -> "da" - > "neutral", so in order to make the localization for the "da-DK" specific UI culture work, you should put the following line in your web.config file instead:
| <globalization uiCulture="da-DK" culture="da-DK"/> |
Please accept our apologies for the inconvenience this documentation error has caused you! The KB article on our web site would be fixed shortly and the help documentation will be updated for the upcoming Q1 2008 SP1 release too.
Greetings,
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Henrik Brinch
Top achievements
Rank 2
Rank 2
answered on 23 Apr 2008, 03:43 PM
Thanks, that did the trick - now it is localized...
almost ...
I noticed the "[xxx] of [yyy]" part isn't localizable (that is the "of" part), though I've just submitted a bug-report on that.
Brgds.
- Henrik
almost ...
I noticed the "[xxx] of [yyy]" part isn't localizable (that is the "of" part), though I've just submitted a bug-report on that.
Brgds.
- Henrik
0
David
Top achievements
Rank 1
Rank 1
answered on 24 Apr 2008, 08:22 AM
Hi
I am unable to localize the win viewer.
I use a properly name convention of the resx file, in my case:
Telerik.ReportViewer.WinForms.es-ES.Resources.resx
or
Telerik.ReportViewer.WinForms.Resources.es-ES.resx
I tried both.
I also set on contructor of a windows form that have thw win viewer control, before the initialize call:
After All, The Win report viewer still not localized to spanish.
I don't know what is wrong with that...
David Tomás
I am unable to localize the win viewer.
I use a properly name convention of the resx file, in my case:
Telerik.ReportViewer.WinForms.es-ES.Resources.resx
or
Telerik.ReportViewer.WinForms.Resources.es-ES.resx
I tried both.
I also set on contructor of a windows form that have thw win viewer control, before the initialize call:
System.Threading.Thread.CurrentThread.CurrentCulture =
New System.Globalization.CultureInfo("es-ES")
System.Threading.Thread.CurrentThread.CurrentUICulture =
New System.Globalization.CultureInfo("es-ES")
I also tried to put this line before the report instance was asigned to the viewer (RPT is report instance):
rpt.Culture =
New System.Globalization.CultureInfo("es-ES")
After All, The Win report viewer still not localized to spanish.
I don't know what is wrong with that...
David Tomás
0
Hello David,
As my colleague Ivan explained in his last reply, there is a mistake in the Telerik Reporting documentation, for which we apologize. The correct place for the culture specifier is just before the extension:
Telerik.ReportViewer.WinForms.Resources.[culture].resx
We have already updated the online version of Telerik Reporting documentation, the CHM version and the related KB article as well.
Regarding the missing localization for the Web Viewer's [xxx] of [yyy] string - we have already added to the resources so it will be available with the upcoming service pack due in a couple of weeks.
Greetings,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
As my colleague Ivan explained in his last reply, there is a mistake in the Telerik Reporting documentation, for which we apologize. The correct place for the culture specifier is just before the extension:
Telerik.ReportViewer.WinForms.Resources.[culture].resx
We have already updated the online version of Telerik Reporting documentation, the CHM version and the related KB article as well.
Regarding the missing localization for the Web Viewer's [xxx] of [yyy] string - we have already added to the resources so it will be available with the upcoming service pack due in a couple of weeks.
Greetings,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
David
Top achievements
Rank 1
Rank 1
answered on 24 Apr 2008, 09:42 AM
Hi,
As I explained before, I tried it with both forms of naming convention, including your last response. The problem is that win report viewer is ignoring it. It never was translated.
David Tomás
As I explained before, I tried it with both forms of naming convention, including your last response. The problem is that win report viewer is ignoring it. It never was translated.
David Tomás
0
Hello David,
We have confirmed that there is a bug in the Report Viewer localization. This bug concerns only the Windows Forms version of the Report Viewer and only when the Telerik Reporting assemblies are stored in the Global Assembly Cache (GAC). Apparently, in that particular case, the Report Viewer searches for the RESX resource files in the wrong place and fails to locate and load them. This bug is logged in our bug tracking system and will be fixed for the upcoming service pack.
Meanwhile, you can use the following workaround to make the Windows Forms Report Viewer localization work, at least on the machines of your customers:
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We have confirmed that there is a bug in the Report Viewer localization. This bug concerns only the Windows Forms version of the Report Viewer and only when the Telerik Reporting assemblies are stored in the Global Assembly Cache (GAC). Apparently, in that particular case, the Report Viewer searches for the RESX resource files in the wrong place and fails to locate and load them. This bug is logged in our bug tracking system and will be fixed for the upcoming service pack.
Meanwhile, you can use the following workaround to make the Windows Forms Report Viewer localization work, at least on the machines of your customers:
- Find all references to the Telerik Reporting assemblies in your solution and set the property "Copy Local" to "True" in the Property Inspector for each of them.
- When deploying your Windows Forms application, copy the Telerik Reporting assemblies and the localization RESX resource files in the same directory where your main application executable is installed (do not store the Telerik Reporting assemblies in the GAC).
- When the application is started, the Report Viewer will be able to load the localization RESX resource files from the right place and successfully localize itself according to the current UI culture.
Please, accept our apologies for all the troubles this last minute feature caused you! Your Telerik points have been updated.
Best wishes,
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center