This page is available by selecting Preferences > Discovery Preferences
In this page you can organize the supported language for automatic discovery purposes.
Auto discovery uses the file naming policies selected during discovery to auto detect the supported languages for a discovered asset based on the file name of the asset discovered
Selecting a group in the top pane displays the actual real devices in this group in the lower pane.(Shown in Caption 1:)
Managing the discovery languages is identical to the channel language pages and is outlined in Channel Supported Languages. A language group is typically a group with a 'group name' containing 'real' locales. What this means during the discovery operation is that Metaflow will review the discovered assets filename, filling in the supported 'real' locales in the discovery wizard for the asset if the file name contains the group name. For example, a discovery language group is named 'efigs' containing the locales 'en','sp','de','fr' and 'it' and during discovery Metaflow sees an asset named killerapp_efigs.jad.
The discovery process will have filled in the supported locales on the discovery wizards assets data page for that asset.
Should Language mappings have been set up incorrectly or not exist in the discovered assets file name then the user can manually add the supported languages during the new Midlet packager project wizard page, or use the bundle editor after discovery to correctly update the data as required.
Language mappings can also be added to all or some particular devices using the much more powerful Filtered Actions.