Developer 6i does not auto-map fonts for Arabic shaping.
Step 1: Choose a Unicode/Arabic font installed on Windows, e.g.:
Step 2: Configure Forms runtime
In forms90.cfg (or forms60.cfg for 6i):
FONT=Arabic Transparent
FONTSIZE=10
Step 3: Configure Reports
In reports60.cfg:
FONT=Arabic Transparent
FONTSIZE=10
Step 4: Set RTL layout property in each form
For each canvas, text item, and button:
When launching your form, use:
ifrun60.exe module=my_form.fmx NLS_LANG=ARABIC_EGYPT.AL32UTF8
Correct data storage is insufficient without correct visual rendering. Developer 6i Forms require specific property changes at the Item and Canvas levels.
For text items intended to display Arabic or Urdu:
Limitation: Dev6i cannot display complex script shaping (like initial/medial/final forms of Urdu characters) fully in all versions. Basic Arabic works reliably; Urdu may show disconnected glyphs.
Set these in the Form Property Palette:
| Property | Value |
|---|---|
| NLS_LANG | ARABIC_EGYPT.AR8MSWIN1256 |
| NLS_DATE_FORMAT | DD/MM/YYYY (or Arabic-enabled format) |
| NLS_SORT | ARABIC |
| NLS_COMP | LINGUISTIC |
Arabic and Urdu reports often face issues where characters appear disjointed (scrambled) or output as question marks.
For each text item that will hold Arabic/Urdu:
| Property | Setting |
|---|---|
| Case Restriction | None |
| Keyboard State | ARABIC (if available) |
| Justification | Right |
| Direction | Right-To-Left (in later FMB properties) |
| Font | Arial, Times New Roman, or Simplified Arabic |
| Character Set (if shown) | AR8MSWIN1256 | Developer 6i does not auto-map fonts for Arabic shaping
Fallback for Urdu specific glyphs: Try Noto Naskh Arabic or Urdu Typesetting font installed on Windows.