Cause: FORMS60_CHARACTER_SET mismatch with OS codepage.
Solution: In Windows Control Panel -> Region -> Administrative -> Change system locale to Arabic (Saudi Arabia) or Urdu (Pakistan). Reboot.
| Component | Setting | Status |
|-----------|---------|--------|
| Database character set | AR8MSWIN1256 or AL32UTF8 | ☐ |
| NLS_LANG client | ARABIC_EGYPT.AR8MSWIN1256 | ☐ |
| Windows OS language pack | Arabic/Urdu installed | ☐ |
| Forms property Right To Left | Yes | ☐ |
| Text item font | Arial / Tahoma | ☐ |
| Test insert & select | Shows correct text | ☐ |
| Printing (Report) | RTL + correct font | ☐ |
Set the NLS_LANG environment variable/registry key to match database character set.
Format: NLS_LANG = LANGUAGE_TERRITORY.CHARACTER_SET Cause : FORMS60_CHARACTER_SET mismatch with OS codepage
For Arabic:
NLS_LANG = ARABIC_EGYPT.AR8MSWIN1256
For Urdu (using Arabic locale):
NLS_LANG = ARABIC_EGYPT.AR8MSWIN1256
Location (Windows Registry):
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_Dev6iHome\NLS_LANG
(or under HKEY_CURRENT_USER\Software\Oracle) Set the NLS_LANG environment variable/registry key to match
Developer 6i relies heavily on Windows Registry settings and environment variables to determine how to interpret and render data.
Windows doesn’t natively support Urdu keyboard in older systems. You must:
For Reports 6i to output Arabic/Urdu to PDF or printer: For Urdu (using Arabic locale): NLS_LANG = ARABIC_EGYPT
This is the most common point of failure. Simply typing in Arabic often results in Left-to-Right alignment, breaking the visual logic.
Configure the following properties for every Text Item:
When launching your form, use:
ifrun60.exe module=my_form.fmx NLS_LANG=ARABIC_EGYPT.AL32UTF8