Izenda Logo

Izenda Language Pack

Izenda provides a localization package capable of localizing the Izenda UI, and Field Names into other languages. What version of AdHoc supports the Language Pack?

To use the Language Pack you should have Izenda AdHoc of version 6.4.4314 or higher

What Languages Are Included?

The following languages are currently supported. More are being added based on customer demand and are available upon request. Please contact your sales rep or sales@izenda.com if you need additional languages.

  • Arabic (ar-SA)
  • Bulgarian (bg-BG)
  • ChinesePeoplesRepublicofChina (zh-CN)
  • ChineseTaiwan (zh-TW)
  • Croatian (hr-HR)
  • Czech (cs-CZ)
  • Danish (da-DK)
  • Dutch (nl-NL)
  • English (en-US)
  • Estonian (et-EE)
  • Finnish (fi-FI)
  • French (fr-FR)
  • FrenchCanadian (fr-CA)
  • German (de-DE)
  • Greek (el-GR)
  • Hebrew (he-IL)
  • Hindi (hi-IN)
  • Hungarian (hu-HU)
  • Icelandic (is-IS)
  • Italian (it-IT)
  • Japanese (ja-JP)
  • Korean (ko-KR)
  • Latvian (lv-LV)
  • Lithuanian (lt-LT)
  • Macedonian (mk-MK)
  • Norwegian (nb-NO)
  • Polish (pl-PL)
  • Portuguese (pt-PT)
  • Romanian (ro-RO)
  • Russian (ru-RU)
  • Serbian (sr-Latn-RS)
  • Slovenian (sl-SI)
  • Spanish (es-ES)
  • Swedish (sv-SE)
  • Turkish (tr-TR)
  • Ukrainian (uk-UA)

What Are The Codes Next To The Language Names?

The Izenda localization capability is built on top of Microsoft’s .NET localization API. The Microsoft .NET localization API assigns a specific culture code to each language. For example, American English spoken in the United States is en-US.

What Is “Resources”?

For localization, Izenda uses .Net managed resources Files (*.resx), which are standard resources for .Net. Resource files are XML-formatted text files, so you can edit it in an XML editor or even any plain text editor.

How Do I Install The Language Pack?

The language pack consists of a set of *.resx files inside the “Resources” folder. In addition, you will need a special license key that enables localization. Please contact your account manager to get these resources. Installing the Izenda Language Pack consists of two steps:

  1. Copying localization resources
  2. Set up localization in the code

Copying localization resources

The language pack consists of a set of *.resx files inside “Resources” folder. You should copy this folder to the “bin” folder of your website(Izenda.AdHoc.dll should be in that folder). It's easy to find it, just locate the folder where Izenda.AdHoc.dll is.

Here is a step-by-step list of actions you need to perform to accomplish this:

  1. Locate the “bin” directory inside the folder with your website. It should contain file named “Izenda.AdHoc.dll”.
  2. Create a “Resources” folder there. So the target folder will be “..\bin\Resources”
  3. 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).
  4. Copy that file from the 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”).
  5. 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 In Code?

You should specify the AdHocSettings.Language. This should be done in the InitializeReporting() method in the CustomAdHocConfig class in the Global.asax file. You can set this globally for all users or use logic to change the language per user or per tenant as you like.

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 the target *.resx resource file. Resource files are XML-formatted files, so you can change them easily using any XML or text editor. For example, open the 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. 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 a modified *.resx file is not in the “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

Example:

  • Set AdHocSettings.Language = AdHocLanguage.Spanish (or the appropriate language) in the PostLogin() method
  • Set 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 a page is loaded. The best place to do this is in the 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.