The A typical application module structure shows a typical module structure of an application program. A well designed program structure separates its program resources from its handling method modules. The following portions are related to the DBCS enabling:
The control resource or the environment identifies information. This is a group of information that describes what is the current environment is.
The methods or logic that is used to handle a function requested by the user. Some functions need to handle DBCS, but some are not.
Some functions do not need to handle the DBCS in their logic, but need appropriate resources that can handle the DBCS correctly.
(*4) country code (*1)
┌─────────┐ ┌───────────┐ code page (*1)
│ Initial │ │ Control │ language ID (*1)
│ Process │ ─── │Information│ SBCS/DBCS (*2)
└─────────┘ └───────────┘ DBCS environment vector (*2)
User │ │ │
Inter─ │ │ Device caps (*3)
face ┌─────────┐ │ │ Setup information *.INI (*3)
│ Main │ │ │ System Font Size (PM) (*3)
── │ Routine │ │ │ Dialog Unit size (PM) ... (*3)
│ Module │ │ │
└─────────┘ │ │
│ │ │
(*4) (*4)
┌─────────┐ ┌──────────┐ MRI/message files/string tables (*1)
│ Handling│┐ │ Handling │┐ Dialog resource (*1)
│ Method ││┐─── │ ││┐ for each code page...
└─────────┘││ ─── │ Resource │││ Font data (User preference) (*3)
└─────────┘│ ───└──────────┘││
└─────────┘ └──────────┘│
│ └──────────┘
┌─────────┐
│Terminate│
│ Process │ NOTE: (*1) : NLS resources
└─────────┘ (*2) : DBCS resources
(*3) : Application resources
(*4) : Portion required modification or creation
for DBCS enabling
A typical application module structure