I am starting to localize a project (English/Spanish) and noticed that the SF labels have a Task facility to automatically create a Localization Key in the Default Language project, but for other controls like the Form's Text, GradientFormHeader Title, ThemedGroupBox, ListView Column Text, does not have this kind of facility, or at least I have not found an easy way to auto-create those localization keys.

So my question is how to handle those controls other than Labels to auto create the localization keys? specially for ListView columns headers.

Thanks!

It is a bit messy this way, if this has to be done for each BrowserDialog and each ListView, then it does not make sense.

Trent, Ivan, can you confirm if this is the only way to deal with localization for these controls?

The form, ThemedGroupBox, GradientFormHeader, etc. all have localization properties.

1. Form - LocalizationKey and PropertyToLocalize
2. GradientFormHeader - TitleLocalizationKey, DetailTextLocalizationKey
3. ThemedGroupBox - same as form

If you will show the property sheet in category mode instead of alphabetic, you will see that there is an SF category called, "StrataFrame: Localization" with the related properties.

However, a ListView column and BD labels will have to be done manually with the retrieve text method like Juan explained.

But why these controls ListView Columns and BD Labels does not have a LocalizationKey property? 

It is important to me to understand how a feature works so I can get the most benefit out of it.

Also, is there an event that will be fired when using Localization.ShowAvailableLanguages() so the currently opened forms would be shown with the selected language? 

Still I would like to know about this: