translation-diff-import

Name: translation-diff-import
Availability: InStock
Author: Devolutions

Merge translated JSON patches into full target-language JSON files.

25.4k|893|Updated Jun 15, 2021

Search Tags:#localization #translation #json #merge #i18n #powershell

Ready to run

npx skills add https://github.com/Devolutions/UniGetUI --skill translation-diff-import

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: translation-diff-import
Source: https://github.com/Devolutions/UniGetUI/tree/main/.agents/skills/translation-diff-import
Command: npx skills add https://github.com/Devolutions/UniGetUI --skill translation-diff-import

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of integrating translated text back into the main language files, ensuring consistency and accuracy in multilingual applications.

Core Features & Use Cases

Import Translated Patches: Merges translated strings from a sparse JSON file into a full target-language JSON file.
Validation: Validates translated content against source files to ensure structural integrity and prevent common translation errors.
Use Case: After translators have worked on a specific set of strings exported from the application, this skill can be used to efficiently merge their work back into the main French language file, updating only the translated entries.

Quick Start

Use the translation-diff-import skill to merge the translated French patch into the full French JSON file.

Frequently Asked Questions about translation-diff-import

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I merge translated JSON patches into full target-language i18n files?▼

Merging translated JSON patches into full target-language i18n files involves integrating sparse translated strings into the main file. This process updates only the translated entries while validating against source files to ensure structural integrity and prevent common translation errors.

What is the best way to preserve key order when merging translation files?▼

Preserving key order when merging translation files requires a deterministic merging approach. Using PowerShell 7 with the 'cirup' utility for file merging operations ensures that the original key order and structure of the target JSON file are fully maintained.

Does the translation merge process validate localized content against source files?▼

Yes, the translation merge process validates localized content against source files. This validation step ensures structural integrity and prevents common translation errors before the translated patches are integrated into the full target-language JSON file.

Do I need PowerShell 7 to import localized JSON strings?▼

Yes, you need PowerShell 7 to import localized JSON strings. PowerShell is required for executing the deterministic file merging operations, and the process specifically relies on the 'cirup' utility to merge translated patches accurately into the target files.

Can I use this to update only a specific set of translated strings in a French language file?▼

Yes, you can use this to update a specific set of translated strings in a French language file. After translators work on exported strings, this approach efficiently merges their work back from a sparse JSON patch into the full target file.