redhat-documentation / asciidoc-markup-conventions

How to use AsciiDoc mark-up to properly style elements in Red Hat documentation
https://access.redhat.com/documentation/
17 stars 16 forks source link

{nbsp} in Command Block #32

Closed apinnick closed 1 year ago

apinnick commented 6 years ago

{nbsp} in a command block does not render correctly unless the block is preceded by [subs="attributes"], as in the following example:

[options="nowrap" subs="+quotes,verbatim,attributes"]

ansible-playbook --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa -i /usr/share/ovirt-engine-metrics/bin/ovirt-engine-hosts-ansible-inventory --extra-vars "{nbsp}cluster_name=_ClusterName ovn_central=_OVN_CentralIP ovn_tunneling_interface=_VDSM_NetworkName" ovirt-provider-ovn-driver.yml


VladimirSlavik commented 6 years ago

I'd say this particular issue is not with the conventions, but with the insufficient documentation for markup inside command blocks.

That said, I'd love to have some reference for the command block shenanigans, too - it's a rater murky topic. Even the official AsciiDoc(tor?) manual does not say enough.