XProc 3.1: text steps 201820192020 20212022202320242025 the Contributors to the XProc 3.1 Standard Step Library specifications XProc/specification XProc Next XML Norman Walsh Achim Berndzen Gerrit Imsieke Erik Siegel This specification describes the optional text related steps for XProc 3.1: An XML Pipeline Language. This specification was published by the XProc Next Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Contributor License Agreement (CLA) there is a limited opt-out and other conditions apply. Learn more about W3C Community and Business Groups. If you wish to make comments regarding this document, please send them to xproc-dev@w3.org. (subscribe, archives). This draft is the “editor’s working draft” and may continue to evolve.
Introduction This specification describes the optional text related XProc steps. A machine-readable description of these steps may be found in steps.xpl. Familarity with the general nature of steps is assumed.
Step library
p:markdown-to-html The p:markdown-to-html step converts a text document in Markdown to XHTML. The p:markdown-to-html step transforms a text document containing Markdown, for example , into HTML. The flavor(s) of Markdown supported and the parameters allowed are implementation-defined. Document properties No document properties are preserved.
Conformance Conformant processors must implement all of the features described in this specification except those that are explicitly identified as optional. Some aspects of processor behavior are not completely specified; those features are either implementation-dependent or implementation-defined. An implementation-dependent feature is one where the implementation has discretion in how it is performed. Implementations are not required to document or explain how implementation-dependent features are performed. An implementation-defined feature is one where the implementation has discretion in how it is performed. Conformant implementations must document how implementation-defined features are performed.
Implementation-defined features The following features are implementation-defined:
References Glossary Glossary needs to be generated Ancillary files This specification includes by reference a number of ancillary files. An XProc step library for the declared steps.