The term MRI isolation has two meanings as follows:
The former achieves ease of translation. On the other hand, the latter achieves MRI switching at runtime. This section describes the former MRI isolation. The next section will describe the latter case.
┌──────────────────────────────────────────────────────────────────────┐│Utilize PM facility such as the resource compiler and IPFC to create │ │MRI so that you can isolate MRI from the source code. │ └──────────────────────────────────────────────────────────────────────┘
Since a translator is not a programmer in general, it is difficult to distinguish MRI from program codes. Moreover, you need to modify the program whenever you need to support another language.
PM provides some facilities to generate program resources as an isolated module. All resources related to panels (e.g. dialog windows, menus and strings represented onto the panels) can be stored in a resource file which can be compiled with the resource compiler. Help resources can be compiled by IPFC (refer to IPFC (Information Presentation Facility Compiler)).
MRI isolation has another merit for version control of your product. If your source code contains an MRI information, you need to prepare one source code per language. If there is a change in logic, you need to reflect the change to all source codes.