localization of DevExpress LayoutControl Component - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ...

Support forum of the software localization tool Sisulizer

Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Not logged in - Login | Register

Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > localization of DevExpress LayoutControl Component

Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius

New Topic

Printer Friendly

localization of DevExpress LayoutControl Component - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ...

Author

Post

Posted: Wed Mar 26th, 2008 10:32 am

Quote

Jean-Luc
Member

Joined:	Wed Mar 26th, 2008
Location:
Posts:	3
Status:	Offline

Hi,

i'm using the latest version of Sisulizer 1.6.22 and for our .Net/C# projects we are using most of the DevExpress components. After we change the strategy of building usercontrols based on the LayoutControl component from DevExpress, Sisulizer is no longer able to find the components enclosed by this LayoutControl.

Here is an example of a designer file:

private DevExpress.XtraLayout.LayoutControl layoutControl1;

private System.Windows.Forms.Label lblKostenProTeilnehmer;

private System.Windows.Forms.Label lblAnzahlTeilnehmer;

private System.Windows.Forms.Panel panel2;

private System.Windows.Forms.Panel panel3;

private System.Windows.Forms.Panel panel4;

private System.Windows.Forms.Panel panel5;

private DevExpress.XtraLayout.LayoutControlGroup layoutControlGroup1;

private DevExpress.XtraLayout.LayoutControlGroup layoutControlGroup5;

private DevExpress.XtraLayout.LayoutControlItem layoutControlItem13;

private DevExpress.XtraLayout.LayoutControlItem layoutControlItem14;

private DevExpress.XtraLayout.EmptySpaceItem emptySpaceItem4;

private DevExpress.XtraLayout.LayoutControlGroup layoutControlGroup6;

private DevExpress.XtraLayout.LayoutControlItem layoutControlItem18;

private DevExpress.XtraLayout.LayoutControlItem layoutControlItem19;

private DevExpress.XtraLayout.LayoutControlItem layoutControlItem20;

private DevExpress.XtraLayout.LayoutControlItem layoutControlItem21;

}

Are there any informations about this control and its child controls?

regards,

Jean-Luc

Quote

Posted: Wed Mar 26th, 2008 10:37 am

Quote

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Tokyo, Japan
Posts:	1641
Status:	Online

Are you using assembly localization (added .exe to SL project) or project localization (.csproj or .sln)

Can you send the form file (.resx file and both .cs files) to

support (at) sisulizer.fi

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Quote

Posted: Wed Mar 26th, 2008 11:04 am

Quote

Jean-Luc
Member

Joined:	Wed Mar 26th, 2008
Location:
Posts:	3
Status:	Offline

hi Jaakko,

we localize an assembly (exe + dll). I send the files you requested

regards,

Jean-Luc

Quote

Posted: Wed Mar 26th, 2008 10:20 pm

Quote

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Tokyo, Japan
Posts:	1641
Status:	Online

Thank you for the files. If found the reason. This form and many other has Localizable property value set to False. When the value is False Visual Studio does not store property values to the resource file (.resx) but hard codes them to source code file (.cs).

This is from online help

.NET's Localizable property
In order to localize a .NET application each form or user control of the application has to have Localizable property set true. This makes the IDE to store the properties of the form in the .resx file instead hard coding them to the source code. Having the resources in the .resx file makes localization possible.

To change the Localizable property true open your project, select each form and user control and make sure that Localizable property is set to true.

If you localize a project or solution file (e.g. .csproj or .sln) save your application project and [url=mk:_(at)_MSITStore:D:\SL1\Bin\Sisulizer.chm::/ProjectScanMenu.htm]rescan[/url] your Sisulizer project. If you localize an assembly file (e.g. .exe) recompile your application and then rescan your Sisulizer project.

Jaakko

Attachment: Localizable.PNG (Downloaded 14 times)

____________________
http://www.sisulizer.com - Three simple steps to localize

Quote

Posted: Fri Mar 28th, 2008 11:48 am

Quote

Jean-Luc
Member

Joined:	Wed Mar 26th, 2008
Location:
Posts:	3
Status:	Offline

thanks for the advice, its embarassing

we enabled the localization property and saw the controls in sisulizer. Items in this layout control have a text-property to deal as an associated label. This one can't be seen on your visual editor. As it is available for translations its ok so far.

Thanks a lot

Quote

Current time is 04:28 am
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > localization of DevExpress LayoutControl Component

Sisulizer software localization tool - Three simple steps to localize