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 / March 2005

Tip: Looking for answers? Try searching our database.

Control's Resizing, Without making the form layout unpresentable

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Shahzad Atta - 04 Mar 2005 11:06 GMT
Hi All,

I am working on internationalizing my app. I have all the resources and
structure in place but I am unable to figure out the best way to handle
control resizing in order to accommodate localized strings which are larger
then the English version.

One way to do this is to provide ample room in the controls but that's make
my form in English look unpresentable.
Another way is to dynamically handle the size of control but that seems a
bit tricky. The size of string in not known until runtime. what would be the
limit. Controls overlapping and those sort of issues.

So any idea, best practice I can follow to get things done. I greatly
appreciate any idea being posted.

Regards,
Shahzad Atta
Mihai N. - 05 Mar 2005 05:36 GMT
> One way to do this is to provide ample room in the controls but that's make
> my form in English look unpresentable.
> Another way is to dynamically handle the size of control but that seems a
> bit tricky. The size of string in not known until runtime. what would be the
> limit. Controls overlapping and those sort of issues.
100% right.

Dialogs are resized after translation. This is why the .rc files
are considered localizable and store dialog coordinates.
Otherwise you would just localize a .txt file with pairs id-string.
It is impossible to design a dialog that is good enough for 20 languages
and looks good in any of them.

Best idea is to provide ample room, but without making the original
language look bad:
http://www.microsoft.com/globaldev/getwr/steps/wrg_uiloc.mspx

This will make resizing the localized versions way easier,
but will not eliminate the need or resizing.

To help for future versions, many professional localization tools
are able to leverage more than text from one version to another.
They can handle coordinate information, bitmaps, fonts, icons, etc.

Just take care not to change every single dialog from one
version to the next :-)

Another option is to use some smart auto-layout system.
Many tried, and many failed :-)
It is possible, but it is a lot of work and you should
expect a lot of troubles until it is fine tuned well enough
to be good for any language.

Signature

Mihai Nita [Microsoft MVP, Windows - SDK]
------------------------------------------
Replace _year_ with _ to get the real email

Marin Millar - 22 Mar 2005 19:33 GMT
Yes, as Mihai mentions, in version 1.0 and 1.1, the best way is to use a
localization tool or the VS designer for resizing localized controls.  
However, in our next version (VS 2005), we do have some controls which help
with automatic resizing according to text size.  If you're interested, take
a look at VS Beta 2, to be release sometime in April.  The controls which
are interesting for this scenario are TableLayoutPanel and FlowLayoutPanel.
Marin Millar [MSFT]

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.