Intersoft Community - WebGrid Enterprise - WebGrid Localization questions

WebGrid Localization questions

Gmontes — Wed, 16 Mar 2011 09:26:44 GMT

Yeah, that settles it.

Thanks Martin.

WebGrid Localization questions

MarTin — Wed, 16 Mar 2011 03:41:08 GMT

Hello,

Here is the answer for your questions.

1) I don't need the whole 'CommonLibrary' folder in production, just 'CommonLibrary/WebGrid/v7_0_722/Localization', right?

Yes, you only need the folder that is related with the localization.

2) Would the steps I tookt be enough to settle the localization issue? (That is moving the files, setting those TextSetting properties and adding the web.config key)

Yes, once you set the configuration in web.config, WebGrid will detect and read the location specified in that file.

Hope this helps.

Thank you.

WebGrid Localization questions

Gmontes — Tue, 15 Mar 2011 10:03:26 GMT

Hi Martin,

Yeah, your reply answers most of my questions. Still, could you help me confirm the two remaining?

1) I don't need the whole 'CommonLibrary' folder in production, just 'CommonLibrary/WebGrid/v7_0_722/Localization', right?

2) Would the steps I tookt be enough to settle the localization issue? (That is moving the files, setting those TextSetting properties and adding the web.config key)

Thanks

WebGrid Localization questions

MarTin — Mon, 14 Mar 2011 00:39:39 GMT

Hello,

Actually you can delete those files (Japanase.xml, Korean.xml and List2.xml). The complete localization list should be wglang_ja-JP.xml for japanese.

We have TextSettings property in WebGrid, which you can use to set the language manually or you can use custom mode to obtain the language from the xml file which is located in Localization folder.

wglang_ja-JP is the default format of the localization file. It represents a single language that is available to be used in WebGrid.

Therefore, it is not possible to manage various cultures in one single language file.You could only assign 1 culture in each file.

Hope this helps.

Thank you.

WebGrid Localization questions

Gmontes — Fri, 11 Mar 2011 17:18:12 GMT

Hi,

We're thinking of using our own language files for WebGrid localization purposes. Could you help me validate these changes I've done in my project?

In the OnInitializeLayout event for those instances that require localization I've added:

webGrid.LayoutSettings.TextSettings.UseWebResources = false;
            webGrid.LayoutSettings.TextSettings.Language = LanguageMode.UseCulture;

And in my web.config file, inside appSettings...

<add key="ISNet.WebUI.WebGrid.v7_0_7200.LocalizationDirectory" value="~/GridLocalization/" />

And finally... the instructions in the reference file said I needed to copy the whole CommonLibrary folder. I just took "Inside CommonLibrary\WebGrid\V7_0_7200\Localization" and renamed it to "GridLocalization" a folder inside our webapplication folder. That's all I should need from the CommonLibrary contents, right?

Also, I see some files in the localization folder that I don't quite find an use for? Can I delete those?

Inside CommonLibrary\WebGrid\V7_0_7200\Localization there's:

Japanese.xml

Korean.xml

List2.xml

What is the purpose of those files? I mean... we already have wglang_ja-JP.xml for japanese and wglang_ko-KR.xml for Korean.

Also, is there a way to point various cultures to a single language file? We may not have differences between en-US and en-CA and en-GB...

Regards