Localization.md
... ...
@@ -1,4 +1,4 @@
1
-**Izenda Language Pack**
1
+<a name="Top"></a>**Izenda Language Pack**
2 2
3 3
[[_TOC_]]
4 4
... ...
@@ -6,7 +6,7 @@ Izenda provides an add-on localization package capable of localizing the Izenda
6 6
What version of AdHoc supports Language Pack?
7 7
8 8
To use Language Pack you should have Izenda AdHoc of version 6.4.4314 or higher
9
-###<a name="IncludedLanguages"></a>What Languages Are Included?
9
+###<a name="IncludedLanguages"></a>What Languages Are Included? | [Top](#Top)
10 10
11 11
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.
12 12
* Arabic (ar-SA)
... ...
@@ -41,7 +41,7 @@ Installing Izenda Language Pack consists of **two** steps:
41 41
1. Copying localization resources
42 42
2. Set up localization in the code
43 43
44
-###Copying localization resources
44
+###Copying localization resources | [Top](#Top)
45 45
46 46
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.
47 47
... ...
@@ -49,7 +49,7 @@ The language pack consists of a set of *.resx files inside “Resources” folde
49 49
50 50
![](http://wiki.izenda.us/Localization/resources_folder_2.png)
51 51
52
-###Set up localization in the code
52
+###Set up localization in the code | [Top](#Top)
53 53
54 54
You can set up the localization language almost anywhere in the code by specifying the AdHocSettings.Language setting.
55 55
But normally you would like to set localization in the PostLogin() method of the CustomAdHocConfig class in the Global.asax file because different users might like to use different languages:
... ...
@@ -68,7 +68,7 @@ Let’s suppose you need Izenda Reports in French. Here is a step-by-step list o
68 68
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”).
69 69
5. Replace your license key with one supporting localization. Please contact support@izenda.com or your account manager for details.
70 70
71
-###How To Set The Language I Want To Use?
71
+###How To Set The Language I Want To Use? | [Top](#Top)
72 72
73 73
You should specify the AdHocSettings.Language setting in the code. Normally it’s done in the PostLogin() method (or ConfigureSettings() method if you’d like to all users use the same language) of CustomAdHocConfig in the Global.asax file:
74 74
... ...
@@ -80,7 +80,7 @@ public override void PostLogin()
80 80
81 81
```
82 82
83
-###Can I Change Some Or All Of The Resources?
83
+###Can I Change Some Or All Of The Resources? | [Top](#Top)
84 84
85 85
Yes, you can change the localization by yourself.
86 86
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.
... ...
@@ -103,11 +103,11 @@ The “name” attribute should be as it is. You can change values inside ``` <v
103 103
That’s it. Save the file and restart IIS and you’ll see the changes immediately.
104 104
Note: If a modified *.resx file is not in the “bin\Resources” folder of your site, you should copy it there.
105 105
106
-###Can I Use Language That Is Not In The Language Pack?
106
+###Can I Use Language That Is Not In The Language Pack? | [Top](#Top)
107 107
108 108
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.
109 109
110
-###What Code Do I Need to Localize The User Interface and Field Names?
110
+###What Code Do I Need to Localize The User Interface and Field Names? | [Top](#Top)
111 111
112 112
The following settings need to be applied to the PostLogin() method of the CustomAdHocConfig class.
113 113
* Add an alias for every field that needs to be localized or perform a dynamic lookup from the database.
... ...
@@ -117,15 +117,15 @@ Example:
117 117
* Set AdHocSettings.Language = AdHocLanguage.Spanish (or the appropriate language) in the PostLogin() method
118 118
* Set Izenda.AdHoc.FieldAliases[“ShipCity”] = “Cuidad” to localize individual field names in PostLogin()
119 119
120
-###How Do I Refine The Provided Localization?
120
+###How Do I Refine The Provided Localization? | [Top](#Top)
121 121
122 122
The Izenda.AdHoc.AdHocSettings.LabelAliases[] collection may be used to provide more granular UI localization if the provided localization is not sufficient.
123 123
124
-###What Code Do I Need to Localize Actual Report Data?
124
+###What Code Do I Need to Localize Actual Report Data? | [Top](#Top)
125 125
126 126
Data may be localized by overriding the AdHocConfig.ProcessDataSet() method and dynamically changing the DataSet returned by the database.
127 127
128
-###Does It Support Right-To-Left Languages?
128
+###Does It Support Right-To-Left Languages? | [Top](#Top)
129 129
130 130
Yes. Right-to-left languages are supported.
131 131
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)