Hi, Unfortunately, nested inline markup is not allowed in reST spec. http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup
Thanks, Takeshi KOMIYA 2017-04-14 23:32 GMT+09:00 Mark Peters <[email protected]>: > Hi, > > Is it possible to parse an inline literal to replace text using > substitution? > > For example, our RST doc includes values that are updated periodically such > as: > > The policy must be stored in the ``/etc/debsig/policies/|GPG_KEY_ID|`` > directory > > .. |GPG_KEY_ID| replace:: 69BE019A > > The substitution text is interpreted, well, literally: > > > I've tried using backslash-escaped whitespace, as follows, but the second > backslash escapes both the text and the second set of double-ticks: > > The policy must be stored in the ``/etc/debsig/policies/\ |GPG_KEY_ID|\ `` > directory > > > I know to use the parsed-literal directive for code blocks. Is there an > option for inline literals? > > Thanks, > Mark > > > > > > > -- > You received this message because you are subscribed to the Google Groups > "sphinx-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sphinx-users. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sphinx-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sphinx-users. For more options, visit https://groups.google.com/d/optout.
