Application Designer uses CSV files as the default implementation for storing translation information. In some scenarios, you do not want Application Designer to be responsible for storing this information, but want to store translation information on your own.
Example: you may already have a text database within your existing application, and you may already have defined procedures on top of this: translation tools, automated translation etc.
Application Designer provides an interface
com.softwareag.cis.multilanguage.IMLManager that is
internally used for accessing translation information:
public interface IMLManager
public void refreshBuffers();
public String getString(String language,
String project,
String application,
String literal);
public boolean checkIfExists(String language,
String project,
String application,
String literal);
public String getString(String language,
String project,
String application,
String literal,
String[] embeddedStrings);
public String[] getApplicationStrings(String language,
String project,
String application,
String[] textIds);
}
See the JavaDoc API documentation for detailed information.
You can implement this interface by a class of your own and register this class in the Application Designer runtime environment. The registration is done inside the cisconfig.xml file:
<cisconfig ...
multilanguagemanager="<your implementation>"
...>
Be aware of the fact that the interface is a pure "access interface" that is used at runtime; i.e. whenever Application Designer requires information about a certain text ID, the interface is called. The interface currently does not provide methods for writing text information back, i.e. there is no coupling of Application Designer's multi language tools (e.g. translation inside the Layout Painter).
