Re: History

Rich Bowen <[EMAIL PROTECTED]> wrote: > >I would like to have a historical document that lists all >releases, what the changes were in each release, apache-1.3/src/CHANGES does that for 1.0 to 1.3. I haven't seen much evidence of anything before 1.0 being still around other than

Re: Incorrect behaviour in ap_get_server_port()?

Lars Oppermann <[EMAIL PROTECTED]> wrote: > >Now, whenever a self-referencing, absolute URL is to be constructed, it >has to point to said application responsible for request distribution, >and not to the particular Apache server that generated the response >containing this URL. To achive this, we

Re: url mapping

Joshua Slive <[EMAIL PROTECTED]> wrote: > >- anybody thinks this is interesting; >- what I am writing is at all intelligible; >- this belongs in Apache; Yes, it's good. >- there are important topics I am missing; mod_vhost_alias >In deciding what file to serve for a given request, Apache starts

Re: ISO-8859-1 characters

"Jaime E . Villate" <[EMAIL PROTECTED]> wrote: > >I apologize if this has already been discussed, but I could not find it in the >list's archive: would it be OK if I added a > >tag in the header of the pages I translate into Spanish? No. You should use Apache's configuration directives to get th

Re: "programs" directory

Joshua Slive <[EMAIL PROTECTED]> wrote: > >- I can't think of a better name than "Include Programs". This is what I >am using as a link on the front page of the manual, and as a title for the >programs page. I was going to use "Support progrmas", but now that I have >also included the httpd man p

Re: httpd-docs-2.0/manual/index.html.fr

Rodent of Unusual Size <[EMAIL PROTECTED]> wrote: > >First suggestion: attach them as something that is recognisably >text rather than application/octet-stream. One simple way is >to just add ".txt" to th end of the file name.. They were sensibly attached using the intended final filename, e.g. i

Re: French translation

Benoit Garnier <[EMAIL PROTECTED]> wrote: >"Hervé Dumont" <[EMAIL PROTECTED]> wrote: >> >> is there anybody involved in a french of the apache 2.0 >> documentation ? I'd like to participate to translate some pages and >> I'd like to know if there is anybody already involved in this task. > >Well, I

Re: support program documentation

Joshua Slive <[EMAIL PROTECTED]> wrote: > >The question is how to do this without creating a bunch of duplicate, >difficult to maintain docs. We could just use "man2html" to convert the >man pages, but this program creates horrible HTML, and would require >hand-tweaking of the output in any case.

Re: [Fwd: Correction about FreeBSD accept filters.]boundary="------------81FF6C751748E02AD2464EDB"

"JONGBaek KANG [°­Á¾¹é]" <[EMAIL PROTECTED]> wrote: >Not acked. Were we supposed to be able to read that? Given that I did the accept filters stuff which is what this appears to be about I think I'd like to see the content of the mail... Tony. -- f.a.n.finch[EMAIL PROTECTED][EMAIL PROTEC

Re: Converting docs to XHTML

Joshua Slive <[EMAIL PROTECTED]> wrote: > >For this to work, someone would need to invest a significant chunk of time >in developing the format, and making sure that tools were available >to convert it to other formats. Don't bother -- use DocBook instead: the tools are already available and they

Re: MPM documentation

[EMAIL PROTECTED] wrote: > >> 1. mpmt_pthread is a really crappy name for a module. > >Agreed. It is even worse because it doesn't rely on pthreads >anymore. Please, if anybody can come up with a better name, we need it. I think the important thing is to make the distinction between mpmt_pthread

Re: Translations and MultiViews (was Re: htdocs/manual/index.html.ja.jis)

Yoshiki Hayashi <[EMAIL PROTECTED]> wrote: > > $ cvs log NEW # Remember the non-branch tag names > $ cvs tag -d TAG1 NEW It's easier to find the tags by looking at the ,v file itself, IMO (noting that branch tags can be distinguished by the fact that they contain a 0, but this

Re: Translations and MultiViews (was Re: htdocs/manual/index.html.ja.jis)

Joshua Slive <[EMAIL PROTECTED]> wrote: > >OK, this is cool, but now that we have our first start at a translation, >we need to think a little. If I just drop this into manual/, nobody is >going to see it. In order for MultiViews to come into effect, we would >need to rename the existing index.ht

Re: cvs commit: httpd-docs-1.3/htdocs/manual/mod core.html

[EMAIL PROTECTED] wrote: > > +For HTTP/1.0 clients, Keep-Alive connections will only be used if > +they are specifically requested by a client. In addition, a > +Keep-Alive connection with an HTTP/1.0 client can only be used when > +the length of the content is known in advance. This implies

Re: main page

Joshua Slive <[EMAIL PROTECTED]> wrote: > >- Two or three columns? On my high-res monitors, the two column display >is nicer, but I can see how it could involve lots of scrolling on >lower-res displays. We can't please everyone, but what is the best >compromise? I think two columns is fine. My b

Re: main doc page: REALLY last call

Joshua Slive <[EMAIL PROTECTED]> wrote: > >What'd'ya'think? Cool. I should have looked at this before sending my previous message to this list! I'm not sure I like the header. IMO it should be more like the rest of the docs, i.e. header gif, "Apache HTTP Server", "Apache 1.3 User's Guide" as befo

Re: SSI tutorial

Joshua Slive <[EMAIL PROTECTED]> wrote: >On Sat, 28 Oct 2000, Rich Bowen wrote: >> >> So, the question I had is, is it reasonable to create a new section for >> HOWTOs and tutorials? There's a doc right now (/manual/misc/howto.html) >> that has some howto's on it, but once we have more than just a

Re: env.html and a template for future docs

Joshua Slive <[EMAIL PROTECTED]> wrote: >On Wed, 18 Oct 2000, Tony Finch wrote: > >> >Joshua Slive wrote: >> >> >> >> So, here is a second draft of my "Apache Environment Variables" >> >> doc. >> > >> Another su

Re: env.html and a template for future docs

Rodent of Unusual Size <[EMAIL PROTECTED]> wrote: >Joshua Slive wrote: >> >> So, here is a second draft of my "Apache Environment Variables" >> doc. > >Looks good, but a couple of suggestions: > >1. Mention suexec and its restricted list of envariables. >2. Where available, reference tutorial/expa

Re: cvs commit: httpd-docs-1.3/htdocs/manual/mod index.html index-bytype.html mod_example.html

Joshua Slive <[EMAIL PROTECTED]> wrote: > >Check the results of what I did. (Sorry, the comment on the commit was >probably not detailed enough.) I left in the compatibility info for all >the obsolete modules. I only removed it for modules that are still in the >distribution, but were introduced

Re: cvs commit: httpd-docs-1.3/htdocs/manual/mod index.html index-bytype.html mod_example.html

Joshua Slive <[EMAIL PROTECTED]> wrote: > >However, I disagree with your logic. You are essentially assuming that >people with Apache 1.2 are going to be coming to the website and trying to >use the 1.3 docs, and that we should be trying to make life very easy for >them. They should in fact be us

Re: Order Mutual-failure

Joshua Slive <[EMAIL PROTECTED]> wrote: > >Well, I'm tempted to nuke it from the documentation, at least. >It confuses me, and obviously other people too. I agree, mutual-failure is bogus. Tony. -- en oeccget g mtcaaf.a.n.finch v spdlkishrhtewe y[EMAIL PROTECTED] eatp o v eiti i d.[E

Re: Order Mutual-failure

Joshua Slive <[EMAIL PROTECTED]> wrote: > >I've never been able to figure this out either. What the heck is >"Order Mutual-failure" supposed to do? Dunno. It's really old code, though, so the CVS archive isn't much help. Tony. -- en oeccget g mtcaaf.a.n.finch v spdlkishrhtewe y[EMAIL PR

Re: Module docs

Joshua Slive <[EMAIL PROTECTED]> wrote: >As I think is evident, I am interested in improving the consistency (and >usability) of the module docs by putting them all in a standard format. I >have made a suggestion of a format (See message-id ><[EMAIL PROTECTED]>) >but I really don't feel comfortabl

Re: "Legacy Free" apache-2.0 docs

Joshua Slive <[EMAIL PROTECTED]> wrote: > >My opinion is that there should be a good "new features" document to help >people upgrade from 1.3, but other than that, there should be no >references to versions earlier than 2.0 in the docs. Those references are >not really there for people upgrading,

Re: CVS errors

Rich Bowen <[EMAIL PROTECTED]> wrote: > >There seem to be perms in the CVS tree that are borked. Either that, or >I'm not set up right in the 2.0 docs tree: > >[EMAIL PROTECTED]:~/devel/httpd-docs-2.0$ cvs update -d >[EMAIL PROTECTED]'s password: >cvs server: Updating . >cvs server: Updating apidoc