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.

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

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.