On 6 August 2015 at 19:43, Benno Schulenberg <[email protected]> wrote: > > On Thu, Aug 6, 2015, at 16:39, Eli Zaretskii wrote: >> > Date: Thu, 6 Aug 2015 11:20:55 +0100 >> > From: Gavin Smith <[email protected]> >> > >> > On 6 August 2015 at 11:18, Benno Schulenberg <[email protected]> >> > wrote: >> > > I have a string, including the double quotes, that I wish to have set >> > > in a fixed-wdith font in the HTML document, but I don't want single >> > > quotes added around the string when such type setting is not available. >> > > >> > > Currently I have @code{"string"}, which results in '"string"' in the >> > > Info document, which is undesirable. >> > >> > Use @t instead of @code. (Info node (texinfo)Fonts.) >> >> My recommendation would be to use @samp{string} (yes, without the >> quotes: they are redundant in this case). > > @samp{} produces 'single quotes' in Info and ‘pretty single quotes’ in > HTML output. But for my case the double quotes are part of the code > and must be shown exactly so. > >> I think @t and other direct >> references to typefaces should be avoided. > > I agree with that. But texinfo does not provide something > like @code-but-only-use-typeface-never-quotes. I wish to > indicate that something is code (when the output method > alllows it) only through typefaces (like fixed-width or bold) > never by using any kind of quotes.
I've remembered that you can turn off code quotes completely with "texi2any -c OPEN_QUOTE_SYMBOL= -c CLOSE_QUOTE_SYMBOL= FILE.texi" where FILE.texi is your input file. I don't know if that's what you want: you won't have the option of having quotes around code-like text anywhere.
