V7 languages and reports
VCL2FMXConverter v7.0 Atlas. Updated October 15, 2026.
Choose a language
Use the Language selector in the header. The 35 bundled language packs work offline. The selection is saved for the next launch. Product names, Delphi identifiers and source evidence retain their original spelling.
Conversion output
Live messages are translated for display. The language selected at the start of a conversion is captured for its saved HTML and text reports. A later language change does not rewrite an existing report. JSON remains canonical English with the stable vcl2fmx.report.v1 schema.
Generated Pascal and FMX application content is not translated into natural languages. Built-in interface and report messages use machine-generated translations; custom mapping-pack notes and external exception messages may remain original. The Help button opens the installed manual in the selected interface language. Translation requires Internet access; English Help remains available offline. Keep Atlas running while navigating Help.
Dry-run preview and outcomes
A dry run can write reports and create the output folder, but it preserves existing build/history folders and does not write converted source. An unreadable Pascal input produces a blocking issue. Mapping-pack loading diagnostics are retained. Report buttons refer only to reports successfully written during the current run.
Portable installation
Extract the complete release ZIP. Keep Localization/Languages, mapping_packs and docs/Help beside the executable. Use a dedicated output folder for ordinary conversions.
Source and output safeguards
Select one project folder and a separate, dedicated output folder. Relative paths are resolved before conversion. If multiple project files are found at the selected level, select a narrower folder. A DPR and DPROJ must refer to the same main program. Empty selections, unreadable folders and directory links or junctions in scanned trees are blocked before output cleanup. Use ordinary folders for conversion; the source remains unchanged.
Source text encoding
UTF-8 with or without a byte-order mark and UTF-16 are supported. For legacy Pascal source, an explicit {$CODEPAGE 1251} or other supported numeric code-page directive identifies its encoding. Without a byte-order mark or directive, valid UTF-8 is preferred and other legacy bytes default to Windows-1252; other legacy encodings cannot be inferred reliably. Save such files as UTF-8 in Delphi before conversion. Generated Pascal source uses UTF-8 and its code-page directive is updated accordingly.
Before relying on converted output
Review all blocking and manual-review findings, compile the generated project in Delphi, and test its behavior.
Interface terminology
- Project Scan
- The page where you choose the source project, output folder and conversion options. Start the conversion with Convert Project.
- Conversion Output
- The page containing the live conversion log and report status. Open Report opens the saved report from the current run.
- Rules
- The rule-family switches used for the next conversion. The Dashboard and Current rule state summaries use the same names as these switches.
- Dry-run preview
- Inspects the conversion without writing converted source or project files. Reports may still be written and the output folder may be created.
- Language packs and mapping packs
- Language packs translate displayed text. Mapping packs define conversion rules; editing a translation does not change a conversion rule.
Report a translation correction
Include the converter version, the language and locale shown in the Language selector, the screen or Help topic, the exact current wording, and your suggested wording. Explain the correction if helpful.
For clipped or overlapping text, also include the window size and Windows display scaling. Crop screenshots to the affected text and remove private paths, names and project information.
Email a translation correction. This opens a message template in your email application; nothing is sent automatically. You can also edit translations and glossaries using the Delphi App Translation Studio.
For the complete procedures for editing translations, adding languages, maintaining glossaries and installing packs, see Using and maintaining translations.