Greetings Gilles, Perhaps my email was ambiguous. What I was planning to do is make the default value of "no_next_page_text" "$(next_page_text)", instead of "next". That still gives people the option to make them different if they want to, but means that customising them both to be the same value only requires customising one value.
I can't see that this will break anything. People who have set no_next_page_text to something specific in the htdig.conf file won't be affected, and people who haven't changed next_page_text won't be affected. The only people affected are those who have changed next_page_text, but still have "next" when there is no next, which is presumably an oversight of theirs. If you see a problem that I don't, then let me know... Cheers, Lachlan >From: Gilles Detillieux <[EMAIL PROTECTED]> >According to Lachlan Andrew: >> For problem (1), also set "no_next_page_text: [page suivante]". (I'll >> fix that to default to next_page_text in the next release...) > >Please don't. There's a reason for using a different attribute for >the next page text on the _last_ search page. >-- >Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> >Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ >Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
