httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <>
Subject Re: End of life for 2.0 documentation?
Date Fri, 13 Jul 2012 15:28:45 GMT
On 13.07.2012 16:48, Daniel Gruno wrote:
> On 07/13/2012 04:26 PM, Eric Covener wrote:
>> I think some kind of hint would help, a quick google search for me
>> shows DirectoryIndex has 2.0 as first result but AllowOverride has
>> 2.4.
>> However, I think (naively) calling /current/ the canonical version may
>> stretching the semantics a bit.  So maybe the former?
> Yeah, perhaps it's better to start out referring to the 2.2
> documentation as the 'upgrade' for 2.0. I have been researching a bit on
> how it's done, and it seems that the best approach would be to add the
> canonical tag for each individual page, f.x. mod/core.html would then
> have the following tag:
> <link href=""
> rel="canonical" />

This is something Rich did for the 1.3 docs earlier this year. He 
actually was using the "current" links then.

Example from /docs/1.3/invoking.html:

     <meta name="generator" content="HTML Tidy, see" />
     <link rel="canonical" 

     <title>Starting Apache</title>

> This is an automated process, and may refer to some non-existent pages
> where the 2.0 and 2.2 modules differ, but Google claims to be able to
> sort this out by themselves.
>> It would be cool if each page in the manual had a persistent link to
>> toggle the version being displayed (where applicable!).  If only there
>> was someone who wasn't afraid to generates pages of commit messages :)
> That's an idea as well, and while I'm not against it in any way, I think
> it may just be a whole lot of manual work if I were to add a 'version
> changer' for each applicable page. But I'll think about that as well - I
> have a tendency to go ahead and make crazy things like this anyway ;)




To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message