Asciidoctor fails to parse formatted text: "<a data-type
I'm running asciidoctor with the following command:
asciidoctor -r asciidoctor-pdf -b pdf master.asciidoc
And it fails to parse the following text:
pass:[<a data-type="xref" data-xrefstyle="ct" href="#m1">#m1</a>]::
With the following error:
failed to parse formatted text: <a data-type="xref" data-xrefstyle="ct" href="#m1">#m1</a>
How can I fix it?
Asciidoctor with backend PDF does only have limited support for passthrough syntax as the documentation states.
Asciidoctor PDF does not support arbitrary passthrough content. While the basebackend for the PDF converter is html, it only recognizes a limited subset of inline HTML elements that can be mapped to PDF (e.g., a, strong, em, code, ). Therefore, if your content contains passthrough blocks or inlines, you most likely have to use a conditional preprocessor to skip them (and make other arrangements).
While the a tag is mentioned above a small test shows that only basic syntax is supported.
Using the below adoc file...
= test pass
pass:[<em>#m1</em>]
pass:[<strong>#m1</strong>]
pass:[<code>#m1</code>]
pass:[<a href="#m1">#m1</a>]
pass:[<a href="#m1" data-type="xref" data-xrefstyle="ct">#m1</a>]
Running it through the asciidoctor pdf backend produces the same error as you already mentioned in your question.
$ asciidoctor -r asciidoctor-pdf -b pdf test.adoc
asciidoctor: ERROR: failed to parse formatted text: <a href="#m1" data-type="xref" data-xrefstyle="ct">#m1</a>
The resulting PDF looks like the below screenshot. The simple <a href="#m1">#m1</a> line is properly converted. But as soon as further attributes are added it fails. This is in sync with the documentation stating advanced html syntax is not recognized by the pdf backend.
To generate a PDF with the desired passthrough you may want to convert it with plain asciidoctor and pipe it to wkhtmltopdf.
asciidoctor -o - test.adoc | wkhtmltopdf - test.pdf
The result uses the html look and feel of as shown below with slightly smaller body text.
- How to generate random variable names in C++ using macros?
- How can I create a Swift macro that forwards parameters to another macro?
- Macro definition to determine big endian or little endian machine?
- What causes a TU to be included in compilation?
- Understanding why certain preprocessor macro overloads don't work
- Can you compare two constant pointers in the C preprocessor?
- Is there way to tell IntelliJ IDEA which output folder to use for GWT compiler?
- CL Macro does not resolve properly
- How to print constexpr in C23 at compile-time?
- How to declare a struct with fields at specific offsets in C++?
- Inlining a function with Clojure macros
- How to redefine (override) C++ __DATE__ and __TIME__ predefined macros in Visual Studio?
- Anonymous union definition/declaration in a macro GNU vs VS2008
- Does the Visual C++ compiler optimize out undefined macro blocks?
- C++ Compiler Macro for Status of "Use Precompiled Headers"
- Is there a way to use a preprocessor macro inside of another function-like macro?
- C++ - style passing caller file and line to function (equivalent of __FILE__ and __LINE__)
- Catia Macro " Collapse all geometrical sets "
- Suppress comparison always true warning for Macros?
- Using logical operators with macros
- What are the Pros and Cons of VBA Code vs Macros in MS Access?
- Can a scala3 macro introduce an implicit value around an existing block?
- What is the purpose of a double negative in macro definition, like (!!(expr))?
- Getting base name of the source file at compile time
- Matching enum variant without specifying variants in Rust macro
- How to create a variable number of printf formats and values in a C macro?
- Recursive C Macros
- What Turing complete macro languages are available for C/C++
- Treating __func__ as a string literal instead of a predefined identifier
- Array-size macro that rejects pointers