LocalizeAdder QT

Overview

LocalizeAdder _ QT is a professional All- in-One Localization Manager for audit, validation, repair and multilingual translation of localization files. The tool supports both the old Python-based structure (.py) and the new modern text format (.localize).

• Audit of localization files: Statistics, language comparison, integrity control
• ♪ 6 providers with intelligent fallback
• Validation of the structure: Detection of duplicates, missing keys, structural problems
• Language synchronisation: Automatic repair and synchronization
• Management of new languages: Add with automatic translation from 60 + languages
• graphical interface + batch mode: Professional Qt5 graphical interface for operators, batch mode for automation

Function

graphical interface Layout, Control & Keyboard Shortcuts

Main window (QMainWindow) structure:

Bookmarks (detailed content of each):

📊 AUDIT: Summary of statistics (number of languages, keys, problems), Recent audits table, Health status indicator (green / yellow / red), Quick actions buttons (Run Audit, Export Report)

🌍 LANGUAGES: Table of all languages (Flag 124; Code 124; Name 124; Total Keys 124; Missing 124; Extra 124; Duplicates 124; Completeess%), filtering, sortable, per- language events (Edit, Translate, Sync)

🔄 FALLBACK: CZ vs EN comparison, list of missing keys in CZ / EN, duplicity report (with number of occurrences, lines), Missing in code, Unused in code

📐 STRUCTURE: Key order, per-language list with problems (missing # comments, whitespace issues, format error), preview of lines with error

🌐 TRANSLATION: Selection of language target, provider selection, SmartTranslate checkbox, progress bar, table of candidates with scores (4-way), preview, Apply button

✅ VALIDATION: Duplicity report, Placeholder issues list, Format errors (lang _ * structure), Summary, Autofix with preview

📋 LOG: Real-time active record (text edit with timestamp), filters (All / Info / Warning / Error), Clear / Save / Copy action

Key abbreviations:

Data formats (.py vs .localiza)

Format # 1: .py (Legacy Python dict)

Location: APP _ DATA / localize _ data.py

Example:

Benefits of .py format:

• Native Python dict - parsing free, direct use
• Historical (existing in the project from the beginning)
• You can add logic / dynamics (calculated keys)

The drawbacks of .py format:

• Syntax Error = the whole module is not uploaded
• More complex version control (diffs are large)
• Dangerous edit without IDE (Python syntax)

Format # 2: .localize (New Text Format - Recommended)

Location: APP _ DATA / * .localize (e.g. localizedata.localize, mavi.localize)

Example:

Advantages of .localize format:

• Text, readable - easy to edit
• INI-like structure - parsing easily
• Safer - syntax bug no worse (ignore line)
• Git friendly - clean diffs
• Trans friendly - standard for gettext-like tools

The disadvantages of .localize format:

• New, less experience in the project
• Parsing is necessary (small overhead, ~ < 10ms)

Conversion of .py → .localize:

Real operating scenarios

Scenario 1: Add a new language (Italian)

1. Open the application → You go to [VIOLANGUAGES]
2. Click [INCLUDING Add Language]
3. Select "Italian (it)" from Dropdown
4. Check [Auto- Translate using SmartTranslation]
5. Click [Start] → system starts translation (4-way: CZ → IT + EN → IT with both providers)
6. Progress bar is moving (0% → 50% → 100%)
7. Finish → Table with 450 candidates (each with score 50-150)
8. Check spot-check (choose 5-10 random keys, check quality)
9. Click [Apply] → to save in 'APP _ DATA / localize _ data.py'
10. Commit: 'git commit -m' Add Italian language (it) with autotranslation ''

Scenario 2: Update existing translation (German after change of CZ text)

1. A week ago, a translation into German was created.
2. Today it will turn into CZ: "Hello" → "Welcome"
3. Open App → [REGULATIONS] → click DE → [Translate Changed Keys]
4. System detects: "msg _ hello" has changed (old: 'Hello', new: 'Welcome')
5. SmartTranslate automatically translate only changed keys (the remaining 449 takes from cache)
6. ♪
7. Click [Apply] → Only the key in DE is updated
8. Validation → All OK
9. Commit: 'git commit -m' Update German translation for msg _ hello ''

Scenario 3: Correction of structural problems (Duplicity and missing emes)

1. Audit detects: duplicate "msg _ exit" (row 150 and 175), missing emes in "lang _ it"
2. Go to [VALIDATION] → See the list of problems
3. Check [Dry Run Mode] and click [AutoFix All]
4. Preview: "Deletes duplicity (leaves # 1), adds emme to lang _ it"
5. Check and click [Apply] → the actual repair will be done
6. Backup creates' backup _ localize _ data _ 2026 -02-21 _ 14-30-00.py'
7. Redo Audit → All OK (0 problems)
8. Commit: 'git commit -m' Fix: Remove duplicates, add emome to lang _ it '

Data formats

.py format (Legacy):

.localize format (New, text, safer):

Supported languages

60 + languages with complete metadata: ISO codes, flags (emme), native names, specifics.

Examples: Czech (en / cz), English (en), German (de), French (fr), Spanish (es), Russian (ru), Chinese (zh), Japanese (ja), and others.

Troubleshooting & Problem Solving

Problem: "Translation fails with 'API limit exceeded' error"

Cause: The translator reached the daily limit (MyMemory 1000 words / day, DeepL free 500k chars / month).

Solution:

1. Lower in config.json (e.g. 100 to 50)
2. Switch to another provider: (less limits)
3. Wait 24 hours for the reset of the rain limit
4. Buy an API key (DeepL Pro: €5 +, Google Cloud: free first 0.5M chars)

Problem: "Application is not responsive / graphical interface freezes"

Cause: The operation runs at the main thrad instead of the worker thread.

Solution:

1. Close application: Ctrl + Q
2. Check for error messages
3. Reduce batch _ size (large translationbats block UI)
4. Restart application with a flag for verbose output

Problem: "How to add a new language?"

Solutions (graphical interface):

1. Click on the tab [REGULATIONS]
2. Click [INCLUDING Add Language]
3. Select language from drop down (e.g. Italian)
4. Click [Start Auto-Translate] → SmartTranslate Translate All Keys
5. Review results in the table (sort by score)
6. Click [Apply] → to save in localize _ data.py

Solution (batch mode):

Problem: "Validation detects placeholders errors"

Cause: Translation increased / reduced {var} placeholder (e.g. {name} → {n}).

Solution:

1. Go to the [VALIDATION] tab
2. See the list of "Placeholder Issues" with lines
3. Manually correct translations in editor (change {n} back to {name})
4. Or click [Auto- Fix Placeholders] (auto-replace)
5. Check [Dry-Run] for preview before application

Problem: "I accidentally deleted the file - how to return the backup?"

Solution:

1. Go to directories
2. Find (with latest date)
3. Copy it back to the original place:
4. Click [INAUDITION] to verify that all has returned

Problem: "How to run dry-run mode (without real changes)?"

Solutions (graphical interface):

1. Check the checkbox [☐ Dry Run Mode] at the top bar
2. Start any operation (Translate, Fix, etc.)
3. You see the preview that would change (without real modification)
4. Click [Apply] for the actual application (or [Cancel] for cancellation)

Solution (batch mode):

FAQ (All common questions)

Q: Is LocalizeAdder safe for production? Can I run it at 10,000 plus keys?
A: Yes, quite safe. All operations have backup + dry-run mode + audit trail. It's tested for 10,000 + keys without a problem.

Q: How fast is he translating? What is the typical time for 500 keys?
A: On average 100-200 keys / minute (dependent on the provider). 500 Keys = ~ 3-5 minutes with Google Translat, ~ 10 minutes with DeepLem (due to quality scoring).

Q: Can I scribble / automate LocalizeAdder in CI / CD?
A: Yes, fullCLI mode: , , . For details see below. batch mode section.

Q: What OS supports?
A: Python 3.7 + s PyQt5 → Windows 7 +, Linux (Debian / Ubuntu), macOS 10.13 +. All the same. "

Q: What is recommended workflow for the team?
A: (1) Audit → Problem Detection, (2) Translate → adds new keys to languages, (3) Validate → finds errors, (4) Fix → fixes with backup, (5) Export → XLSX for manual review, (6) Commit → do git.

Q: Is there an API for programming (except desktop and batch)?
A: Yes, you can import modules: . Details in README.

Q: Where are the logs stored?
A: . The back 5 files are stored, the older files are archived.

Q: How can I change the subject from dark to light?
A: Config → → . Or at graphical interface: ITESCETings → UI Theme.