query about literal inclusion with :literal: and :code:

--===============1594953296394823349==
Content-Type: multipart/alternative; boundary="0000000000008786f6063e6610ad"

--0000000000008786f6063e6610ad
Content-Type: text/plain; charset="UTF-8"

I am happy that if I include code specifying :literal: as well as using
:code: to specify the language that this suppresses the parsing for syntax
highlighting, which I definitely do not want in this case. But it seems to
me that I should still get the `code` and programming language classes set
on the pre element and also to have the inclusion wrapped in a `code`
element. Currently, the fact that I set :code: is apparently ignored (by
the rst2html5 writer).

Thanks for considering this viewpoint,
Alan Isaac

--0000000000008786f6063e6610ad
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I am happy that if I include code specifying :literal: as =
well as using :code: to specify the language that this suppresses the parsi=
ng for syntax highlighting, which I definitely do not want in this case. Bu=
t it seems to me that I should still get the `code` and programming languag=
e classes set on the pre element and also to have the inclusion wrapped in =
a `code` element. Currently, the fact that I set :code: is apparently ignor=
ed (by the rst2html5 writer).<div><br></div><div>Thanks=C2=A0for considerin=
g this viewpoint,</div><div>Alan Isaac</div></div>

--0000000000008786f6063e6610ad--


--===============1594953296394823349==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============1594953296394823349==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline