>> I couldn't find anywhere in the documentation that `@include` does
>> not accept file names containing spaces. AFAICS, since `@include`
>> needs a line of its own, such a limitation is not necessary.
>> Compare this to LaTeX's `\input{...}` command, which also accepts
>> file names with spaces.
>
> My recommendation is just to avoid spaces in Texinfo file names.
Mhmm, Windows users might not be happy about this :-)
> So if we added double quotes (or curly braces) around the file name in
> texinfo.tex all the time, this may not be 100% reliable as it is not a
> standard feature of TeX.
Using braces sounds promising. Regarding reliability: what TeX system
do you have in mind that is not based on Web2C, or which doesn't have
the standard extensions provided by Web2C? AFAIK, recent versions of
LaTeX require them.
> I've made an attempt at wrapping braces around the file name only if
> it has a space. I've implemented this in a way that it should be
> easy to remove if it turns out to cause problems.
>
> This will not work if the file name has two spaces or more in a row,
> however.
Thanks.
Werner
