Fixing a Hangul form by changing what the tool edits

I wanted to replace wording while keeping the form’s tables and formatting. Yet a file could pass ZIP and XML checks and still have tangled text. The generator was collecting all text under a table-enclosing paragraph, merging multiple cells into one long editing unit.

With Codex I excluded table-enclosing paragraphs and selected the actual cell paragraphs. Replacement, rebuilding, inspection and previews now use that same boundary. I also documented field-based edits for fixed forms and clarified input, output and backup roles after restoring a wrongly changed file.

I preserved the package order and compression, with mimetype first and uncompressed. Editing the body also rebuilds preview text and clears cached line layouts for Hangul to recalculate. The requested 95% character width and −5 spacing were specific to that form.

Testing the revised generator against the original symptom found no merged paragraphs over 500 characters; the longest editable paragraph was 99 characters. I also ran syntax, ZIP and form checks.

For the next form, I can reuse the sequence: inspect the structure, identify fields, preserve their surroundings, then check the package, preview and rendered page. The lasting result is the rule shared by the tool and skill. Its output is HWPX; binary HWP still requires conversion in Hangul.

This account follows the form failure and my generator/skill repair, distinguishing the repair tests from structural checks on an older file. ZIP/XML checks on the older retained output establish its package condition, not the rendered appearance of the repaired output.