Alessandro Strazzari
Top achievements
Rank 1
Rank 1
Alessandro Strazzari
asked on 05 Jan 2011, 06:15 PM
Hi!
There is support for localization of reports serialized on xml files? How it works?
For instance serializing a report we have obtained the following xml extract:
<TextBox Value="Cliente: " >
where the value of label textbox is built-in in the xml in one only culture. There is any way to have something like a link to a resource like report in compiled mode?
We have found the following fix in the last release:
<<<
What's Fixed in Telerik Reporting Q3 2010 SP1 (v4.2.10.1221)
Report Model
Fixed: XML report serialization should be culture agnostic
>>>
what that means? We can't find other information about it.
Thanks
There is support for localization of reports serialized on xml files? How it works?
For instance serializing a report we have obtained the following xml extract:
<TextBox Value="Cliente: " >
where the value of label textbox is built-in in the xml in one only culture. There is any way to have something like a link to a resource like report in compiled mode?
We have found the following fix in the last release:
<<<
What's Fixed in Telerik Reporting Q3 2010 SP1 (v4.2.10.1221)
Report Model
Fixed: XML report serialization should be culture agnostic
>>>
what that means? We can't find other information about it.
Thanks
3 Answers, 1 is accepted
0
Hello Alessandro Strazzari,
Peter
the Telerik team
You have noticed correctly that the serialized XML report can be serialized in single culture only. This is expected behavior because the XML serialization doesn't support multiple cultures. Thus our suggestion is to have a separate XML definition for every culture used.
All the best,Peter
the Telerik team
0
Alessandro Strazzari
Top achievements
Rank 1
Rank 1
answered on 12 Jan 2011, 06:39 PM
> report can be serialized in single culture only. This is expected behavior because the XML serialization doesn't support multiple cultures. Thus our suggestion is to have a separate XML definition for every culture used.
Ok, is clear, but this is not optimal, because for any report update force us to upgrade all the relative xml culture definitions. Do you have any plan to upgrade the xml defition to be culture aware?
Thanks
Ok, is clear, but this is not optimal, because for any report update force us to upgrade all the relative xml culture definitions. Do you have any plan to upgrade the xml defition to be culture aware?
Thanks
0
Hi Alessandro Strazzari,
By design the xml report definition corresponds to an instantiated Report class and this is the reason why it supports only one culture. Indeed, you have a point here that a change in the report layout will make you update multiple .xml files because of the localization. One way to work around this is to set the Values of the localizable items after the report is loaded from xml by using the same approach as in the InitializeComponent method with the ResourceManager.
Hope this helps.
All the best,
Chavdar
the Telerik team
By design the xml report definition corresponds to an instantiated Report class and this is the reason why it supports only one culture. Indeed, you have a point here that a change in the report layout will make you update multiple .xml files because of the localization. One way to work around this is to set the Values of the localizable items after the report is loaded from xml by using the same approach as in the InitializeComponent method with the ResourceManager.
Hope this helps.
All the best,
Chavdar
the Telerik team