Jump to content

Edit History

ZiedDams

ZiedDams

Hi PrestaShop Core & Module Developers 👋

I’m currently brainstorming a new module idea and would love to get feedback from the community before starting development.

🎯 Goal

Create an Auto-Translation System Module that:

Detects missing translations in modules and themes

Automatically translates untranslated keys

Optionally improves existing low-quality translations

Works without breaking PrestaShop’s native translation system

💡 Concept Overview

The idea is NOT to replace PrestaShop’s translation mechanism,
but to extend it intelligently.

The module would:

Scan translation domains (modules, themes, core)

Detect missing or empty translation entries

Send only missing strings to an external translation service (API-based)

Store translations using native PrestaShop translation storage (DB or XLF depending on version)

This approach keeps default behavior intact and fully compatible with core updates.

🏗️ Architecture Thoughts

Possible architecture:

Scanner Service – Detect missing translation keys

Domain Resolver – Identify the correct translation domain

External Translation Adapter – Abstract layer for translation providers (API-based)

Translation Persister – Uses native PrestaShop translation writing logic

Admin UI – Controls:

Auto mode (background cron)

Manual scan mode

Module/theme whitelist & blacklist

⚙️ Key Technical Questions

What is the safest way to write translations in PS 8/9 without bypassing the Symfony Translator?

Should translations be written directly into XLF files or via database layers?

Is there a recommended hook or process to trigger translation refresh safely?

Has anyone already built something similar or partially addressed this?

🚀 Extra Ideas

Translation quality score (flag machine-generated translations)

Fallback language detection

CLI support for developers

Translation diff viewer (before / after comparison)

🔎 Why This Could Be Useful

Many shops install multiple modules and themes that are only partially translated.
Manually translating everything is time-consuming and error-prone.

An intelligent assistant that respects PrestaShop’s architecture
could significantly improve multilingual shop adoption.

🙌 Feedback Welcome

I would really appreciate feedback from core contributors or developers who have worked deeply with the translation system.

Is this technically viable in a clean way?

Would you approach the architecture differently?

Thanks in advance!

ZiedDams

ZiedDams

<h2>Hi PrestaShop Core & Module Developers 👋</h2>

<p>
I’m currently brainstorming a new module idea and would love to get feedback 
from the community before starting development.
</p>

<h3>🎯 Goal</h3>
<p>
Create an <strong>Auto-Translation System Module</strong> that:
</p>

<ul>
  <li>Detects missing translations in modules and themes</li>
  <li>Automatically translates untranslated keys</li>
  <li>Optionally improves existing low-quality translations</li>
  <li>Works without breaking PrestaShop’s native translation system</li>
</ul>

<hr>

<h3>💡 Concept Overview</h3>

<p>
The idea is NOT to replace PrestaShop's translation mechanism, 
but to extend it intelligently.
</p>

<p>
The module would:
</p>

<ul>
  <li>Scan translation domains (modules, themes, core)</li>
  <li>Detect missing or empty translation entries</li>
  <li>Send only missing strings to an external translation service (API-based)</li>
  <li>Store translations using native PrestaShop translation storage (DB or XLF depending on version)</li>
</ul>

<p>
This way, default behavior remains untouched and fully compatible with core updates.
</p>

<hr>

<h3>🏗️ Architecture Thoughts</h3>

<p><strong>Possible architecture:</strong></p>

<ul>
  <li><strong>Scanner Service</strong> – Detect missing translation keys</li>
  <li><strong>Domain Resolver</strong> – Identify translation domain correctly</li>
  <li><strong>External Translation Adapter</strong> – Abstract layer for API providers</li>
  <li><strong>Translation Persister</strong> – Uses native PrestaShop translation writing logic</li>
  <li><strong>Admin UI</strong> – Control:
    <ul>
      <li>Auto mode (background cron)</li>
      <li>Manual scan mode</li>
      <li>Whitelist/Blacklist modules</li>
    </ul>
  </li>
</ul>

<hr>

<h3>⚙️ Key Technical Questions</h3>

<ul>
  <li>Best way to safely write translations in PS 8/9 without bypassing Symfony translator?</li>
  <li>Should translations be written directly into XLF files or through database layers?</li>
  <li>Any recommended hook to trigger translation refresh safely?</li>
  <li>Has anyone already built something similar?</li>
</ul>

<hr>

<h3>🚀 Extra Ideas</h3>

<ul>
  <li>Quality score system (flag machine translations)</li>
  <li>Fallback language detection</li>
  <li>CLI support for developers</li>
  <li>“Translation diff viewer” for reviewing changes</li>
</ul>

<hr>

<h3>🔎 Why This Could Be Useful</h3>

<p>
Many shops install multiple modules and themes that are partially translated. 
Manually translating everything is time-consuming.
</p>

<p>
An intelligent assistant that respects PrestaShop’s architecture 
could significantly improve multilingual adoption.
</p>

<hr>

<p>
I would really appreciate feedback from core contributors or developers who 
have worked deeply with the translation system.
</p>

<p>
Is this technically viable in a clean way?  
Would you approach it differently?
</p>

<p>Thanks in advance 🙌</p>

 

×
×
  • Create New...