I'm a bit confused in what is currently possible and not possible with the ReportViewer and Silverlight in regards to localization.
Searching through the forums you'll get a mixture of very old and new threads and I'm having a hard time finding out what I actually can do right now. Also the release notes for the latest version confuse me.
In the release notes for Telerik Reporting Q2 2010 SP1 (v4.1.10.921).
There's an entry in the Silverlight Report Viewer section that says:
"Fixed: Cannot localize a Report through the Localizable property."
Still there's a entry in the PITS:
"Issue ID 355 - Cannot localize a Report using the Localizable property"
(http://www.telerik.com/support/pits.aspx#/public/reporting/355)
which to me sounds similar to the one fixed in the current release but the entry in the PITS still says its status is open and that it's not scheduled for a specific verison yet. If they are not the same can you please explain their differences.
I've managed to somewhat localize my reports by setting the Localizable property to True and adding the resx files for the languages that I need. There's also a Culture property on the Report class which let's you specify the format for dates, currency etc. but this property is not controlling the localized texts which still needs Thread.CurrentThread.CurrentUICulture property. And setting that property affects all reports in the current renderingprocess. Are you planning to extend the Culture feature to also apply to the UICulture in such way that you can set the report language per report?
I'm currently trying to use the ReportBook to display a bunch of invoices to ease batch printing etc.
And what I ultimately would like to do is for each report in my ReportBook specify the culture it will use when rendering and this would be based on the language settings of the customer recieving the invoice and not the on UICulture using my application.
Will anything in this area change with the next release when you move to Silverlight 4?
Tomas
3 Answers, 1 is accepted
Indeed the entry in PITS and in our release notes is the same work item which for some reason did not get updated and we would forward that to the colleagues responsible for PITS - please excuse us for the confusion that this created. So in short to confirm - this problem has been fixed!
As for your other inquiry - this is how globalization in the .NET framework works. You always need to specify CurrentUICulture in order to get properly localized values on the client.
Sorry for the created confusion once again.
Greetings,
Steve
the Telerik team
Rank 1
Hi Steve,
What I meant was that the Report has a Culture property but setting this to the culture of choice only affects
the dynamic text part, "Thread.CurrentThread.CurrentCulture" (i.e. date, time, money) and not the
static text part, "Thread.CurrentThread.CurrentUICulture" (i.e. column headings, titles)
By only having one property called Culture I would assume they would set both underlying properties?
Btw the PITS (http://www.telerik.com/support/pits.aspx#/public/reporting/355) has not been updated yet.
Tomas
Indeed I've verified that there is a problem with the Culture settings due to changes we've made for the new interactivity features. We apologize for the inconvenience and rest assured we would address the glitch in the upcoming release.
With the current development of this problem, the Open Status of the issue in PITS is correct :).
Best wishes,
Steve
the Telerik team