Re: Texinfo -> HTML issues

[Patrice Dumas]

> > So the --no-split references and the split references which makeinfo
> > produces are not compatible.
> 
> Oops!  Sorry, I was sure this worked.  Perhaps it did at one time, and
> became broken, or maybe I was just dreaming...
> 
> Karl, can this be fixed?  I think this is a bug (assuming that the
> other manuals are produced with the same splitting option as the one
> we are running through makeinfo).

This can not be fixed easily, as (I think Karl) explained in the manual
(node HTML Cross-reference Mismatch)

     In the case where we assume the referent is split, but it is actually
   available in mono, the only recourse would be to generate a `manual/'
   subdirectory full of HTML files which redirect back to the monolithic
   `manual.html'.  Since this is essentially the same as a split manual in
   the first place, it's not very appealing.

A possible workaround would be to use the external source of information 
discussed in a proposal but still not implemented and maybe to be rediscussed.

> > I regularly produce HTML files on GNU/Linux for use on lesser
> > operating systems.  Is there an makeinfo option to case-fold HTML
> > filenames?
> 
> No (but only because no one has written the code).  For now, you need
> to generate the files on the same OS; on those systems where file
> names are case-insensitive, makeinfo does TRT.  Or you could generate
> the files on the system with most problems, and then they will work on
> more (or even all) systems.

This is not an issue for cross references. But this could be an issue 
because you cannot copy the html files from the unix computer to the
Microsoft OS computer.

Pat