Produce Skeleton Translation Files — Unordered Library

[AuraMindNest]

Problem

The boost-unordered library has documentation that needs to be brought into the Weblate translation pipeline. .

Acceptance Criteria

• Skeleton translation files for unordered library 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
• Skeleton translation files are generated for all translatable .adoc pages in the boost-unordered documentation

References

• Related files: scripts/inject_translations.py, boost-unordered .adoc source files

[AuraMindNest]

I did this work.

To produce skeleton translation files, I deployed pure upstream Weblate and created components for the Boost Unordered 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. And by using inject_translations.py script, I injected the translations of original into skeleton files.

boost-unordered-documentation-original-PR39.zip

boost-unordered-documentation-zh_Hans-2-PR39.zip