You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
see snippet below. when the parser encounters a document attribute trying to set author and/or email, we need to special case so that we can produce/parse an Author struct. these explicit attrs (as opposed to using the Author line) are documented to be only supported in the document header, so we can contain the logic there.
note in the snippet below how author_1 value shows up as John M Doe -- which sort of proves this exact example is really an error (maybe should produce a warning?) but at the very least explicitly setting via attrs (not combined with an author line) is a supported mechanism and needs to work.
= Doc Title
john M Doe <john@doe.com>; Bob Smith <bob@smith.org>
:author: Sally McAttr:email: [email protected]
author={author}
author_1={author_1}
authors={authors}
email={email}
initials={authorinitials}[subs=-macros]
email={email}
The text was updated successfully, but these errors were encountered:
see snippet below. when the parser encounters a document attribute trying to set
author
and/oremail
, we need to special case so that we can produce/parse anAuthor
struct. these explicit attrs (as opposed to using the Author line) are documented to be only supported in the document header, so we can contain the logic there.note in the snippet below how
author_1
value shows up asJohn M Doe
-- which sort of proves this exact example is really an error (maybe should produce a warning?) but at the very least explicitly setting via attrs (not combined with an author line) is a supported mechanism and needs to work.see https://docs.asciidoctor.org/asciidoc/latest/attributes/document-attributes-ref/#document-metadata-attributes
The text was updated successfully, but these errors were encountered: