Hello,

Currently, from what I understand, the AsciiDoc writer discards the semantic of SmallCaps elements.

There is no native syntax for small capitals in AsciiDoc. To my knowledge, the only implementation that exists is in Asciidoctor PDF, where it is used for styling text using a CSS-like text-transform property.

And in Pandoc, native syntax for small capitals is still an ongoing debate.

Though, I would argue that totally discarding this information in the AsciiDoc output is not the best compromise we could have, and I believe it should be at least interpreted as a class. This behavior would be consistent with how SmallCaps are currently handled in Markdown, and it would somewhat be consistent with the reasoning that led to close this issue.

To illustrate the situation, here is an example. Right now, in order to retain the small caps information in my AsciiDoc output, I have to use this Markdown syntax:

The last word is in small <span class="small-caps">capitals</span>.

Which is actually not recognised by Pandoc as a SmallCaps element, but as a Span element with a small-caps class. It gives me this output (which is definitely fine by me):

The last word is in small [.small-caps]#capitals#.

But the "correct" Pandoc syntax is actually without the hyphen between small and caps:

The last word is in small <span class="smallcaps">capitals</span>.

But it currently outputs this:

The last word is in small capitals.

What do you think? :)