Integrate Auto-Translation Versioning for LVGL YAML Files

[marcelpetrick]

Description:
The project currently lacks integration of the auto-translation versioning mechanism for YAML files originating from LVGL projects. These files follow a specific structure and require proper handling to ensure compatibility with automated translation workflows.

Expected Behavior:

• YAML files from LVGL projects should be fully supported.

• The auto-translation versioning mechanism should:

  • Recognize and preserve the structure of LVGL YAML files.
  • Track translation versions consistently.
  • Work seamlessly during both processing and runtime.

Suggested Solution:

• Implement support for LVGL YAML schema within the auto-translation system.
• Ensure version tracking is embedded and updated as part of the translation workflow.
• Validate compatibility with typical LVGL project file layouts.

Why This Matters:

• Ensures reliable handling of structured YAML translation sources.
• Prevents data loss or corruption due to incompatible parsing.
• Enables consistent translation version tracking across projects.

---

Version 2 — Detailed & Structured

Title: Add Support for Auto-Translation Versioning on LVGL YAML File Structures

Overview:
CuteLingoExpress currently does not support the auto-translation versioning mechanism for YAML files used in LVGL-based projects. These files have a defined structure that must be preserved while enabling translation version tracking.

Problem Statement:

• No integration of auto-translation versioning for YAML inputs.
• LVGL YAML structures are not explicitly supported or validated.
• Risk of structural inconsistencies or loss of metadata during processing.
• No mechanism to track translation state/version within these files.

Proposed Improvement:
Introduce full support for auto-translation versioning specifically tailored to LVGL YAML file formats.

Requirements:

1. YAML Structure Compatibility

   • Ensure parser correctly handles LVGL-specific YAML schemas.
   • Preserve hierarchy, keys, and metadata during processing.

2. Translation Version Integration

   • Embed or associate version information within the YAML files.
   • Maintain consistency across translation updates.

3. Processing Pipeline Integration

   • Ensure compatibility during import, transformation, and export stages.
   • Avoid breaking existing LVGL workflows.

4. Validation & Testing

   • Validate against real-world LVGL project YAML files.
   • Ensure no structural regressions or data loss.

5. Extensibility

   • Design solution to support future YAML-based formats if needed.

Benefits:

• Enables seamless use of LVGL project files within the tool.
• Provides consistent translation version tracking.
• Reduces risk of structural errors in YAML processing.
• Improves interoperability with embedded/UI workflows using LVGL.

Conclusion:
Supporting LVGL YAML structures with integrated auto-translation versioning is essential for expanding compatibility and ensuring reliable translation workflows.