Localization
in [Reports]
|
From: Henrik Skak Pedersen on 3 Oct 2006 16:17 Hi, We are currently working on a project where we need to deploy some reports (Reporting Services 2005) in a multi language environment, but we struggling to find out how to localize reports in reporting services. 1) How do I localize report texts? I can see that there's language property and a ValueLocId property? Should I use these and how? 2) How do I localize report parameter prompts? 3) How do I localize reportname and description? For the description I can see that there's a DescriptionLocId? Are there any good resources on how to localize reports in Reporting Services 2005? Kind Regards Henrik
From: Steven Cheng[MSFT] on 4 Oct 2006 01:24 Hello Henrik, As for the Reporting Service 2005, it does support some localization features, they include: 1)the localization of the built-in UI components, such as SSRS's htmlviewer, report designer 2) some simple localization on the SSRS report's data For 1), the SSRS has done the work for us already, for example, when we visit the html report, the UI elements on the htmlviewer(button or other UI element's text) will render the localized representation according to client-side browser's user-language setting. For 2), if we want to do some simple localization on the static data/text displayed on our report, we can dynamically format them according to the "User!Language" parameter in our report expression. Or you can even build custom assembly that has custom code logic to generate localizaed text(from .net resource ) accordin to this parameter. You can find all the localization support of SSRS 2005 in the BOL: #International Considerations for Reporting Services http://msdn2.microsoft.com/en-us/library/ms156493.aspx Therefore, for your scenario and the questions you mentioned, my understanding is: 1) How do I localize report texts? I can see that there's language property and a ValueLocId property? Should I use these and how? ======================================== These properties is mainly used to specify a fixed culture/locale for text/data formatting. Our report expression's output will be affected by these setting. I'm wondering whether you also want to localize the data which will be displayed on report(retrieved from datasource). If this is the case, I'm afraid those settings can not help on this because the data is already retrieved by data processing engine before rendering, and rendering engine can not translate text on the fly. For report which has data dedicated to different languages/cultures, it is recommended that we build multiple reports for each culture/language respectively. 2) How do I localize report parameter prompts? ======================================== I think the report parameter prompts is a part of the built-in report htmlviewer which will render localized UI according to client browser's language setting. 3) How do I localize reportname and description? For the description I can see that there's a DescriptionLocId? ========================================= I think such LOCID is also mainly used for some date/time number formatting , and can not help on text/data localized formatting. For displaying multiple language specific reports, I would suggest create multiple reports for each language(use the corresponding datasource from database) as mentioned in #1. Please feel freee to let me know if you have any questions or other consideration on this. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights.
From: Steven Cheng[MSFT] on 9 Oct 2006 05:05 Hello Henrik, How are you doing on this issue? I've just discussed with some other engineers from reporting service team and they have help confirm that the "LocId" of reportItem or the report is still an unsupported feature that teams the SSRS runtime which generate report will ignore such properties on each reportItem. The only usage of this LocID property is that we can use this property to do some static localization related transformation on the RDL file. For example, we can use XSLT to transform the RDL into another RDL xml form and use the "LocID" to reference certain elements in the RDL when performing XSLT transforming. Currently , for SSRS report localization, I've mentioned the most common approaches in my last reply. Please feel free to let me know if you have any further questions on this. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights.
From: sebastiangomezcorrea on 26 Oct 2006 12:28 Hi all, I'm working with local reports (rdlc) and what I'm trying to do is to localize the static text (column headers), not displayed data. I have my column headers in textboxes which have the 'ValueLocID' property, but I can't figure out how to make it work. Is it possible to accomplish what I want with a single rdlc file? (not as many as languages) Could somebody point me out to the right direction? TIA, Sebastian On Oct 9, 7:05 am, stch...(a)online.microsoft.com (Steven Cheng[MSFT]) wrote: > Hello Henrik, > > How are you doing on this issue? I've just discussed with some other > engineers from reporting service team and they have help confirm that the > "LocId" of reportItem or the report is still an unsupported feature that > teams the SSRS runtime which generate report will ignore such properties on > each reportItem. > > The only usage of this LocID property is that we can use this property to > do some static localization related transformation on the RDL file. For > example, we can use XSLT to transform the RDL into another RDL xml form and > use the "LocID" to reference certain elements in the RDL when performing > XSLT transforming. > > Currently , for SSRS report localization, I've mentioned the most common > approaches in my last reply. Please feel free to let me know if you have > any further questions on this. > > Sincerely, > > Steven Cheng > > Microsoft MSDN Online Support Lead > > This posting is provided "AS IS" with no warranties, and confers no rights.
|
Pages: 1 Prev: Localization of reports Next: Multi-value parameter returns syntax error |