bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Renaming an Index node to prevent file collision


From: Michael Hope
Subject: Re: Renaming an Index node to prevent file collision
Date: Mon, 25 Jun 2012 09:36:57 +1200

On 23 June 2012 00:00, Patrice Dumas <address@hidden> wrote:
> On Fri, Jun 22, 2012 at 10:59:00AM +1200, Michael Hope wrote:
>>
>> There's at least three groups working around the problem in their
>> build systems which is unfortunate.
>>
>> The current Top to index.html mapping is in nodename_to_filename_1().
>> One fix is to special case nodes called 'Index' in the same way and
>> rename them to 'Index_.html'.  This keeps the problematic names in one
>> place.
>
> makeinfo in C is not maintained anymore, and the current resolution of
> this issue was to consider that we should not bother with that issue,
> both nodes will end up in the same file, that's all.

Unfortunately that code is enabled based on the build machine, not on
the target.  We've discussed always using the case insensitive code
but that would need a patch to makeinfo.

> That being said, it is fairly easy with the cvs makeinfo version (in
> perl) to change the filename associated with a node, as there are many
> hooks for customization (in perl).  The API may not be definitive,
> however, but there will still be some way to do it when the API is
> stabilized.
>
> You can try the attached file to do that (I have not checked on anything
> else than GNU/Linux, though), and call along
>
>  ./texi2any.pl --html --init-file map_index_name.pm myfile.texi
>
> You could even conditionalize the regexp to a value indicating whether
> this mapping is required or not based on a platform detection, or maybe
> another perl variable.
>
> As the API will certainly change, be prepared to have to change the
> customization file if you use it (but you can ask me, as this is a
> fairly common need).

Ta.  The GDB maintainers will probably want to stay with the current
4.x version of makeinfo.  I'll look for other workarounds.

-- Michael



reply via email to

[Prev in Thread] Current Thread [Next in Thread]