StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9229902
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-10T15:11:32.627
FavoriteCount
0
LastActivityDate
2012-02-10T15:29:28.680
LastEditDate
2012-02-10T15:29:28.680
LastEditorUserId
251386
OwnerUserId
251386
ParentId
8784686
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
please use the second method you've mentioned. <blockquote> I got some advice that I should simplify the whole localization process, by setting the "localizable" property to true and make the translations done. And most of the tutorials follow this way. </blockquote> Because this is the intended way of how Microsoft think localization should be done in a winforms app. <a href="http://msdn.microsoft.com/en-us/library/y99d1cd3%28v=vs.90%29.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/y99d1cd3%28v=vs.90%29.aspx</a> One problem with your first solution: How do you maintain that a text in another language will be displayed correctly? That's one of the occuring problems, Microsoft have been aware of. With a small tool found in the SDK called: WINRES.exe you can see the designed forms and write the translation for them. <a href="http://msdn.microsoft.com/en-us/library/8bxdx003%28v=vs.90%29.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/8bxdx003%28v=vs.90%29.aspx</a> If you want to change the language on runtime and update all forms this article maybe a hint for you: <a href="http://msdn.microsoft.com/en-us/magazine/cc163609.aspx#S9" rel="nofollow">http://msdn.microsoft.com/en-us/magazine/cc163609.aspx#S9</a> The following lines gives an explain howto update you UI: <pre><code>Dim crm As ComponentResourceManager crm = New ComponentResourceManager(GetType(Main)) crm.ApplyResources(cmdAddCustomer, cmdAddCustomer.Name) crm.ApplyResources(mnuFile, mnuFile.Name) crm.ApplyResources(mnuFileAddCustomer, mnuFileAddCustomer.Name) </code></pre> The last 3 lines of this code can be found in each form (localizable = true) in the designer file. So you can specify an interface for an update method, which every form should implement, implement the interface and after language change iterate the through all forms and call these method. Hope this might help you ...
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLoad all localization resources on startup
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. US70sCommander
UserOwnerUserId
1. US70sCommander
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.