I'm trying to make the administration screen of our module multilingual but for now my tests doesn't seem to work. IIS7 admin screen do work properly. When we install the japanese language pack on w2k8, IIS7 admin screens works fine but not ours for now.
What make it a little bit difficult is that since all pages are abtract, you have to make you GUI by hand for all page objects. In the case of the DialogPage, you can always get away by creating a user control and add it at run time but still in that case, the language was not changed.
What is the procedure and gotcha that I have to be careful when making it multilingual? For now, for testing pupose, I separated the code of my derived ModuleListPage control in a partial class to make it similar to the way visual studio would make it (not necessary but remove the clutter from the main class). I gave it for testing the same name VS would give it but I don't think that a problem. I created all the column headers, set the strings by hand in the resource file, then I apply them with the ComponentResrouceManager.ApplyResources. For the main language, it works well. for Japanese, it doesn't show it.
I didn't set in the resource the $this.Localizable variable since I cannot set the "others" resource like Visual studio do since it doesn't let me do it (I need to figure out how to do this one since I need to adjust the size of controls for the other language). I don't think that's the cause since the localized user control that contain that information ($this.Localizable) generated by VS in its resource file didn't react when inserted in a ModuleDialogPage.
Any information about the subject will be greatly appreciated.