KikuAI Untwine
Fix Articulate import errors
Compare original and translated XLF locally. Download a repaired file when the structure is safely repairable, or a diagnosis report when it is not.
Add both files. No extra button needed.
Output is a repaired XLF or a diagnosis report. No prompt-writing or blind XML rewrite.
Demo downloads: original, repairable translated, manual-review translated, sample diagnosis report.
Not sure which file is which?
Original = untouched export from the exact Articulate course copy. Translated = the same file after translation. If you duplicated the course after exporting, export a fresh original XLF from that copy.
Not a chat prompt
Why not just use ChatGPT?
Chat is fine for explaining XML. This checker is for strict original-vs-translated file comparison before an Articulate import.
Pair comparison
It compares the original export with the translated file instead of editing one XML blob in isolation.
No blind rewrite
It does not rewrite translated text or protected tags when a safe deterministic repair is not proven.
File artifact
The useful output is a repaired XLF or a report you can send to a translator or support.
Translation file does not match this course.
The preview can flag segment-map drift before you retry the import.
Targets, tags, or protected placeholders changed.
Detect structure damage without rewriting translated text.
No false promise.
Unsupported cases show a diagnosis, not an automatic repair claim.
When vendor fixes do not help
Some Articulate import errors are product bugs. Others are file-pair drift.
If Articulate has already fixed a specific Rise import bug, re-exporting may be enough. Untwine is for the next case: the original export imports cleanly, but the translated file no longer matches the same course structure.
Still worth checking
- The course was edited or duplicated after export.
- The translation tool changed IDs, namespaces, segmentation, or protected tags.
- The translated file is missing expected XLIFF file/body structure.
Not a vendor-bug detector
The checker does not replace Articulate release notes or support. It gives you a local report when the translated file itself appears to have drifted from the original export.
Supported cases
Use it for Articulate import failures where the source export is available.
The checker needs the untouched original XLF/XLIFF export and the translated file from the same course workflow. It separates safe structural repairs from manual-review cases.
Supported when
- Original and translated Articulate XLF/XLIFF files are both available.
- The translated file came from Rise or Storyline XLIFF workflow.
- The likely break is IDs, targets, protected tags, encoding, or course-copy mismatch.
- You need a repaired file only when the repair is deterministic.
Not for
- Generic XLIFF translation, proofreading, or terminology QA.
- Files without the matching original Articulate export.
- Rebuilding missing course structure after heavy manual XML edits.
- Cloud upload, private file review, or a promise that every file can be repaired.