idl_type=IDL Type
corba_idl=CORBA IDL
com_idl=COM IDL
open=Open
select_folder=Select folder
dialog_title=Generate IDL
current=Current
current_w_subpackages=Current with subpackages
all=All
selected_only=Selected only
output_directory=Output directory\u0020
options_ellipsis=Options...
packages=Packages
# Config pane option names
filter_by_stereotype=Filter by stereotype
include_interfaces=Include Interfaces
include_classes=Include Classes
process_attributes=Process Attributes
process_links=Process Links
process_publics_only=Process Public Members Only
process_imports=Process Imports
process_cardinality=Process Cardinality
convert_std_types=Convert Standard Types
use_module_statements=Use Module Statements
module_prefix=Module prefix
interface_suffix=Interface suffix
create_subdirectory=Create IDL subdirectory
one_file_per_module=One file per module
use_long_filenames=Use long file names
output_directory=Output directory
suppress_warnings=Suppress warning messages

description.filter_by_stereotype=When set to true only classes, interfaces and members with respective stereotypes\
 will be processed. For instance, classes may get \
 <code>&lt;&lt;Idl-Interface&gt;&gt;</code>,\
 <code>&lt;&lt;union&gt;&gt;</code>, \
 <code>&lt;&lt;enum&gt;&gt;</code>, \
 <code>&lt;&lt;struct&gt;&gt;</code> and \
 <code>&lt;&lt;exception&gt;&gt;</code> \
 stereotype. See the description of IDL Export script for all used \
 stereotype names. This is a recommended option.

description.include_interfaces=Map model interfaces into IDL interface \
 declarations. If this option is not set, model interfaces will not be \
 exported. \
 See also <b>Filter by Stereotype</b> option.

description.include_classes=Map model classes into IDL interfaces. \
 If this option is not set, model classes will not be exported. \
 See also <b>Filter by Stereotype</b> option. 

description.process_attributes=Map class attributes to IDL attributes. \
 If this option is set, attributes of classes and interfaces being \
 processed will be exported and mapped to corresponding IDL interface \
 fields. The effect of this option also depends on \
 <b>Process public members only</b> option.

description.process_links=Map association links into IDL attributes. \
 If this option is set, association links drawn between classes will \
 be mapped in output interfaces as attributes. Otherwise, the links are \
 ignored.

description.process_cardinality=Convert links to arrays or sequences \
 according to supplier cardinality value. Below is the table that shows \
 cardinalities and corresponding types <br> \
 <table width="70%" border="0"> 									\
   <tr>																\
     <td><b><font size="-1">Supplier Cardinality</font></b></td>	\
     <td><b><font size="-1">Generated IDL Type</font></b></td>		\
   </tr>															\
   <tr>																\
     <td><font size="-1">0</td>										\
	 <td><i><font size="-1">no code generated</font></i></td>		\
   </tr>															\
   <tr>																\
     <td><font size="-1">0..n</td>									\
	 <td><code>sequence &lt;type, n&gt;</code></td>					\
   </tr>															\
   <tr>																\
     <td><font size="-1">n..m</td>									\
	 <td><code>sequence &lt;type, m&gt;</code></td>					\
   </tr>															\
   <tr>																\
     <td><font size="-1">n</td>										\
	 <td><code>sequence &lt;type&gt;</code></td>					\
   </tr>															\
   <tr>																\
     <td><font size="-1">*</td>										\
	 <td><code>sequence &lt;type&gt;</code></td>					\
   </tr>															\
   <tr>																\
     <td><font size="-1">0..n</td>									\
	 <td><code>sequence &lt;type&gt;</code></td>					\
   </tr>															\
   <tr>																\
     <td><font size="-1">n</td>										\
	 <td><code>type[n]</code></td>									\
   </tr>															\
 </table>								

description.process_publics_only=Export only public classes and members. \
 When this option is set all private, protected and package local entities \
 will be ignored during export.


description.process_imports=This option is not implemented yet.

description.convert_std_types=Convert types that are standard for the \
 language of the model into standard IDL types. For example, \
 <code>java.lang.String</code> would be converted into <code>string</code> \
 and <code>long</code> would be converted into <code>long long</code>.

description.use_module_statements=Generate IDL interfaces inside module \
 scopes, retrieving module names from package names. \
 For example, an interface produced after the class \
 <code>org.company.Sample</code> would have this wrapping around it:\
 <pre> \
 module org { 					\n\
   module company { 			\n\
     interface Sample { 		\n\
	 ... 						\n\
	 }	 						\n\
   } 							\n\
 } 								\n\
 </pre>

description.module_prefix=When specified, all modules will be automatically prefixed with defined value. \
For example if <code>foo::bar</code> is \
entered here, all interfaces located in default package will get into module <code>foo::bar</code>. \
Effect of this prefix is global, both elements with <code>@idlModule</code> and the ones without will be prefixed.

description.interface_suffix=Interface suffix is appended to all \
 generated interface names. \
 Using interface suffix makes sense when you're generating IDL files to \
 the same directory where your \
 source model files are, thus avoiding interference with original \
 files after compilation.

description.create_subdirectory=This option allows separate source files generated by \
 IDL-to-language compiler from files used as source for IDL script.\
 In C++-based projects, if this option is set to true generated idl files are placed \
 into idl subdirectory of the package directory. Otherwise .idl files are generated \
 right in the same directory where model files are stored. It is recommended to leave this \
 option set to true.

description.one_file_per_module=Generated IDL Entities can be placed in separate \
files or one file can be used per module


description.use_long_filenames=Generate .idl files with long names based \
 on fully qualified names of classes or interfaces. It is recommended to use \
 this option of there is a chance of overlapping names in packages that \
 are to be processed.

description.output_directory=Output directory for generated IDL files. \
 If <b>Create IDL subdirectory</b> option is set, subdirectory called \
 <code>idl</code> will be created in this directory.

description.suppress_warnings=Be quiet, do not produce any messages during model processing.

