Let’s suppose you need Izenda Reports in French. Here are step-by-step list of actions you need to perform then:

1. Locate “bin” directory inside the folder with your website. It should contain file named “Izenda.AdHoc.dll” and create “Resources” folder there. So the target folder will be “..\bin\Resources”
2. Refer to section “What Languages Are Included?” and get from localization pack the *.resx with name corresponding to the language you need (in our case this will be “French.resx” file).
3. Copy that file from localization pack into the previously created “..\bin\Resources” folder of your website (in our case the full file path will be “..\bin\Resources\French.resx”).
4. Replace your license key with one supporting localization. Please contact support@izenda.com or your account manager for details.

How To Set The Language I Want To Use?

You should specify AdHocSettings.Language setting in the code. Normally it’s in PostLogin() method (or ConfigureSettings() method if you’d like to all users use the same language) of CustomAdHocConfig in the Global.asax file:

public override void PostLogin()  
{
        AdHocSettings.Language = AdHocLanguage.French;
}

Can I Change Some Or All Of The Resources?

Yes, you can change the localization by yourself.

All you have to do is to change target *.resx resource file. Resource file is XML-formatted file, so you can change it easily using any XML or text editor.

For example open French.resx file in text editor. At the top you will see service information (<xsd:schema></xsd:schema> node) and headers (<resheader></resheader> nodes). Just skip them because all you need is <data></data> nodes:

<data name="Field" xml:space="preserve">
	<value>Champ</value>
</data>
<data name="Table" xml:space="preserve">
	<value>Table</value>
</data>
<data name="NoFieldsSelected" xml:space="preserve">
	<value>Pas de champs sélectionnés</value>
</data>
    

The “name” attribute should be as it is. And you can change values inside <value></value> nodes.

That’s it. Save the file and restart IIS and you’ll see the changes immediately.

Note: If modified *.resx file is not in “bin\Resources” folder of your site you should copy it there.

Can I Use Language That Is Not In The Language Pack?

If you didn’t find the language you want to use in Language Pack (see “What Languages Are Included?” section) you can contact your sales rep or sales@izenda.com to get it.

What Code Do I Need to Localize The User Interface and Field Names?

The following settings need to be applied to the PostLogin() method of the CustomAdHocConfig class. Add an alias for every field that needs to be localized or perform a dynamic lookup from the database.

Install the appropriate languages in your bin folder

Set AdHocSettings.Language = AdHocLanguage.French (or the appropriate language) in the PostLogin() method

Use Izenda.AdHoc.FieldAliases[“ShipCity”] = “Cuidad” to localize individual field names in PostLogin()

How Do I Refine The Provided Localization?

The Izenda.AdHoc.AdHocSettings.LabelAliases[] collection may be used to provide more granular UI localization if the provided localization is not sufficient.

What Code Do I Need to Localize Actual Report Data?

Data may be localized by overriding the AdHocConfig.ProcessDataSet() method and dynamically changing the DataSet returned by the database.

Does It Support Right-To-Left Languages?

Yes. Right-to-left languages are supported.
First you should add a new css class to the master page (or separately to the all pages if you don't use master page)

	<style type="text/css">
		.TabStrip .ActiveTab, .TabStrip .InactiveTab, .TabStrip .DisabledTab{
			direction: ltr;
		}
	</style>
  

Now you should add some code to the master page code behind file. Since you may change localization almost anywhere in the code it is required to check the language every time page loaded. the best place to do it is Page_Load method of the page.

	protected void Page_Load(object sender, EventArgs e)  
	{
		if (AdHocSettings.Culture.TextInfo.IsRightToLeft)
			this.Page.Header.Controls.Add(
				new System.Web.UI.LiteralControl(
					"<style type=\"text/css\">div{direction:rtl;}tr.VisualGroup td{text-align:right !important;}</style>"));
	}
  

The result is below:

What Needs To Be Installed on The Server and Browser?

The Microsoft Language must be installed on the server as well as the browser for the fonts to display properly. Please download the language file from Microsoft’s web site. The Izenda Localization Pack assumes that the server and user have the proper resources installed.