Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Internationalization / November 2006

Tip: Looking for answers? Try searching our database.

Localization and form layout

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Dale - 15 Nov 2006 03:10 GMT
In localizing a Windows Form application, is it best to always use the Resize
event and then calculate the size of all controls based on the localized
strings and manually lay out the form?  

Or do most of you try to do your translations so that they fit a common size
for labels, buttons, etc?

Signature

Dale Preston
MCAD C#
MCSE, MCDBA

Mihai N. - 15 Nov 2006 04:27 GMT
> In localizing a Windows Form application, is it best to always use the
> Resize
> event and then calculate the size of all controls based on the localized
> strings and manually lay out the form?  
Use layout managers (FlowLayoutPanel, TableLayoutPanel) and properties like
AutoSize, AutoSizeMode, docking/anchors, and let them do the work.

> Or do most of you try to do your translations so that they fit a common
> size for labels, buttons, etc?
Definintely not. This is guarantee for bad localization.

Signature

Mihai Nita [Microsoft MVP, Windows - SDK]
http://www.mihai-nita.net
------------------------------------------
Replace _year_ with _ to get the real email

Dale - 16 Nov 2006 02:23 GMT
Thanks for your reply.  What do you do when your autosized controls don't fit
the form?  Do you have to resize the form as well?

Is it possible to get too carried away with localization?

Thanks in advance,

Dale

Signature

Dale Preston
MCAD C#
MCSE, MCDBA

> > In localizing a Windows Form application, is it best to always use the
> > Resize
[quoted text clipped - 6 lines]
> > size for labels, buttons, etc?
> Definintely not. This is guarantee for bad localization.
Mihai N. - 16 Nov 2006 05:34 GMT
> Thanks for your reply.  What do you do when your autosized controls don't
> fit the form?  Do you have to resize the form as well?
The form also has the AutoSize attributhe, but to be fair I was not really
able to take advantage of it. But yes, is best if you find a way to resize
the form.
I find it easyer to design the forms for auto-layout, localize the string
part, then just manualy resize a bit for the languages, if needed.
If the autolayout is done right, there is very little work. It really pays
if you have many languages.

> Is it possible to get too carried away with localization?
Like with everything else, the answer is probably yes :-)
But in my experience, the better the English, the easyer the localization.
Everything you do for a good English (clean dialogs, autolayout, clear
language and terminology) also helps languages.

Signature

Mihai Nita [Microsoft MVP, Windows - SDK]
http://www.mihai-nita.net
------------------------------------------
Replace _year_ with _ to get the real email

Jaska - 15 Nov 2006 12:58 GMT
Hi,

The best way it to modify to original layout each time you import
translations. If some translation does no fit and the translator has
reshaped the UI you should do the same change to the ORIGINAL file. When
localizing to the next language it is less likely that the translator need
to change the UI.

I have experience translating a large application to German, French,
Japanese, Finnish and Russian. After doing German, Finnish and Japanese
translations French and Russian did not need any layout changing. Most
likely the next translations will be translate-only!

Less the translators need to do layout changing cheaper the localization
will be. A properly internationalized UI also looks good!

Some guidelines about UI design:
http://www.sisulizer.com/translation/vcl/delphi.shtml
This is for Delphi but the same principles are valid for .NET. By following
this you will cut at least to half the need of your layout changing when
translating UI.

Best regards,
Jaakko Salmenius
www.sisulizer.com
Dale - 16 Nov 2006 02:25 GMT
Thanks for the tips.  Already, based on what I learned reading your site, I
am making changes to my forms.  Luckily, it's early in the localization
process so most of my forms, I can implement your ideas from the beginning.

Dale
Signature

Dale Preston
MCAD C#
MCSE, MCDBA

> Hi,
>
[quoted text clipped - 21 lines]
> Jaakko Salmenius
> www.sisulizer.com 

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.