-My project is asp.NET MVC 4 web application.
-My project use VS integrated designer with report templates being .cs files.
-My project still use old ASPX report viewer.
I want to set specific fonts and other 'Style' properties for each localized culture. (for example, I want to use Font_A as default, Font_B for en-US and Font_C for en-GB.)
I tried localizing them the normal way like how I localized the texts. (Starting from changing 'Localizable' property to True and switch 'Language' property to put the localized text in, which in this case, set a font specific for that culture)
The problem is, the designer didn't count changing 'Style' properties as a part of localization and didn't store the data in .resx files.
Any solution or work-around?
PS. I don't want to change into new version.
-My project use VS integrated designer with report templates being .cs files.
-My project still use old ASPX report viewer.
I want to set specific fonts and other 'Style' properties for each localized culture. (for example, I want to use Font_A as default, Font_B for en-US and Font_C for en-GB.)
I tried localizing them the normal way like how I localized the texts. (Starting from changing 'Localizable' property to True and switch 'Language' property to put the localized text in, which in this case, set a font specific for that culture)
The problem is, the designer didn't count changing 'Style' properties as a part of localization and didn't store the data in .resx files.
Any solution or work-around?
PS. I don't want to change into new version.
1 Answer, 1 is accepted
0
Hinata
Top achievements
Rank 1
Rank 1
answered on 14 Jan 2015, 02:16 PM
Hi Builk,
Localizing reports is about changing the language of the report, not the layout and design. The built-in localization in Reporting also states this: http://www.telerik.com/help/reporting/advanced-localizing-reports.html
The built-in mechanism saves the text strings inside a report resource file specific for the culture. It does not save style and other type of configurations.
By your description I can suggest that you need to programmatically check the culture inside your application. Depending on the results of this check, you need to swap the report with a different report which is designed specifically for the culture of the client.
Localizing reports is about changing the language of the report, not the layout and design. The built-in localization in Reporting also states this: http://www.telerik.com/help/reporting/advanced-localizing-reports.html
The built-in mechanism saves the text strings inside a report resource file specific for the culture. It does not save style and other type of configurations.
By your description I can suggest that you need to programmatically check the culture inside your application. Depending on the results of this check, you need to swap the report with a different report which is designed specifically for the culture of the client.