[mod_python] Any LaTex gurus here?

Jim Gallacher jg.lists at sympatico.ca
Sun Jun 26 09:23:11 EDT 2005


Nick wrote:
> I believe the indexing is actually done in perl, and it's probably one 
> of the most problematic features I've encountered.  Generally, just go 
> with what works, unless you want to rip into the perl to figure out what 
> the problem is.  

Perl. Nooooooooo........ :) So I'll just go with the hack for now. It 
only affects a couple of lines and it works, so it's good enough.

Thanks Nick.

Jim


> I've banged my head enough times against the wall on 
> problems like these to either: a) just do broad indexing for the TOC and 
> not worry about a keyword index, or b) use non-contextual indexing, 
> because it just seems to work better.
> 
> Nick
> 
> Jim Gallacher wrote:
> 
>> I'm trying to generate the mod_python documentation, but finding some
>> slight weirdness in the index that is created. I'm hoping someone here
>> may have be able to offer some insight before I wander off elsewhere in
>> search of an answer.
>>
>> OS: Debian unstable
>> TeTex version: 2.0.2
>> Python src: 2.3.5
>>
>> This does not work (it ignores the \longprogramopt):
>>
>>   \indexii{./configure}{\longprogramopt{with-apxs}}
>>
>> Output:
>>
>> <a href="inst-configure.html#l2h-6">\longprogramoptwith-apxs</a>
>>
>>
>> But this alternate form does work:
>>
>>   \index{./configure!\longprogramopt{with-apxs}}
>>
>> Output:
>>
>> <a href="inst-configure.html#l2h-6"><b
>> class="programopt">--with-apxs</b></a>
>>
>> Any ideas what may be wrong?
>>
>> Regards,
>> Jim
>>
>>
>> _______________________________________________
>> Mod_python mailing list
>> Mod_python at modpython.org
>> http://mailman.modpython.org/mailman/listinfo/mod_python
> 
> 



More information about the Mod_python mailing list