Skip to main content

Open-source localization for Delphi

# Build multilingual Delphi applications with no cloud dependency.

Delphi App Translation Studio scans VCL and FireMonkey projects, creates reviewable translations, validates the result, and exports compact JSON language packs that work offline in the finished application.

Download the Beta source Read the User Guide
Beta test software
Read the guides before you download, build, or use the Studio.

This release is intended for controlled developer evaluation during active Delphi development. Begin with a version-controlled test copy, follow the Setup Wizard Guide, and inspect every translated screen and generated output before considering production use.

User Guide Setup Wizard Guide All documentation
An actual Studio screen: review source entries, translation context, suggestions, and approval status.
VCL + FMX One localization workflow
DeepL + Google Developer-time providers
Offline JSON No end-user API key
Apache 2.0 Open-source licensing

A development tool, not an EXE translator

## Localization stays inside the development process.

Run the Studio while forms, resources, messages, and layouts can still be examined in Delphi. Rescan as the application changes, preserve translations that still match, and send only new or revised eligible text to the provider.

Machine translation can be very useful, but it cannot guarantee perfect wording or layout. The developer remains responsible for terminology, dynamic messages, custom controls, right-to-left behavior, and final visual review.

Guided from source to deployment

## A controlled path from Delphi project to offline language pack.

The Setup Wizard handles the repeatable work and keeps the important decisions visible.

01
P

### Select the project

Detect the application identity, VCL or FMX framework, forms, source units, targets, and normal build outputs.

02
A

### Scan and translate

Build a stable catalog from saved forms and approved Delphi text, then translate unresolved entries with DeepL or Google.

03
✓

### Review and validate

Inspect terminology, placeholders, source changes, language direction, and conservative layout proposals before export.

04
{ }

### Integrate and deploy

Generate the VCL or FMX component kit and place compatible source and target packs beside the intended executable.

Translation with application context

## Short interface words need more than a dictionary.

“Play,” “Close,” “Schedule,” and “Enable” can mean different things in different applications. The Studio adds proper context, control roles, surrounding evidence, terminology, and review status with each entry.

- Preserves approved and reviewed work during later scans
- Protects Delphi placeholders, accelerators, identifiers, and markup
- Uses project glossary and translation-memory evidence
- Separates machine drafts from human review and approval

Source text Play
Control role Media action
Wrong context Theatrical performance
Approved meaning Start playback

Context confidence High

The Studio keeps first-time setup and ongoing maintenance as distinct workflows.

Designer-owned integration

## Normal Delphi components. Offline application runtime.

Place one framework-appropriate language manager and one connected selector on the primary form. Their published properties remain visible in Object Inspector, and ordinary forms are managed through the application lifecycle.

Source stays readable The recommended workflow does not rewrite Pascal, DFM, FMX, DPR, or DPROJ source.
Switching is reversible The runtime restores the designer baseline before applying the next language.
Layout is language-aware LTR, RTL, wrapping, intelligent hyphenation, and reviewed layout rules are applied conservatively.

Built around valuable source code

## Safety is part of the workflow, not a final checkbox.

1

### Read-only discovery

Project detection and scanning inspect saved source without executing it.

2

### Explicit authorization

Final processing begins only after the project, backup, and intended actions are reviewed.

3

### Atomic project data

Catalogs, packs, settings, glossaries, and preferences use validated replacement and recovery files.

4

### Offline trust boundary

Provider keys stay on the developer computer and never belong in the target application.

Limited Beta testing is open

## Help test multilingual Delphi applications in real development projects.

This is Beta test software, not a production release. Read the current guides first, build from source, work on a safe project copy, and report functional, layout, translation, RTL, and documentation issues without sharing private source or credentials.

Read the Beta guides Download the Beta source Report a Beta issue