Re: Question about r1584417

[Eric Covener]

On Mon, May 1, 2017 at 4:47 AM, Christophe JAILLET
 wrote:
> This was added in trunk in r1584417 but apparently never backported. Should
> it be or should the trunk doc only mention 2.5?

Seems like ideal would be to backport it, leaving the 2.4.10 reference
in both releases.

-- 
Eric Covener
cove...@gmail.com

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

Question about r1584417

[Christophe JAILLET]

Hi,

in https://httpd.apache.org/docs/trunk/en/rewrite/flags.html#flag_b, 
there is a note about a new behavior in 2.4.10+.


However, this note is not present in the 2.4.x documentation.

This was added in trunk in r1584417 but apparently never backported. 
Should it be or should the trunk doc only mention 2.5?


CJ


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

Re: Question about prettify.js

[Yann Ylavic]

Hi Christophe,

On Wed, Dec 28, 2016 at 10:07 AM, Christophe JAILLET
 wrote:
>
> At line 920, in PR_TAG, why is there: Proxy\b
>
> Why is there a \b for this tag only? Is it really useful?
> The whole regex is already delimited by some \b (Word Boundaries), so why an
> extra one, in the middle?

Looks like a typo from http://svn.apache.org/r1330278, can probably be
"fixed" with no issue (note that prettify.min.js, generated from
prettify.js after r1330278, seems to have the same typo).

Regards,
Yann.

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

Question about prettify.js

[Christophe JAILLET]

Hi,

I was looking at 'docs/manual/style/script/prettify.js' in order to 
update the list of the directives used for syntax highlight in the doc.

How ever, I have a question.

At line 920, in PR_TAG, why is there: Proxy\b

Why is there a \b for this tag only? Is it really useful?
The whole regex is already delimited by some \b (Word Boundaries), so 
why an extra one, in the middle?


CJ




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

Re: Question

[Luis Gil]

On Tue, 10 May 2016 at 16:02 Eric Covener  wrote:

> On Tue, May 10, 2016 at 6:58 AM, Luis Gil 
> wrote:
> > I had came across with "Authn/Authz" i guess this is a
> > abbreviation of Authentication -authorization or is it a specific name we
> > got in the pages?
>
> An abbreviation/shorthand.  In most contexts I would think it's
> probably better to expand it in the manual.
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
>
Ok thanks.
In the translation (es)  im expanding them, if so i can expand it on the
English versions of the xml i pass through.
-- 

Luis J.G

Question

[Luis Gil]

hello folks
I had came across with "Authn/Authz" i guess this is a
abbreviation of Authentication -authorization or is it a specific name we
got in the pages?
I'm just getting confused
-- 

Luis J.G

Re: Question

[Eric Covener]

On Tue, May 10, 2016 at 6:58 AM, Luis Gil  wrote:
> I had came across with "Authn/Authz" i guess this is a
> abbreviation of Authentication -authorization or is it a specific name we
> got in the pages?

An abbreviation/shorthand.  In most contexts I would think it's
probably better to expand it in the manual.

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

Re: ProxyPassReverse documentation question

[Rich Bowen]

On 08/14/2015 08:44 AM, Eric Covener wrote:

On Fri, Aug 14, 2015 at 8:20 AM, Mike Rumph mike.ru...@oracle.com wrote:

pass-through


It should remain  [P] -- I would actually drop the passthrough term
altogether on the mod_proxy side



+1

proxy pass-through is a confusing phrase.


--
Rich Bowen - rbo...@rcbowen.com - @rbowen
http://apachecon.com/ - @apachecon

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

ProxyPassReverse documentation question

[Mike Rumph]

While doing a grammar review of the mod_proxy documentation,
I came across the following excerpt in the ProxyPassReverse Directive 
section:


Note that this |ProxyPassReverse| directive can also be used in 
conjunction with the proxy pass-through feature (|RewriteRule ... [P]|) 
from |mod_rewrite 
http://httpd.apache.org/docs/trunk/mod/mod_rewrite.html| because it 
doesn't depend on a corresponding |ProxyPass 
http://httpd.apache.org/docs/trunk/mod/mod_proxy.html#proxypass| 
directive.


- http://httpd.apache.org/docs/trunk/mod/mod_proxy.html#proxypassreverse
- http://httpd.apache.org/docs/trunk/mod/mod_rewrite.html#rewriterule

But the RewriteRule documentation includes the following two table entries:

- proxy|P:  Force the substitution URL to be internally sent as a proxy 
request.
- passthrough|PT:  Forces the resulting URI to be passed back to the URL 
mapping engine for processing of other URI-to-filename translators, such 
as |Alias| or |Redirect|.


So does the RewriteRule example in the ProxyPassReverse documentation 
need to be changed to [PT],
or is the [P] correct and the description (the proxy pass-through 
feature) needs to be worded differently?


Also, I see dictionary entries for passthrough as well as 
pass-through and pass through.

Which of these is the best for our purpose?

- http://encyclopedia2.thefreedictionary.com/passthrough
- http://encyclopedia2.thefreedictionary.com/pass-through
- http://www.thefreedictionary.com/pass+through

Thanks,

Mike Rumph

Re: ProxyPassReverse documentation question

[Eric Covener]

On Fri, Aug 14, 2015 at 8:20 AM, Mike Rumph mike.ru...@oracle.com wrote:
 pass-through

It should remain  [P] -- I would actually drop the passthrough term
altogether on the mod_proxy side

-- 
Eric Covener
cove...@gmail.com

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

Re: ProxyPassReverse documentation question

[Mike Rumph]

Thanks Eric,

That is the direction I thought most likely.
The use of the word pass-through made this mod_proxy passage confusing.

On 8/14/2015 5:44 AM, Eric Covener wrote:

On Fri, Aug 14, 2015 at 8:20 AM, Mike Rumph mike.ru...@oracle.com wrote:

pass-through

It should remain  [P] -- I would actually drop the passthrough term
altogether on the mod_proxy side




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

Re: question about committing

[Lucien Gentis]

Le 16/05/2014 17:44, André Malo a écrit :
 * Takashi Sato wrote:

 Hi,

 your commit r1594560 contains three things:

 (1) your modification of french XML, for example, glossary.xml.fr
 (2) build results related to (1), for example, glossary.html.fr.
 (3) build results not related to (1), for example,

httpd/httpd/trunk/docs/manual/mod/allmodules.xml.fr
httpd/httpd/trunk/docs/manual/mod/core.html.fr
httpd/httpd/trunk/docs/manual/mod/index.html.fr
httpd/httpd/trunk/docs/manual/mod/mod_authnz_ldap.html.fr
httpd/httpd/trunk/docs/manual/mod/mod_authz_dbm.html.fr
httpd/httpd/trunk/docs/manual/mod/mod_authz_groupfile.html.fr
httpd/httpd/trunk/docs/manual/mod/mod_authz_host.html.fr
 I think there is no consensus whether (1) and (2) should been
 committed separately or not.
 IMHO at least (3) should been committed separately from (1).
 Technically xml and html/meta files should be committed separately, because 
 the translation revision numbering will be only correct after this first 
 step. After that I'd just commit everything that's been transformed.

 nd
Hi,

So today I had only one file to update : expr.xml.fr in trunk and 2.4
branches.

I made 2 separate commits :

1.  manual/expr.xml.fr - trunk branch
2.  manual/expr.xml.fr - 2.4 branch

build trunk and 2.4 branch, then 2 other separate commits :.

3.  manual/expr.html.fr - trunk branch
4.  manual/expr.html.fr - 2.4 branch

Is it OK ?


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

Re: question about committing

[André Malo]

* Lucien Gentis wrote:

 Le 16/05/2014 17:44, André Malo a écrit :
  * Takashi Sato wrote:
  Hi,
 
  your commit r1594560 contains three things:
 
  (1) your modification of french XML, for example, glossary.xml.fr
  (2) build results related to (1), for example, glossary.html.fr.
  (3) build results not related to (1), for example,
 
 httpd/httpd/trunk/docs/manual/mod/allmodules.xml.fr
 httpd/httpd/trunk/docs/manual/mod/core.html.fr
 httpd/httpd/trunk/docs/manual/mod/index.html.fr
 httpd/httpd/trunk/docs/manual/mod/mod_authnz_ldap.html.fr
 httpd/httpd/trunk/docs/manual/mod/mod_authz_dbm.html.fr
 httpd/httpd/trunk/docs/manual/mod/mod_authz_groupfile.html.fr
 httpd/httpd/trunk/docs/manual/mod/mod_authz_host.html.fr
 
  I think there is no consensus whether (1) and (2) should been
  committed separately or not.
  IMHO at least (3) should been committed separately from (1).
 
  Technically xml and html/meta files should be committed separately,
  because the translation revision numbering will be only correct after
  this first step. After that I'd just commit everything that's been
  transformed.
 
  nd

 Hi,

 So today I had only one file to update : expr.xml.fr in trunk and 2.4
 branches.

 I made 2 separate commits :

 1.  manual/expr.xml.fr - trunk branch
 2.  manual/expr.xml.fr - 2.4 branch

 build trunk and 2.4 branch, then 2 other separate commits :.

 3.  manual/expr.html.fr - trunk branch
 4.  manual/expr.html.fr - 2.4 branch

 Is it OK ?

Yep, that should be fine.

nd
-- 
Gib' mal folgendes in die Kommandozeile ein (und einen Moment warten):

net send localhost Buuuh!
Na, erschreckt?  -- Markus Becker in mpdsh

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

Re: question about committing

[André Malo]

* Takashi Sato wrote:

 Hi,

 your commit r1594560 contains three things:

 (1) your modification of french XML, for example, glossary.xml.fr
 (2) build results related to (1), for example, glossary.html.fr.
 (3) build results not related to (1), for example,

 httpd/httpd/trunk/docs/manual/mod/allmodules.xml.fr
 httpd/httpd/trunk/docs/manual/mod/core.html.fr
 httpd/httpd/trunk/docs/manual/mod/index.html.fr
 httpd/httpd/trunk/docs/manual/mod/mod_authnz_ldap.html.fr
 httpd/httpd/trunk/docs/manual/mod/mod_authz_dbm.html.fr
 httpd/httpd/trunk/docs/manual/mod/mod_authz_groupfile.html.fr
 httpd/httpd/trunk/docs/manual/mod/mod_authz_host.html.fr

 I think there is no consensus whether (1) and (2) should been
 committed separately or not.
 IMHO at least (3) should been committed separately from (1).

Technically xml and html/meta files should be committed separately, because 
the translation revision numbering will be only correct after this first 
step. After that I'd just commit everything that's been transformed.

nd
-- 
$_=q?tvc!uif)%*|#Bopuifs!A`#~tvc!Xibu)%*|qsjou#Kvtu!A`#~tvc!KBQI!)*|~
tvc!ifmm)%*|#Qfsm!A`#~tvc!jt)%*|(Ibdlfs(~  # What the hell is JAPH? ;
@_=split/\s\s+#/;$_=(join''=map{chr(ord(  # André Malo ;
$_)-1)}split//=$_[0]).$_[1];s s.*s$_see;  #  http://www.perlig.de/ ;

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

Re: question about committing

[Lucien Gentis]

Le 15/05/2014 07:44, Takashi Sato a écrit :
 Hi,

 your commit r1594560 contains three things:

 (1) your modification of french XML, for example, glossary.xml.fr
 (2) build results related to (1), for example, glossary.html.fr.
 (3) build results not related to (1), for example,

httpd/httpd/trunk/docs/manual/mod/allmodules.xml.fr
httpd/httpd/trunk/docs/manual/mod/core.html.fr
httpd/httpd/trunk/docs/manual/mod/index.html.fr
httpd/httpd/trunk/docs/manual/mod/mod_authnz_ldap.html.fr
httpd/httpd/trunk/docs/manual/mod/mod_authz_dbm.html.fr
httpd/httpd/trunk/docs/manual/mod/mod_authz_groupfile.html.fr
httpd/httpd/trunk/docs/manual/mod/mod_authz_host.html.fr
 I think there is no consensus whether (1) and (2) should been
 committed separately or not.
 IMHO at least (3) should been committed separately from (1).

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

Hi,

OK, in addition to modifications of french XML files, I also had updates
of files that were not up to date (indicated by the build output) ; and
I made a build and committed all modifications together.

But certain files are automatically modified during a build process !
For example, I didn't modified allmodules.xml.fr myself
So, how to commit them separately ?





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

Re: question about committing

[Takashi Sato]

Hi,

your commit r1594560 contains three things:

(1) your modification of french XML, for example, glossary.xml.fr
(2) build results related to (1), for example, glossary.html.fr.
(3) build results not related to (1), for example,

httpd/httpd/trunk/docs/manual/mod/allmodules.xml.fr
httpd/httpd/trunk/docs/manual/mod/core.html.fr
httpd/httpd/trunk/docs/manual/mod/index.html.fr
httpd/httpd/trunk/docs/manual/mod/mod_authnz_ldap.html.fr
httpd/httpd/trunk/docs/manual/mod/mod_authz_dbm.html.fr
httpd/httpd/trunk/docs/manual/mod/mod_authz_groupfile.html.fr
httpd/httpd/trunk/docs/manual/mod/mod_authz_host.html.fr

I think there is no consensus whether (1) and (2) should been
committed separately or not.
IMHO at least (3) should been committed separately from (1).

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

Re: question about committing

[Lucien Gentis]

Le 14/05/2014 14:52, Eric Covener a écrit :
 On Tue, May 13, 2014 at 8:50 AM, Lucien Gentis
 lucien.gen...@univ-lorraine.fr wrote:
 I believed doc was build automatically and periodically, but apparently,
 this is not the case : for example, I updated core.xml.fr (2.4 branch)
 at the end of april, and corresponding html file is not yet updated.
 I think the only periodic part is someone occasionally builds the docs
 and notices there are uncommitted changes and checks them in. I think
 ideally, you checkin the changed XML then checkin the generated
 portions.


That's the way I do yet.

Additionally, ./build.sh fr command tells if there are files which are
not up to date.

Thanks Eric


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

Re: question about committing

[Eric Covener]

On Tue, May 13, 2014 at 8:50 AM, Lucien Gentis
lucien.gen...@univ-lorraine.fr wrote:
 I believed doc was build automatically and periodically, but apparently,
 this is not the case : for example, I updated core.xml.fr (2.4 branch)
 at the end of april, and corresponding html file is not yet updated.

I think the only periodic part is someone occasionally builds the docs
and notices there are uncommitted changes and checks them in. I think
ideally, you checkin the changed XML then checkin the generated
portions.

-- 
Eric Covener
cove...@gmail.com

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

question about committing

[Lucien Gentis]

Hello everybody,

Since several years, I commit my updates of doc files (french
translation) this way :

--- I open .xml.fr file to update in a text editor
--- I record the updated .xml.fr file
--- I check if there isn't any syntax error through ./build.sh
validate-xml command
--- I commit my changes through svn commit command

. . . and that's all !

Am I right, or have I to build the doc before committing ?

I believed doc was build automatically and periodically, but apparently,
this is not the case : for example, I updated core.xml.fr (2.4 branch)
at the end of april, and corresponding html file is not yet updated.

Regards

Lucien

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

question about flags.xml - trunk branch

[Lucien Gentis]

Hello everybody,

In flags.xml - trunk branch - line 99 :

pAn alternative to this flag is using a directive module=mod_rewrite
RewriteCond/directive to capture against %{THE_REQUEST} which will
capture
strings in the encoded form./p

I don't understand the meaning of to capture against %{THE_REQUEST}.


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

回复: question about flags.xml - trunk branch

[cd93...@gmail.com]

Hello everybody,

In flags.xml - trunk branch - line 99 :

pAn alternative to this flag is using a directive module=mod_rewrite
RewriteCond/directive to capture against %{THE_REQUEST} which will
capture
strings in the encoded form./p

I don't understand the meaning of to capture against %{THE_REQUEST}.


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

Re: question about flags.xml - trunk branch

[Eric Covener]

On Sat, Apr 5, 2014 at 10:55 AM, Lucien Gentis
lucien.gen...@univ-lorraine.fr wrote:
 Hello everybody,

 In flags.xml - trunk branch - line 99 :

 pAn alternative to this flag is using a directive module=mod_rewrite
RewriteCond/directive to capture against %{THE_REQUEST} which will
 capture
 strings in the encoded form./p

 I don't understand the meaning of to capture against %{THE_REQUEST}.

If you capture something with a normal rewriterule, it has already been decoded.
If you capture against %{THE_REQUEST} in a rewritecond, it's still
escaped as the client originally sent it.

So if you have some problem where not specifying [B] is broken, and
specifying [B] is also broken, you can often avoid the backref
escaping issue by capturing %{THE_REQUEST} in a condition and using
%1.

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

Re: question about flags.xml - trunk branch

[Lucien Gentis]

Le 05/04/2014 17:03, Eric Covener a écrit :
 On Sat, Apr 5, 2014 at 10:55 AM, Lucien Gentis
 lucien.gen...@univ-lorraine.fr wrote:
 Hello everybody,

 In flags.xml - trunk branch - line 99 :

 pAn alternative to this flag is using a directive module=mod_rewrite
 RewriteCond/directive to capture against %{THE_REQUEST} which will
 capture
 strings in the encoded form./p

 I don't understand the meaning of to capture against %{THE_REQUEST}.
 If you capture something with a normal rewriterule, it has already been 
 decoded.
 If you capture against %{THE_REQUEST} in a rewritecond, it's still
 escaped as the client originally sent it.

 So if you have some problem where not specifying [B] is broken, and
 specifying [B] is also broken, you can often avoid the backref
 escaping issue by capturing %{THE_REQUEST} in a condition and using
 %1.

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

Thanks Eric, your answer is very clear.

Lucien

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

question

[Lucien GENTIS]

Hello,

In mode_cache.xml, env.xml, mod_ssl.xml, what does ...after Apache
2.2.11... mean ?

in 2.2.11 versions and later, or
in versions later than 2.2.11 (say . . . 2.2.12 if it'll exist) ?

Lucien




--
Lucien GENTIS
IUFM de Lorraine
Centre de Ressources Informatiques
5, Rue Paul Richard
C.O. 3 - MAXEVILLE
54528 LAXOU-CEDEX

Tél. 03 83 17 68 41
Email : lucien.gen...@lorraine.iufm.fr

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

Re: question

[Lucien GENTIS]

Dan Poirier a écrit :

Lucien GENTIS lucien.gen...@lorraine.iufm.fr writes:

  

In mode_cache.xml, env.xml, mod_ssl.xml, what does ...after Apache
2.2.11... mean ?

in 2.2.11 versions and later, or
in versions later than 2.2.11 (say . . . 2.2.12 if it'll exist) ?



In versions later than 2.2.11  As you say, we don't know for sure if
2.2.12 will be released, or we could just say In 2.2.12 and later.
Maybe there's a better way to say this, though.

  

Thanks, that's all I wanted to know :-)

--
Lucien GENTIS
IUFM de Lorraine
Centre de Ressources Informatiques
5, Rue Paul Richard
C.O. 3 - MAXEVILLE
54528 LAXOU-CEDEX

Tél. 03 83 17 68 41
Email : lucien.gen...@lorraine.iufm.fr

html question after changing mod/mod_proxy.xml (2.2.x)

[Jean-Frederic]

Hi,

I have changed in 2.2.x docs/manual/mod/mod_proxy.xml (backporting
missing documentation) but after running (cd build; build.sh). I have
more html/xml files changed than excepted:

+++
svn diff . | grep Index
Index: mod/mod_cache.xml.ja
Index: mod/mod_cache.xml.ko
Index: mod/mpm_common.xml.meta
Index: mod/mod_proxy_ajp.xml.ja
Index: mod/mod_proxy.xml
Index: mod/directives.html.en
Index: mod/mod_proxy.xml.ja
Index: mod/mod_proxy_ajp.xml.meta
Index: mod/quickreference.html.en
Index: mod/mod_cache.html.en
Index: mod/mod_proxy.html.en
+++

Any hints?

Cheers

Jean-Frederic




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

html question after changing mod/mod_proxy.xml (2.2.x)

[Jean-Frederic]

Hi,

I have changed in 2.2.x docs/manual/mod/mod_proxy.xml (backporting
missing documentation) but after running (cd build; build.sh). I have
more html/xml files changed than excepted:

+++
svn diff . | grep Index
Index: mod/mod_cache.xml.ja
Index: mod/mod_cache.xml.ko
Index: mod/mpm_common.xml.meta
Index: mod/mod_proxy_ajp.xml.ja
Index: mod/mod_proxy.xml
Index: mod/directives.html.en
Index: mod/mod_proxy.xml.ja
Index: mod/mod_proxy_ajp.xml.meta
Index: mod/quickreference.html.en
Index: mod/mod_cache.html.en
Index: mod/mod_proxy.html.en
+++

Any hints?

Cheers

Jean-Frederic



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: html question after changing mod/mod_proxy.xml (2.2.x)

[Rich Bowen]

On Jun 19, 2007, at 08:17, Jean-Frederic wrote:


Hi,

I have changed in 2.2.x docs/manual/mod/mod_proxy.xml (backporting
missing documentation) but after running (cd build; build.sh). I have
more html/xml files changed than excepted:

+++
svn diff . | grep Index
Index: mod/mod_cache.xml.ja
Index: mod/mod_cache.xml.ko
Index: mod/mpm_common.xml.meta
Index: mod/mod_proxy_ajp.xml.ja
Index: mod/mod_proxy.xml
Index: mod/directives.html.en
Index: mod/mod_proxy.xml.ja
Index: mod/mod_proxy_ajp.xml.meta
Index: mod/quickreference.html.en
Index: mod/mod_cache.html.en
Index: mod/mod_proxy.html.en
+++


Assuming you only modified the english version, you should commit  
only mod_proxy.xml and mod_proxy.html.en
The other file changes are (probably) artifacts of the fact that the  
build process always seems to be slightly different from one machine  
to another, for reasons that I've never ascertained.


--
Rich Bowen
[EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: html question after changing mod/mod_proxy.xml (2.2.x)

[Jean-Frederic]

On Tue, 2007-06-19 at 10:43 -0400, Rich Bowen wrote:
 On Jun 19, 2007, at 08:17, Jean-Frederic wrote:
 
  Hi,
 
  I have changed in 2.2.x docs/manual/mod/mod_proxy.xml (backporting
  missing documentation) but after running (cd build; build.sh). I have
  more html/xml files changed than excepted:
 
  +++
  svn diff . | grep Index
  Index: mod/mod_cache.xml.ja
  Index: mod/mod_cache.xml.ko
  Index: mod/mpm_common.xml.meta
  Index: mod/mod_proxy_ajp.xml.ja
  Index: mod/mod_proxy.xml
  Index: mod/directives.html.en
  Index: mod/mod_proxy.xml.ja
  Index: mod/mod_proxy_ajp.xml.meta
  Index: mod/quickreference.html.en
  Index: mod/mod_cache.html.en
  Index: mod/mod_proxy.html.en
  +++
 
 Assuming you only modified the english version, you should commit  
 only mod_proxy.xml and mod_proxy.html.en

Done.

Cheers

Jean-Frederic

 The other file changes are (probably) artifacts of the fact that the  
 build process always seems to be slightly different from one machine  
 to another, for reasons that I've never ascertained.
 
 --
 Rich Bowen
 [EMAIL PROTECTED]
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

docs question

[Issac Goldstand]

I have a question about doc commits.  I understand that changes need to
be made in xdocs directory and ant will rebuild the files in docs.  Does
ant need to be run locally and both xdocs and docs committed or is it
enough to commit changes to xdocs, do an svn update on people.apache.org
and ant will be run there?

I ask in expectation that I'll need to update the release info for the
forthcoming apreq release
(http://marc.info/?l=apache-modperlm=118054808003929w=2)

Thanks,
  Issac

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: docs question

[Mads Toftum]

On Tue, Jun 05, 2007 at 09:45:15AM +0300, Issac Goldstand wrote:
 I have a question about doc commits.  I understand that changes need to
 be made in xdocs directory and ant will rebuild the files in docs.  Does
 ant need to be run locally and both xdocs and docs committed or is it
 enough to commit changes to xdocs, do an svn update on people.apache.org
 and ant will be run there?
 
xdocs needs to be run locally and both the xml and resulting html has to
be committed  - at least that's how it is done with the httpd docs.

vh

Mads Toftum
-- 
http://soulfood.dk

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Question to committers from recently born committer

[Ilia Soldis]

I don't understand the behaviour of 
cvs-commit messages. I didn't find the answers at committer's FAQ at http://www.apache.org/dev
The question is - how cvs-commit messages are 
generated: automatically by server or manually by a committer? In a latter case: 
how should it be done?
Or may be it is not a question I should worry 
about?

Re: Question to committers from recently born committer

[Joshua Slive]

On Mon, 7 Jul 2003, Thom May wrote:

 * Ilia Soldis ([EMAIL PROTECTED]) wrote :
  I don't understand the behaviour of cvs-commit messages. I didn't find the 
  answers at committer's FAQ at http://www.apache.org/dev
  The question is - how cvs-commit messages are generated: automatically by 
  server or manually by a committer? In a latter case: how should it be done?
  Or may be it is not a question I should worry about?

 they're generated automatically.
 If you've not seen commits come through that you've done, it's because the
 list moderator hasn't allowed emails from your account yet.

Also, just to be clear, you need to be subscribed to the
[EMAIL PROTECTED] mailing list.  All serious docs contributors should
be subscribed there, although it is slightly less necessary for someone
who works only on translations.

Joshua.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Question to non-latin Translators

[Yoshiki Hayashi]

André Malo [EMAIL PROTECTED] writes:

 I'm currently working at a letter bar for the glossary. How will/would
 you translate this page? Does a letter bar make any sense there in your
 language? Should it be dropped? (this could easily be done by leaving a
 note in $lang.xml, for instance messages lang=ja dropletters=yes
 or so)

As for Japanese translation, most translated terms would not
start with latin alphabet so it would better to drop letter
bar.

 If it makes no sense at all: are there alternatives you'd like to see?

Usually Japanese terms are sorted with the pronounciation of
words and indexed with the first sound but I don't think it
would be worth the effort to write such XSLT until glossary
becomes very big.

-- 
Yoshiki Hayashi

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Question to non-latin Translators

[André Malo]

Since I've nearly no knowledge about Japanase or Chinese languages:

I'm currently working at a letter bar for the glossary. How will/would
you translate this page? Does a letter bar make any sense there in your
language? Should it be dropped? (this could easily be done by leaving a
note in $lang.xml, for instance messages lang=ja dropletters=yes
or so)
If it makes no sense at all: are there alternatives you'd like to see?

How will the Russian translation handle the contents of the dts?

Feedback would be much appreciated.

nd
-- 
die (eval q-qq:Just Another Perl Hacker
:-)

# André Malo, http://www.perlig.de/ #

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Newbie question: Is there Apache API doc?

[Andrey Melnikov]

Hello, all!

I browsed httpd.apache.org website but couldn't find good documentation
on Apache modules API. I only found  several articles and
http://httpd.apache.org/dev/apidoc/ draft.

So I have 2 questions:

1. Is http://httpd.apache.org/dev/apidoc/ the best manual I can get? 2.
If there is no any other documentation, where should I ask questions
regarding Apache API? I need to write a module but have to use sources
as a reference :(

Andrew.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Question on install.xml/install.html.en

[Astrid Keßler]

 The compiling and installing documentation contains at Requirements 
 Perl 5:
 
 For some of the support scripts like apxs or dbmmanage (which are
 written in Perl) the Perl 5 interpreter is required (versions 5.003 and
 5.004 are fine)

 5.003/5.004 are very old. Current Perl Version is 5.8. So this sentence
 seems like never changed since it has been written. Shouldn't we change
 it to soumething like:

 For some of the support scripts like apxs or dbmmanage (which are
 written in Perl) the Perl 5 interpreter is required (versions 5.003 and
 5.004 are sufficient)

 or maybe suggest a newer version?

 Kess

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Question on install.xml/install.html.en

[Justin Erenkrantz]

On Sun, Sep 15, 2002 at 02:53:06AM +0200, Astrid Keßler wrote:
  For some of the support scripts like apxs or dbmmanage (which are
  written in Perl) the Perl 5 interpreter is required (versions 5.003 and
  5.004 are sufficient)

5.003 or newer are sufficient.  -- justin

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Question about testing pages

[Luiz Rocha]

Hi everyone,

  I have (really dumb) question. How do you guys test the error pages? Do you 
make apache return the expected error to check if the *.html.var is working, or 
there is a more smart way to test it?

  I just translated some error pages and I wanted to test before submitting it.

Thank in advance,

Luiz Rocha
http://lsdr.net
-- 
Get your free email from www.linuxmail.org 


Powered by Outblaze

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Another XML question

[Patrik Grip-Jansson]

On Sat, 2 Mar 2002, Joshua Slive wrote:

  In mod_include I hvae a link that looks like:
  a href=mod_cgi.htmlCGI/a
  What is the correct way to do this with the module tag?
 I thought about that a little, and I think it is right the way it is.  A
 module tag designates the name of a module.  If you want to link to a
 module without using its name, an ordinary link is correct IMHO.

Is really a good idea to use a html href? If we want to convert the xml 
into something else (pdf, clay tables, what ever) it's probably easier if 
we were to use some of our own markups.

-- 
.-.
| Patrik Grip-Jansson |
| Ringen 4B   |..
| 78444 Borlänge   .--'' http://gnulix.com/ `-.
| Sweden   |  All views and opinions are my own,  |
`--| PH:+46(0)24382823 PW:+46(0)707354360 |
   `--'


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Another XML question

[Rich Bowen]

In mod_include I hvae a link that looks like:

a href=mod_cgi.htmlCGI/a

What is the correct way to do this with the module tag?

-- 
Rich Bowen - [EMAIL PROTECTED]
As we trace our own few circles around the sun
We get it backwards and our seven years go by like one
Dog Years (Rush - Test for Echo - 1999)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Another XML question

[Joshua Slive]

On Sat, 2 Mar 2002, Rich Bowen wrote:

 In mod_include I hvae a link that looks like:

 a href=mod_cgi.htmlCGI/a

 What is the correct way to do this with the module tag?

I thought about that a little, and I think it is right the way it is.  A
module tag designates the name of a module.  If you want to link to a
module without using its name, an ordinary link is correct IMHO.

Joshua.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]