On Wed, Jan 18, 2023 at 11:52:33AM +0100, Patrice Dumas wrote: > Even the recent one? I started having more categories in command_data.txt > both for the inner commands classes (in_heading_spec) and outer commands > classes > (contain_simple_text, contain_plain_text), maybe simply adding more > classes/flags would be enough to have a clear code. The issue is that > the number of flags is constrained for the XS parser.
I actually find it hard to remember the difference between "simple text" and "plain text". If I understand correctly "simple text" includes everything that would occur inside a single paragraph, with some exceptions like cross-references and anchors. This includes markup commands (like @emph and @code) as well as glyph (@AA) and accent (@ogonek) commands. It's an important subset of Texinfo content but I don't like describing it as "text". Can we find a better name for it? "Simple content" seems like an immediate improvement. "Basic paragraphal content" is too long. "Simple inline content" might be ok (where "inline" has the same meaning as HTML). "Horizontal content" is an alternative.
