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 / Windows Forms / WinForm General / October 2007

Tip: Looking for answers? Try searching our database.

localization - disabling the localization of control properties?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Sergei Shelukhin - 25 Oct 2007 15:51 GMT
Hi. Is there any way to prevent standard .NET localization from
"lozalizing" control locations and sizes? Or, preferrably, all the
properties that are put into "other" resource type in resources.

We have an application where the changes to control positions on the
form are done very often as new contrls are added to the forms, via
GUI editor, and having to change control position over and over in
each and every anguage file is annoying as HELL.
There's also a problem with those "other" values not being read by
ResXResourceReader, so we cannot syncronize it easily, I wonder if
there's a way that is better than writing an Xml-based sync.
Grant Frisken - 25 Oct 2007 23:52 GMT
The Visual Studio forms designer only writes out resource values to
the language specific resx files if the value is different from the
invariant.   So provided you don't open the designer in say French and
move controls around, the control positions should not get written out
to French.   Unfortunately because of the way the designer remembers
the last language edited, it is very easy to accidently open a form
(not realizing that it is language specific) and then make changes
that result in the control positions being saved.  Unfortunately
Visual Studio doesn't provide any easy way of resetting these langauge
specific resources back to the invariant value once this has
occurred.   You basically have to edit the resx.

You might be interested in taking a look at Infralution's
Globalizer.NET product.  This makes the whole process of localizing
forms and controls much easier.   You can choose to just localize
certain types of resources (eg strings and icons).   Globalizer.NET
will then generate the language specific resx files for you -
eliminating the frustration you are currently having.   You can get
more information and download an evaluation version from
www.infralution.com/globalizer.html

Regards
Grant Frisken
Infralution

> Hi. Is there any way to prevent standard .NET localization from
> "lozalizing" control locations and sizes? Or, preferrably, all the
[quoted text clipped - 7 lines]
> ResXResourceReader, so we cannot syncronize it easily, I wonder if
> there's a way that is better than writing an Xml-based sync.

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.