Hi,

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!

Edhy Rijo

Actually, this is only partially correct.

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.

Hi Trent,

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? 

Edhy Rijo

Edjy



Take a look to the Localization sample, they do what you asking for:







Regards

Everything is possible, just keep trying...

Juan is on top if it today!

Thanks Juan, Trent.

Still I would like to know about this:

Edhy Rijo

Because these are enumerated values.  The Search fields on the BD, maybe at some point.  But eh columns on teh ListView are standard .NET ListViewColumns...not SFListViewColumns.  So for this to work on a ListView we would have to create our own columns types...so at this point we may as well not inherit from the ListView at all and write our own...which a localization key is DEFINITELY not worth that kind of energy.  Maybe the next version of the ListView.

Thanks for the explanation, I think I understand now why not all .NET controls are SF subclassed.  I am sure this would be a good enhancement for those using the localization engine in future versions.

Edhy Rijo