You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by Joshua Slive <jo...@slive.ca> on 2002/09/13 17:46:59 UTC

Re: no doc for MaxMemFree or AddOutputFilterByType

On 13 Sep 2002, Jeff Trawick wrote:

> "Sander Striker" <st...@apache.org> writes:
>
> > > Does anybody have a short description for MaxMemFree?
> >
> > Sure, I should have documented it in the first place, but hey...
> >
> > MaxMemFree sets the maximum number of free Kbytes that the main
> > allocator is allowed to hold without calling free().  When not
> > set, or set to 0, the threshold will be set to unlimited.
>
> Thanks.  I have a docs patch at
>
>   http://www.apache.org/~trawick/docs-patch
>
> which I expect to eventually commit.  I was a bit alarmed at the scope
> of the changes to the generated html so I intend to get somebody on
> the docs list to review it first (assuming I ever get subscribed :) ).
>
> The patch doesn't update the Japanese version of mpm_common.xml.  I
> started to put in the English description of MaxMemFree as a
> placeholder but I wasn't sure what that sort of havoc that would
> create.
>

I think, in general, we should let translators worry about non-english
docs.  There are a couple reasons for this: 1) we don't want to mess up
the whole file by opening it in an editor that can't handle the encoding;
and 2) we may eventually have many translations, and we don't want to
place barriers in the way of people trying to update the docs -- I suspect
developers are going to be much less willing to update the docs if they
need to hit 15 or 20 files.

In particular, I suggest that you don't even commit the changes
to non-english docs that may occur when you build.
So why don't you regenerate your patch by doing
cd httpd-2.0/docs/manual/mod/
cvs diff *.html.en > docs-patch

Then the diffs will be much more contained.  The other thing that should
be done to cut down on the diffs is to insert some line-breaks in the
process for generating directives.html (and a few other files).  At the
moment, that file is essentially one big line, so the diffs are always
huge.  But there is nothing you can do about that.  It requires a change
to the xsl files.

Joshua.


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: Default build target (was Re: no doc for MaxMemFree or AddOutputFilterByType)

Posted by Astrid Kessler <ke...@kess-net.de>.
Joshua Slive <jo...@slive.ca> wrote: 

> Does anyone (particularly people working on translations) have an
> objection to changing the default ant build target to only build "en",
> and have separate targets to build the other languages?

+1
 
Kess

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: Default build target

Posted by André Malo <nd...@perlig.de>.
* Joshua Slive wrote:

> changing the default ant build target to only build "en", and
> have separate targets to build the other languages?  

+1.

nd
-- 
s;.*;aaaaaoaaaoaaaaooooaaoaaaomaaaa:a:alataa:aaoat:a:a:a
maoaa:a:laoata:a:oia:a:o:a:m:a:o:alaoooat:aaool:aaoaa
matooololaaatoto:aaa:o:a:o:m;;s:\s:\::g;y;mailto:;
\40\51/\134\137|ndparker <nd...@perlig.de>;;print;

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: Default build target (was Re: no doc for MaxMemFree or AddOutputFilterByType)

Posted by Joshua Slive <jo...@slive.ca>.
On Sat, 14 Sep 2002, Hiroaki KAWAI wrote:
> No strong objection. +-0 for me.
>
> # IMHO, the default should be 'all.' For the purpose of the kind you
> # mentioned above, we should switch by arguments; like 'build en.'

The reason I am proposing "en" for the default is my continuing crusade to
make sure that the documentation does not become too complicated for the
developers (the people on the dev@httpd list).  The more hurdles we throw
in their way (like figuring out the right argument to the build script),
the less likely they are to do proper documentation.

Joshua.


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: Default build target (was Re: no doc for MaxMemFree or AddOutputFilterByType)

Posted by Hiroaki KAWAI <ha...@bcl.t.u-tokyo.ac.jp>.
> Does anyone (particularly people working on translations) have an
> objection to changing the default ant build target to only build "en", and
> have separate targets to build the other languages?  This would speed up
> the build for most people, and would also prevent people from accidentally
> screwing up work in languages they don't understand.

No strong objection. +-0 for me.

# IMHO, the default should be 'all.' For the purpose of the kind you 
# mentioned above, we should switch by arguments; like 'build en.'


Hiroaki Kawai
Department of Complexity Science and Engineering,
 The University of Tokyo
http://www.bcl.t.u-tokyo.ac.jp
mailto:hawk@bcl.t.u-tokyo.ac.jp

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: Default build target (was Re: no doc for MaxMemFree or AddOutputFilterByType)

Posted by David Shane Holden <dp...@yahoo.com>.
Joshua Slive wrote:
> On 13 Sep 2002, Jeff Trawick wrote:
> 
> 
>>Joshua Slive <jo...@slive.ca> writes:
>>
>>
>>>In particular, I suggest that you don't even commit the changes
>>>to non-english docs that may occur when you build.
>>>So why don't you regenerate your patch by doing
>>>cd httpd-2.0/docs/manual/mod/
>>>cvs diff *.html.en > docs-patch
>>
>>makes sense...  I'll commit the English changes only.
> 
> 
> Does anyone (particularly people working on translations) have an
> objection to changing the default ant build target to only build "en", and
> have separate targets to build the other languages?  This would speed up
> the build for most people, and would also prevent people from accidentally
> screwing up work in languages they don't understand.
> 
> Joshua.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
> For additional commands, e-mail: docs-help@httpd.apache.org
> 

+1 to separating each language into their own targets.

Shane



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: [PATCH] Re: Default build target

Posted by Erik Abele <er...@codefaktor.de>.
Erik Abele wrote:
> Another point came from an email from Michael Shroepl:
>  > I am +1 for the idea as well, and would love to have the
>  > target names available being documented in some short "how
>  > to build Apache HTML files from XML".
> 
> I we're going to commit this, I'm +1 on documenting the new 
> language-dependent build-process and even the validation process in some 
> (short) way in httpd-site/xdocs/docs-project/translations.xml
> 

Ehhh...meant the docsformat.xml page :-)

Erik



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


[PATCH] Re: Default build target

Posted by Erik Abele <er...@codefaktor.de>.
Joshua Slive wrote:
 >
 > Does anyone (particularly people working on translations) have an
 > objection to changing the default ant build target to only build 
"en", and
 > have separate targets to build the other languages?  This would speed up
 > the build for most people, and would also prevent people from 
accidentally
 > screwing up work in languages they don't understand.
 >
 > Joshua.
 >

I had a bit spare time and tried to incorporate the proposed additions
to build.xml. See the attached patch. For now 'en' is built as default.
All other languages are invoked by using their abbreviations (de, ja,
pt-br, ru). The validation process remained the same as before.
Additionally I introduced an new target 'all' to get all languages built
at once.

I also added the russian build targets submitted by Ilia Soldis
<s0...@tversu.ru>.

For me everything is working fine, but please test on your own system
with your working language thoroughly before anybody commits this. I
haven't had the time to test every case and I don't want to disturb the
build-process another time :-)

BTW we will have to do a rewrite of the dependsets when all the files
are xml-ized. Up to now only the mod-directory correctly depends on the
stylesheets/language-files.

Another point came from an email from Michael Shroepl:
 > I am +1 for the idea as well, and would love to have the
 > target names available being documented in some short "how
 > to build Apache HTML files from XML".

I we're going to commit this, I'm +1 on documenting the new 
language-dependent build-process and even the validation process in some 
(short) way in httpd-site/xdocs/docs-project/translations.xml

For any other additions or ideas, please speak up ;-)

Erik


Default build target (was Re: no doc for MaxMemFree or AddOutputFilterByType)

Posted by Joshua Slive <jo...@slive.ca>.
On 13 Sep 2002, Jeff Trawick wrote:

> Joshua Slive <jo...@slive.ca> writes:
>
> > In particular, I suggest that you don't even commit the changes
> > to non-english docs that may occur when you build.
> > So why don't you regenerate your patch by doing
> > cd httpd-2.0/docs/manual/mod/
> > cvs diff *.html.en > docs-patch
>
> makes sense...  I'll commit the English changes only.

Does anyone (particularly people working on translations) have an
objection to changing the default ant build target to only build "en", and
have separate targets to build the other languages?  This would speed up
the build for most people, and would also prevent people from accidentally
screwing up work in languages they don't understand.

Joshua.


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org


Re: no doc for MaxMemFree or AddOutputFilterByType

Posted by Jeff Trawick <tr...@attglobal.net>.
Joshua Slive <jo...@slive.ca> writes:

> In particular, I suggest that you don't even commit the changes
> to non-english docs that may occur when you build.
> So why don't you regenerate your patch by doing
> cd httpd-2.0/docs/manual/mod/
> cvs diff *.html.en > docs-patch

makes sense...  I'll commit the English changes only.

>                                           The other thing that should
> be done to cut down on the diffs is to insert some line-breaks in the
> process for generating directives.html (and a few other files).

yessir!

-- 
Jeff Trawick | trawick@attglobal.net
Born in Roswell... married an alien...

Re: no doc for MaxMemFree or AddOutputFilterByType

Posted by Jeff Trawick <tr...@attglobal.net>.
Joshua Slive <jo...@slive.ca> writes:

> In particular, I suggest that you don't even commit the changes
> to non-english docs that may occur when you build.
> So why don't you regenerate your patch by doing
> cd httpd-2.0/docs/manual/mod/
> cvs diff *.html.en > docs-patch

makes sense...  I'll commit the English changes only.

>                                           The other thing that should
> be done to cut down on the diffs is to insert some line-breaks in the
> process for generating directives.html (and a few other files).

yessir!

-- 
Jeff Trawick | trawick@attglobal.net
Born in Roswell... married an alien...

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org