c266734448
Previously we used our own homespun formatting. But this produces over-long lines that aren't ideal for diffs in tests. Easier to use something off-the-shelf and standard. Closes #7580. Performance is slower by about a factor of 10, but this isn't really a problem because native isn't suitable as a serialization format. (For serialization you should use json, because the reader is so much faster than native.)
1.1 KiB
1.1 KiB
% pandoc -f latex -t native
\newcommand{\cicd}{CI/CD\xspace}
Software developers create \cicd pipelines to… Following issue can be resolved by \cicd:
^D
[ Para
[ Str "Software"
, Space
, Str "developers"
, Space
, Str "create"
, Space
, Str "CI/CD"
, Space
, Str "pipelines"
, Space
, Str "to\8230"
, Space
, Str "Following"
, Space
, Str "issue"
, Space
, Str "can"
, Space
, Str "be"
, Space
, Str "resolved"
, Space
, Str "by"
, Space
, Str "CI/CD:"
]
]
% pandoc -f latex -t native
\newcommand{\cicd}{CI/CD\xspace}
\cicd\footnote{\url{https://en.wikipedia.org/wiki/CI/CD}} is awesome.
^D
[ Para
[ Str "CI/CD"
, Note
[ Para
[ Link
( "", [], [] )
[ Str "https://en.wikipedia.org/wiki/CI/CD" ]
( "https://en.wikipedia.org/wiki/CI/CD", "" )
]
]
, Space
, Str "is"
, Space
, Str "awesome."
]
]
% pandoc -f latex -t native
\newcommand{\cicd}{CI/CD\xspace}
\newcommand{\pipeline}{pipeline\xspace}
\cicd\pipeline.
^D
[ Para [ Str "CI/CD", Space, Str "pipeline." ] ]