On Thu, Apr 23, 2026 at 08:22:07PM +0100, Gavin Smith wrote: > On Thu, Apr 23, 2026 at 06:38:14PM +0200, Patrice Dumas wrote: > > Having @documentlanguagevariant variants as a line command arguments > > list is Texinfo-ish, but it has a drawback, it is not possible to > > also consider @documentlanguagevariant as a simple string customization > > variable, in contrast with line @-command with only one argument. So, > > for example, it is not possible to do > > > > -c documentlanguagevariant=toto_tata > > > > and similar. > > How do you do it, then? Do you do > > -c "documentlanguagevariant=toto, tata" > > instead?
No, it is not possible to do it at all. > > The alternative would be have @documentlanguage reset the > > documentlanguagevariant and documentscript. The above example could be > > > > @documentlanguage az > > @documentscript Cyrl > > > > ... > > > > @documentlanguage fr > > > > Looks ok? > > I think the @documentlanguage should reset the documentlanguagevariant > and documentscript as you say, as the second example you give is more > natural. Ok. Then should we flag an empty documentlanguagevariant and documentscript as invalid with missing argument, or have them mean that they are reset to the default value? Otherwise said, should it be possible to reset the documentlanguagevariant and documentscript without resetting the @documentlanguage? For example, should only the following be correct: @documentlanguage az @documentscript Cyrl ... @documentlanguage az or also @documentlanguage az @documentscript Cyrl ... @documentscript to reset the @documentscript to the default? -- Pat
