AsciiDoc Unit Skeleton Generation

[AuraMindNest]

Problem

Parse each source .adoc file through Weblate's own AsciiDoc parser to produce skeleton unit files that match exactly how Weblate would segment the content. Each skeleton unit contains the source text, an ID hash, location metadata, and an empty target — ready for translation injection in the next step.

Acceptance Criteria

• Skeleton translation files are produced
• Each unit in the skeleton contains: source (original text), id_hash (deterministic hash matching Weblate's algorithm), location (file path + line range), note (context hint), flags (e.g., no-wrap for preformatted blocks), and target
• The skeleton format matches Weblate's internal storage format
• Output skeletons are stored in a structured directory mirroring the component layout

References

• Related files: Source .adoc component files
• Upstream: Weblate's AsciiDoc format handler, translate-toolkit's unit hashing logic

[AuraMindNest]

I have done this work.

To produce skeleton translation files, I deployed pure upstream Weblate and created components for the Boost Json library documentations by using the Weblate's own AsciiDoc parser. And then I generated the skeleton translation files by using the backup function of Weblate.

boost-json-documentation-zh_Hans-1-PR16.zip

[snowfox1003]

I’ve reviewed this work.
The components/ directory contains per-component JSON exports with Weblate-style units (including id_hash, source, and related metadata). This structure is well suited for offline review, diffing, and migration planning without relying on the live Weblate UI.

---

Appendix

Counts below include only units rows whose translation_id maps to zh_Hans in each file’s translations[] list (Simplified Chinese translation units, not the English/source catalog rows).

Metric	Value
JSON files	32
zh_Hans unit rows (total)	825

Smallest zh_Hans unit counts (5 files):

zh_Hans units	File
3	doc-pages-definitions-adoc.json
4	doc-pages-io-overview-adoc.json
5	doc-pages-allocators-overview-adoc.json
5	doc-pages-conversion-forward-adoc.json
5	doc-pages-dom-nested-access-adoc.json

Largest zh_Hans unit counts (5 files):

zh_Hans units	File
126	doc-pages-benchmarks-adoc.json
115	doc-pages-dom-value-adoc.json
71	doc-library-detail-adoc.json
63	doc-pages-allocators-storage-ptr-adoc.json
61	doc-pages-io-parsing-adoc.json

[wpak-ai]

This issue involved working with Weblate web UI to generate json artifacts and didn't involve any code implementation.
The generated artifacts are independently reviewed and accepted by reviewers.