From 95b5e396f4482fbd8e170a4254a94c2258f11fcc Mon Sep 17 00:00:00 2001 From: Andrew Janke Date: Tue, 14 Apr 2020 05:18:59 -0400 Subject: [PATCH] Quotes inside section name were breaking the doco generation --- doc/slf4o.texi.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/slf4o.texi.in b/doc/slf4o.texi.in index 9be610b..d85987d 100644 --- a/doc/slf4o.texi.in +++ b/doc/slf4o.texi.in @@ -133,8 +133,8 @@ In your code, put calls to @code{logger.info(...)}, @code{logger.debug(...)}, an ... @end example -@node Regular and "j" variants -@subsection Regular and "j" variants +@node Regular and j variants +@subsection Regular and j variants The regular ("m") versions of the logging functions take @code{fprintf}-style formatting and arguments, with @code{%s}/@code{%f}/@code{%d}/etc placeholders. These calls look like normal Octave @code{fprintf()} calls. The argument conversion and formatting is done at the Octave level before the message is passed along to the SLF4J Java library. These are the functions you should usually be using.