Fwd: sugestions

[Luis Gil]

Hello:
I have started translating the apache Doc into spanish and i get the
following error:
[image: Inline images 1]
Does any one can help?
i have to say that the perl is in the path and it should be not getting the
file not fount because it is there... and i dont want to mess around with
this
thx in advance
Linkedin:   https://linkd.in/Ljjt8L http://linkd.in/Ljjt8L
Twitter : https://twitter.com/luigy_tspg

[no subject]

[Luis Gil]

Linkedin:   https://linkd.in/Ljjt8L http://linkd.in/Ljjt8L
Twitter : https://twitter.com/luigy_tspg
Index: index.html.es
===
--- index.html.es   (revision 0)
+++ index.html.es   (working copy)
@@ -0,0 +1,48 @@
+?xml version=1.0 encoding=ISO-8859-1?
+!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN 
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;
+html xmlns=http://www.w3.org/1999/xhtml; lang=es xml:lang=eshead!--
+X
+  This file is generated from xml source: DO NOT EDIT
+X
+  --
+titlePreguntas Frecuentes - Servidor HTTP Apache Versión 2.4/title
+link href=../style/css/manual.css rel=stylesheet media=all 
type=text/css title=Main stylesheet /
+link href=../style/css/manual-loose-100pc.css rel=alternate stylesheet 
media=all type=text/css title=No Sidebar - Default font size /
+link href=../style/css/manual-print.css rel=stylesheet media=print 
type=text/css /link rel=stylesheet type=text/css 
href=../style/css/prettify.css /
+script src=../style/scripts/prettify.min.js type=text/javascript
+/script
+
+link href=../images/favicon.ico rel=shortcut icon //head
+body id=manual-page class=no-sidebardiv id=page-header
+p class=menua href=../mod/Módulos/a | a 
href=../mod/directives.htmlDirectivas/a | a 
href=http://wiki.apache.org/httpd/FAQ;Preguntas Frecuentes/a | a 
href=../glossary.htmlGlosario/a | a href=../sitemap.htmlMapa del sitio 
web/a/p
+p class=apacheVersión 2.4 del Servidor HTTP Apache/p
+img alt= src=../images/feather.gif //div
+div class=upa href=../img title=lt;- alt=lt;- 
src=../images/left.gif //a/div
+div id=path
+a href=http://www.apache.org/;Apache/a gt; a 
href=http://httpd.apache.org/;Servidor HTTP/a gt; a 
href=http://httpd.apache.org/docs/;Documentación/a gt; a 
href=../Versión 2.4/a/divdiv id=page-contentdiv 
id=preambleh1Preguntas Frecuentes/h1
+div class=toplang
+pspanIdiomas disponibles: /spana href=../en/faq/ hreflang=en 
rel=alternate title=Englishnbsp;ennbsp;/a |
+a href=../es/faq/ title=Españolnbsp;esnbsp;/a |
+a href=../fr/faq/ hreflang=fr rel=alternate 
title=Françaisnbsp;frnbsp;/a |
+a href=../tr/faq/ hreflang=tr rel=alternate 
title=Türkçenbsp;trnbsp;/a |
+a href=../zh-cn/faq/ hreflang=zh-cn rel=alternate title=Simplified 
Chinesenbsp;zh-cnnbsp;/a/p
+/div
+
+
+pEsta sección se ha movido a a 
href=http://wiki.apache.org/httpd/FAQ;HTTP Server Wiki/a./p
+/div
+/div
+div class=bottomlang
+pspanIdiomas disponibles: /spana href=../en/faq/ hreflang=en 
rel=alternate title=Englishnbsp;ennbsp;/a |
+a href=../es/faq/ title=Españolnbsp;esnbsp;/a |
+a href=../fr/faq/ hreflang=fr rel=alternate 
title=Françaisnbsp;frnbsp;/a |
+a href=../tr/faq/ hreflang=tr rel=alternate 
title=Türkçenbsp;trnbsp;/a |
+a href=../zh-cn/faq/ hreflang=zh-cn rel=alternate title=Simplified 
Chinesenbsp;zh-cnnbsp;/a/p
+/divdiv id=footer
+p class=apacheCopyright 2014 The Apache Software Foundation.br /Licencia 
bajo los términos de la a 
href=http://www.apache.org/licenses/LICENSE-2.0;Apache License, Version 
2.0/a./p
+p class=menua href=../mod/Módulos/a | a 
href=../mod/directives.htmlDirectivas/a | a 
href=http://wiki.apache.org/httpd/FAQ;Preguntas Frecuentes/a | a 
href=../glossary.htmlGlosario/a | a href=../sitemap.htmlMapa del sitio 
web/a/p/divscript type=text/javascript!--//--![CDATA[//!--
+if (typeof(prettyPrint) !== 'undefined') {
+prettyPrint();
+}
+//--!]]/script
+/body/html
\ No newline at end of file
Index: index.xml.es
===
--- index.xml.es(revision 0)
+++ index.xml.es(working copy)
@@ -0,0 +1,34 @@
+?xml version='1.0' encoding='UTF-8' ?
+!DOCTYPE manualpage SYSTEM ../style/manualpage.dtd
+?xml-stylesheet type=text/xsl href=../style/manual.es.xsl?
+!-- $LastChangedRevision: 1044378 $ --
+
+!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements.  See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the License); you may not use this file except in compliance with
+ the License.  You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an AS IS BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+--
+
+manualpage metafile=index.xml.meta
+parentdocument href=..//
+
+titlePreguntas Frecuentes/title
+
+summary
+
+pEsta secci#243;n se ha movido a a
+href=http://wiki.apache.org/httpd/FAQ;HTTP Server Wiki/a./p

Re: (translation of index.es)

[Luis Gil]

Hi:
yes, i realized i got misspelled the directory a few minutes before sending
the screenshot, ;)
Its from the 2.4 branch
the full path that is supposed to be is httpd-2.4\manual\faq
i resend the files with the comments.
Thax for the answers!!

Linkedin:   https://linkd.in/Ljjt8L http://linkd.in/Ljjt8L
Twitter : https://twitter.com/luigy_tspg

On 3 December 2014 at 22:04, André Malo n...@perlig.de wrote:

 Hi again,

 If you submit files, please specify, which branch they are for (trunk, 2.4
 or 2.2).
 Also, for translations only the xml file is really needed as the rest is
 generated.

 Then your xml file is missing the translation info, like this (picked from
 a
 french file, look, for example in index.xml.fr):

 !-- French translation : Lucien GENTIS --
 !-- Reviewed by : Vincent Deffontaines --
 !-- English Revision : 1524238 --

 The first two lines are optional; the last line however should be there. It
 specifies the revision number of the LastChangedRevision line of the
 English file at the time of translating it.
 The build process modifies this line whenever the English original changes
 and that way keeps track of what needs to be changed in the translations.
 The LastChangedRevision line is only needed for the English originals.

 Furthermore, if you can find a reviewer, that would be fine. If not, well,
 nothing we can do about it right now. I think, we loosened the requirement
 some time ago, so when you fix your submission, we can certainly commit it.

 Thanks!

 nd
 --
 Solides und umfangreiches Buch
   -- aus einer Rezension

 http://pub.perlig.de/books.html#apache2

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




index.html.es
Description: Binary data


index.xml.es
Description: Binary data

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

Sitemap [httpd-2.4] manual

[Luis Gil]

Linkedin:   https://linkd.in/Ljjt8L http://linkd.in/Ljjt8L
Twitter : https://twitter.com/luigy_tspg


sitemap.html.es
Description: Binary data


sitemap.xml.es
Description: Binary data

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

Re: (translation of index.es)

[Luis Gil]

Hi!
wow sincerely thank you for the tip, i will work then better on the trunk
version ;) it will be much better and easier to maintain.
Thx for the Tip.
And one question, i want to commit the changes directly to the svn, i have
sended a mail to the apache svn mail to ask for a svn account, how long
does it take ? im wondering, its juts that i would like to commit directly.
Thanks Lucien


Linkedin:   https://linkd.in/Ljjt8L http://linkd.in/Ljjt8L
Twitter : https://twitter.com/luigy_tspg

On 4 December 2014 at 16:28, Lucien GENTIS lucien.gen...@univ-lorraine.fr
wrote:

  Hello,

 Welcome to you.

 One tip : if you plan to keep on translating httpd doc other next years, I
 recommand you to begin translating trunk branch xml files, then porting
 your translation to 2.4 branch by making a diff between trunk and 2.4 xml
 english files , then reporting differences to your 2.4 file (not so hard
 work because there are still not so much differences between these two
 branches).

 So, when next httpd major version will be released, trunk branch will be
 renamed to 2.6 , and at this moment, you'll have nothing else to do (except
 keep on updating your translations :-) ).

 If you only translate 2.4 branch instead, when next httpd major version
 will be released, you'll have to translate again 2.6 new branch xml files.

 Feel free to ask for information if you need help about your translation
 project management.

 Lucien

 Le 03/12/2014 22:43, Luis Gil a écrit :

  Hi:
 yes, i realized i got misspelled the directory a few minutes before
 sending the screenshot, ;)
 Its from the 2.4 branch
 the full path that is supposed to be is httpd-2.4\manual\faq
 i resend the files with the comments.
 Thax for the answers!!

  Linkedin:   https://linkd.in/Ljjt8L http://linkd.in/Ljjt8L
 Twitter : https://twitter.com/luigy_tspg

 On 3 December 2014 at 22:04, André Malo n...@perlig.de wrote:

 Hi again,

 If you submit files, please specify, which branch they are for (trunk, 2.4
 or 2.2).
 Also, for translations only the xml file is really needed as the rest is
 generated.

 Then your xml file is missing the translation info, like this (picked
 from a
 french file, look, for example in index.xml.fr):

 !-- French translation : Lucien GENTIS --
 !-- Reviewed by : Vincent Deffontaines --
 !-- English Revision : 1524238 --

 The first two lines are optional; the last line however should be there.
 It
 specifies the revision number of the LastChangedRevision line of the
 English file at the time of translating it.
 The build process modifies this line whenever the English original changes
 and that way keeps track of what needs to be changed in the translations.
 The LastChangedRevision line is only needed for the English originals.

 Furthermore, if you can find a reviewer, that would be fine. If not, well,
 nothing we can do about it right now. I think, we loosened the requirement
 some time ago, so when you fix your submission, we can certainly commit
 it.

 Thanks!

 nd
 --
 Solides und umfangreiches Buch
   -- aus einer Rezension

 http://pub.perlig.de/books.html#apache2

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




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


 --
 Lucien GENTIS
 UNIVERSITE DE LORRAINE - ESPE
 Centre de Ressources Informatiques
 5, Rue Paul Richard
 C.O. 3 - MAXEVILLE
 54528 LAXOU-CEDEX

 Tél. 03 83 17 68 42
 Email : lucien.gen...@univ-lorraine.fr

Translation ES es.xml

[Luis Gil]

Hello:
I was working on the Spanish translation of the documentation when I
realised that  the es.xml file is outdated, so my question is, what could
be done to update it?
Thank you.

-- 

Luis J.G

Re: Translation ES es.xml

[Luis Gil]

Hi Luca:
Thank you I will be hands on it.

El mar., 5 de enero de 2016 16:18, Luca Toscano <toscano.l...@gmail.com>
escribió:

> Hello Luis,
>
> I am updating the doc's xmls as well and I noticed a discrepancy between
> the EN documentation and the other locales too. It is really difficult to
> maintain a good documentation in english, keeping multiple languages in
> sync is even harder. My suggestion would be to file a bug in
> https://bz.apache.org/bugzilla/ with a patch attached if you have the
> time to update the Spanish xmls (useful links:
> https://httpd.apache.org/dev/patches.html and
> http://httpd.apache.org/docs-project/docsformat.html).
>
> Thanks!
>
> Luca
>
> 2016-01-04 20:38 GMT-08:00 Luis Gil <ljgbpfeif...@googlemail.com>:
>
>> Hello:
>> I was working on the Spanish translation of the documentation when I
>> realised that  the es.xml file is outdated, so my question is, what could
>> be done to update it?
>> Thank you.
>>
>> --
>>
>> Luis J.G
>>
>
> --

Luis J.G

Re: Translation ES es.xml

[Luis Gil]

Hi CJ:
Thank you for your answer, i will take tht in account.
As soon as i get it working i will open a but report on the bugzilla.
I hope it doesnt take me too long.
Have a nice day.
Luis.

Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
Twitter : https://twitter.com/luigy_tspg

On 6 January 2016 at 07:21, Marion & Christophe JAILLET <
christophe.jail...@wanadoo.fr> wrote:

> Hi Luis,
>
> the best is to open a buzilla (
> https://bz.apache.org/bugzilla/enter_bug.cgi?product=Apache%20httpd-2)
> with the component Documentation. You can then attached there all the
> patches you want
> This is to avoid to loose your proposals in the mail flow.
>
> If you plan to submit many ES documentation updates, the easiest would be
> to provide you a committer access, so that you can modify the files
> yourself.
> Let start with a few proposals via bugzilla.
>
>
> Your changes should first be done against trunk, then backported to 2.4.x
> for the relevant parts. (and to 2.2.x if possible. The latter should be
> close to EOL (no decision taken up to now on when it should happen), so it
> is less important, IMHO, to spend time on it)
>
> Thanks a lot for you interest and contributions,
>
> Best regards,
> CJ
>
>
> Le 06/01/2016 00:19, Luis Gil a écrit :
>
> Hi,
> yes I had read that page, but it doesn't  say  anything about how  the
> locale es.xml for example or others could be updated, as in the first page
> you are refrigerator to says  it's outdated, so I was looking on the Web
> and then, I went straight here to ask, if any one could give a tip or a
> hint on it.
> thanks.
>
>
> El mar., 5 de enero de 2016 19:45, Christophe JAILLET <
> christophe.jail...@wanadoo.fr> escribió:
>
>> Hi,
>>
>> if not already aware of, here is an interesting page when trying to keep
>> in synch a localized version of the doc with the EN version.
>> http://people.apache.org/~takashi/translation-status/test.html#trunk
>> (this page is documented in
>> http://httpd.apache.org/docs-project/translations.html)
>>
>> Best regards,
>> CJ
>>
>> Le 05/01/2016 19:25, Luis Gil a écrit :
>> >
>> > Hi Luca:
>> > Thank you I will be hands on it.
>> >
>> >
>> > El mar., 5 de enero de 2016 16:18, Luca Toscano
>> > <toscano.l...@gmail.com <mailto:toscano.l...@gmail.com>> escribió:
>> >
>> > Hello Luis,
>> >
>> > I am updating the doc's xmls as well and I noticed a discrepancy
>> > between the EN documentation and the other locales too. It is
>> > really difficult to maintain a good documentation in english,
>> > keeping multiple languages in sync is even harder. My suggestion
>> > would be to file a bug in <https://bz.apache.org/bugzilla/>
>> https://bz.apache.org/bugzilla/ with a
>> > patch attached if you have the time to update the Spanish xmls
>> > (useful links: https://httpd.apache.org/dev/patches.html and
>> > http://httpd.apache.org/docs-project/docsformat.html).
>> >
>> > Thanks!
>> >
>> > Luca
>> >
>> > 2016-01-04 20:38 GMT-08:00 Luis Gil < <ljgbpfeif...@googlemail.com>
>> ljgbpfeif...@googlemail.com
>> > <mailto:ljgbpfeif...@googlemail.com>>:
>> >
>> > Hello:
>> > I was working on the Spanish translation of the documentation
>> > when I realised that  the es.xml file is outdated, so my
>> > question is, what could be done to update it?
>> > Thank you.
>> >
>> > --
>> >
>> > Luis J.G
>> >
>> >
>> > --
>> >
>> > Luis J.G
>> >
>>
>>
>>
>> -
>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>
>> --
>
> Luis J.G
>
>
>

Re: Translation ES es.xml

[Luis Gil]

Hi,
yes I had read that page, but it doesn't  say  anything about how  the
locale es.xml for example or others could be updated, as in the first page
you are refrigerator to says  it's outdated, so I was looking on the Web
and then, I went straight here to ask, if any one could give a tip or a
hint on it.
thanks.


El mar., 5 de enero de 2016 19:45, Christophe JAILLET <
christophe.jail...@wanadoo.fr> escribió:

> Hi,
>
> if not already aware of, here is an interesting page when trying to keep
> in synch a localized version of the doc with the EN version.
> http://people.apache.org/~takashi/translation-status/test.html#trunk
> (this page is documented in
> http://httpd.apache.org/docs-project/translations.html)
>
> Best regards,
> CJ
>
> Le 05/01/2016 19:25, Luis Gil a écrit :
> >
> > Hi Luca:
> > Thank you I will be hands on it.
> >
> >
> > El mar., 5 de enero de 2016 16:18, Luca Toscano
> > <toscano.l...@gmail.com <mailto:toscano.l...@gmail.com>> escribió:
> >
> > Hello Luis,
> >
> > I am updating the doc's xmls as well and I noticed a discrepancy
> > between the EN documentation and the other locales too. It is
> > really difficult to maintain a good documentation in english,
> > keeping multiple languages in sync is even harder. My suggestion
> > would be to file a bug in https://bz.apache.org/bugzilla/ with a
> > patch attached if you have the time to update the Spanish xmls
> > (useful links: https://httpd.apache.org/dev/patches.html and
> > http://httpd.apache.org/docs-project/docsformat.html).
> >
> > Thanks!
> >
> > Luca
> >
> > 2016-01-04 20:38 GMT-08:00 Luis Gil <ljgbpfeif...@googlemail.com
> > <mailto:ljgbpfeif...@googlemail.com>>:
> >
> > Hello:
> > I was working on the Spanish translation of the documentation
> > when I realised that  the es.xml file is outdated, so my
> > question is, what could be done to update it?
> > Thank you.
> >
> > --
> >
> > Luis J.G
> >
> >
> > --
> >
> > Luis J.G
> >
>
>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
> --

Luis J.G

Re: es_update

[Luis Gil]

Oh F. .. I realice that I attached the wrong files sorry I Will send them
now

El dom., 10 de enero de 2016 7:01, Marion & Christophe JAILLET <
christophe.jail...@wanadoo.fr> escribió:

> Also please only attach the modified files, not the auto-generated ones.
>
> Thanks.
>
>
> CJ
>
>
> Le 10/01/2016 03:50, Luca Toscano a écrit :
>
> Hi Luis,
>
> the best way to track this change in my opinion is to open a bug using
> https://bz.apache.org/bugzilla/ (File a bug => Apache httpd2 =>
> Documentation).
>
> Thanks!
>
> Luca
>
> 2016-01-09 9:54 GMT-08:00 Luis Gil <ljgbpfeif...@googlemail.com>:
>
>> Hello:
>> I attached the svn diff named as 9-1-2016ES, i attach too the files i
>> have modified on the trunk repo of the documentation.
>> Regards
>> Luis.
>> Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
>> Twitter : https://twitter.com/luigy_tspg
>>
>>
>> -
>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>
>
>
> --

Luis J.G

Re: es_update

[Luis Gil]

Hello again:
I have checked the files i had send before, i guess Google takes out the
".es" at the end... :( but i have attached them again just in case.
Greetings.


Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
Twitter : https://twitter.com/luigy_tspg

On 12 January 2016 at 17:10, Luis Gil <ljgbpfeif...@googlemail.com> wrote:

> Oh F. .. I realice that I attached the wrong files sorry I Will send them
> now
>
>
> El dom., 10 de enero de 2016 7:01, Marion & Christophe JAILLET <
> christophe.jail...@wanadoo.fr> escribió:
>
>> Also please only attach the modified files, not the auto-generated ones.
>>
>> Thanks.
>>
>>
>> CJ
>>
>>
>> Le 10/01/2016 03:50, Luca Toscano a écrit :
>>
>> Hi Luis,
>>
>> the best way to track this change in my opinion is to open a bug using
>> https://bz.apache.org/bugzilla/ (File a bug => Apache httpd2 =>
>> Documentation).
>>
>> Thanks!
>>
>> Luca
>>
>> 2016-01-09 9:54 GMT-08:00 Luis Gil <ljgbpfeif...@googlemail.com>:
>>
>>> Hello:
>>> I attached the svn diff named as 9-1-2016ES, i attach too the files i
>>> have modified on the trunk repo of the documentation.
>>> Regards
>>> Luis.
>>> Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
>>> Twitter : https://twitter.com/luigy_tspg
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>>
>>
>>
>> --
>
> Luis J.G
>


index.xml.es
Description: application/ecmascript


custom-error.xml.es
Description: application/ecmascript

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

Re: Accents

[Luis Gil]

​Hi again:
So im assuming, we are on the correct path, i mean we can use UTF-8 to
translate the documentation, (because its on the own translator task to do
so) and would be no problem dealing with accents, OK, my question is solved
for now. thank you team!
Regards.
​

On 15 January 2016 at 16:14, Tom Fredrik Blenning Klaussen 
wrote:

>
>
> On 15/01/16 14:19, André Malo wrote:
> > * Lucien Gentis wrote:
> >
> >> This bug was about error messages returned by httpd. (docs/error
> directory)
> >>
> >> But here, we talk about manual pages of httpd documentation in
> >> docs/manual directory ? (as far as I understand)
> >> And I confirm that HTML entities are not necessary for accented
> >> characters display.
> >>
> >> Perhaps It creates other technical problems that we can't see as
> >> committers ?
> >
> > It does not *solve* any problems. I think, we've (more or less) decided
> to
> > leave it to the individual translator's groups how they want to enter it.
>
> I remembered incorrectly, seems most of the discussion ended up here:
> http://www.gossamer-threads.com/lists/apache/docs/447798
>
> Anyway, there is a script attached to the issue which does the actual
> work, and can be applied generally. Not saying it's perfect, by far, if
> someone knows a better solution, please tell me.
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
>

Re: Accents

[Luis Gil]

​
​I will answer your questions as follow:​


On 15 January 2016 at 10:44, Lucien Gentis <lucien.gen...@univ-lorraine.fr>
wrote:

> Hello Luis,
>
> I am Lucien Gentis, working on french translation project.
>
> fr.xml file headers are the same as those of es.xml
>
> I noticed that if we edit xml files in UTF8 encoding, we don't need to use
> HTML entities ; accented characters can be written directly, and they are
> displayed in HTML files with encoding specified in lang file header (for
> example ISO-8859-1 for es.xml, UTF-8 for ja.xml, EUC-KR for ko.xml).
>
> Points to verify :
>
> --- What character encoding do you use in your text editor and what text
> editor do you use ?
> For me : vim-gtk, UTF8 encoding
>
​Im Using UTF-8 in my system and Text editor.​


> --- What charset did you specified in your es.xml when you changed it ?
>
​I changed to UTF-8​


> --- You say "i have tried  yesterday to change the charset of the
> /style/lang/es.xml to see  if it generates the html" : what html file do
> you mean ?
>
​The both fils i had submitted to the doc mail list, the index.html.es and
the custom-error.html.es, but i have noticed that i have to first update
the style in es​


> --- When you display generated HTML file (a httpd doc manual page, I
> suppose), what browser do you use, and what character encoding does it
> detect ?
>
​Im using Firefox (Iceweasel for be more precise)​

​​
For me : Firefox or IE : character encoding specified in lang file
header is automatically detected.

Lucien

Le 15/01/2016 06:42, Luis Gil a écrit :

Hello:
I was wondering, how could we work with the accents and not with the html
code of them, i have tried  yesterday to change the charset of the
/style/lang/es.xml to see  if it generates the html, it does but at the
time to open the html file in the browser, it gives me the autogenerated
code and no html page like it should be, so i changed it back to what it
was at the beginning, but still the same issue.
I would appreciate any light in this that i´m getting confused.
Thank you in advance.

Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
Twitter : https://twitter.com/luigy_tspg


-- 
> Lucien GENTIS
> UNIVERSITE DE LORRAINE - ESPE
> Centre de Ressources Informatiques
> 5, Rue Paul Richard
> C.O. 3 - MAXEVILLE
> 54528 LAXOU-CEDEX
>
> Tél. 03 72 74 22 45
> Email : lucien.gen...@univ-lorraine.fr
>
>

Re: Accents

[Luis Gil]

Yes i got at the same point here, sorry for not answering early, thats why
i left the ISO-8859-1 of the files i have submitted.
thanks for the TIP.


Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 17 January 2016 at 18:49, Lucien Gentis 
wrote:

> Hi,
>
> In fact, what I said earlier is false.
>
> If we use UTF-8 for XML files edition, HTML entities are mandatory for
> accented characters.
> (or some files have to be modified like es.xml or manual.es.xsl mentionned
> below; I tried to do so with fr files, but it doesn't work).
>
> The only way I found to avoid HTML entities is to edit XML files in latin1
> (ISO-8859-1) encoding.
>
>
> Le 16/01/2016 08:04, Christophe JAILLET a écrit :
>
>> Hi,
>>
>> could someone clarify, when building the doc what is controlled by the
>> different following charset:
>> in es.xml:
>> ISO-8859-1
>>
>> in manual.es.xsl
>> > ISO-8859-1
>>
>>
>> The 2 latter control the output of the generated documents (encoding of
>> the file written (on the first line of the file) and html meta tag)
>> But where and how is used the charset defined in es.xml?
>>
>>
>> Thanks in advance.
>>
>> CJ
>>
>> -
>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
>

Accents

[Luis Gil]

Hello:
I was wondering, how could we work with the accents and not with the html
code of them, i have tried  yesterday to change the charset of the
/style/lang/es.xml to see  if it generates the html, it does but at the
time to open the html file in the browser, it gives me the autogenerated
code and no html page like it should be, so i changed it back to what it
was at the beginning, but still the same issue.
I would appreciate any light in this that i´m getting confused.
Thank you in advance.

Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

ES Translation. [ping]

[Luis Gil]

Hello people:
Recently I have submitted some updates to the mailing list of the es
translation, I got no commit access
​
at the moment
​.
Here are the updates/translations done:

Install page update:
https://bz.apache.org/bugzilla/show_bug.cgi?id=58887
Custom error update:
https://bz.apache.org/bugzilla/show_bug.cgi?id=58945
New_feature 2.4 update:
https://bz.apache.org/bugzilla/show_bug.cgi?id=58894
Sitemap update:
https://bz.apache.org/bugzilla/show_bug.cgi?id=58907

any improvements that could be done tell me.
Sincerely.
Luis

Re: ES Translation. [ping]

[Luis Gil]

Thank you, now its time for the reviewers. ;)
I will keep on translating.
And thank you for the feedback Lucien.


Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
Twitter : https://twitter.com/luigy_tspg

On 4 February 2016 at 17:28, Lucien Gentis <lucien.gen...@univ-lorraine.fr>
wrote:

> English Revision headers are correct yet.
>
> But your files had to be reviewed by another spanish speaker before being
> submitted to the list .
>
> For example, in the french translation team, most of the time, I translate
> the files, Vincent Deffontaines reviews them, and then commits them to
> Apache repository with the 2 headers "Translated by" and "Reviewed by"
>
> Committers at @httpd.apache.org can so better trust your translation if
> it has been reviewed.
>
>
> Le 04/02/2016 17:09, Luis Gil a écrit :
>
> Hello Lucien:
> as far as i can read on the page, and what i have understood, is that "
> Each* commit message* should list the reviewer. If the translator is not
> the same as the committer, the translator should also be named in the *commit
> messag*e." i know i'm not committing, so i can't do so, because i have no
> commit permission, so i can't mention the reviewer; unless you refer to the
> comment above the file.
>
> On the other hand, i will review the English Revision comment on the files.
> Greetings.
> Luis.
>
> Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
> Twitter : https://twitter.com/luigy_tspg
>
> On 4 February 2016 at 16:37, Lucien Gentis <lucien.gen...@univ-lorraine.fr
> > wrote:
>
>> Hi Luis,
>>
>> As far as I know, new documents have to be reviewed by another spanish
>> speaker, and reviewer must be mentionned at the top of the file. (see
>> "Review Standards" here :
>> <https://httpd.apache.org/docs-project/translations.html>
>> https://httpd.apache.org/docs-project/translations.html)
>>
>> Additionnally, as I earlier said, your "English Revision" header is
>> missing or is not correct ; here is an example :
>>
>> 
>>
>> (replacing the number by english revision number corresponding to your
>> translated file)
>>
>> No extra character must be present, and I'm not sure, but I think it's
>> case sensitive.
>>
>> "LastChangedRevision" header has no effect here, it's for english version
>> of the file.
>>
>> Lucien
>>
>>
>> Le 04/02/2016 15:44, Luis Gil a écrit :
>>
>> Hello people:
>> Recently I have submitted some updates to the mailing list of the es
>> translation, I got no commit access
>> ​
>> at the moment
>> ​ .
>> Here are the updates/translations done:
>>
>> Install page update:
>> <https://bz.apache.org/bugzilla/show_bug.cgi?id=58887>
>> https://bz.apache.org/bugzilla/show_bug.cgi?id=58887
>> Custom error update:
>> <https://bz.apache.org/bugzilla/show_bug.cgi?id=58945>
>> https://bz.apache.org/bugzilla/show_bug.cgi?id=58945
>> New_feature 2.4 update:
>> <https://bz.apache.org/bugzilla/show_bug.cgi?id=58894>
>> https://bz.apache.org/bugzilla/show_bug.cgi?id=58894
>> Sitemap update:
>> <https://bz.apache.org/bugzilla/show_bug.cgi?id=58907>
>> https://bz.apache.org/bugzilla/show_bug.cgi?id=58907
>>
>> any improvements that could be done tell me.
>> Sincerely.
>> Luis
>>
>>
>> --
>> Lucien GENTIS
>> UNIVERSITE DE LORRAINE - ESPE
>> Centre de Ressources Informatiques
>> 5, Rue Paul Richard
>> C.O. 3 - MAXEVILLE
>> 54528 LAXOU-CEDEX
>>
>> Tél. 03 72 74 13 28
>> Email : lucien.gen...@univ-lorraine.fr
>>
>>
>
> --
> Lucien GENTIS
> UNIVERSITE DE LORRAINE - ESPE
> Centre de Ressources Informatiques
> 5, Rue Paul Richard
> C.O. 3 - MAXEVILLE
> 54528 LAXOU-CEDEX
>
> Tél. 03 72 74 13 28
> Email : lucien.gen...@univ-lorraine.fr
>
>

Re: ES Translation. [ping]

[Luis Gil]

Hello Lucien:
as far as i can read on the page, and what i have understood, is that "Each*
commit message* should list the reviewer. If the translator is not the same
as the committer, the translator should also be named in the *commit messag*
e." i know i'm not committing, so i can't do so, because i have no commit
permission, so i can't mention the reviewer; unless you refer to the
comment above the file.

On the other hand, i will review the English Revision comment on the files.
Greetings.
Luis.

Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
Twitter : https://twitter.com/luigy_tspg

On 4 February 2016 at 16:37, Lucien Gentis <lucien.gen...@univ-lorraine.fr>
wrote:

> Hi Luis,
>
> As far as I know, new documents have to be reviewed by another spanish
> speaker, and reviewer must be mentionned at the top of the file. (see
> "Review Standards" here :
> https://httpd.apache.org/docs-project/translations.html)
>
> Additionnally, as I earlier said, your "English Revision" header is
> missing or is not correct ; here is an example :
>
> 
>
> (replacing the number by english revision number corresponding to your
> translated file)
>
> No extra character must be present, and I'm not sure, but I think it's
> case sensitive.
>
> "LastChangedRevision" header has no effect here, it's for english version
> of the file.
>
> Lucien
>
>
> Le 04/02/2016 15:44, Luis Gil a écrit :
>
> Hello people:
> Recently I have submitted some updates to the mailing list of the es
> translation, I got no commit access
> ​
> at the moment
> ​ .
> Here are the updates/translations done:
>
> Install page update:
> <https://bz.apache.org/bugzilla/show_bug.cgi?id=58887>
> https://bz.apache.org/bugzilla/show_bug.cgi?id=58887
> Custom error update:
> <https://bz.apache.org/bugzilla/show_bug.cgi?id=58945>
> https://bz.apache.org/bugzilla/show_bug.cgi?id=58945
> New_feature 2.4 update:
> <https://bz.apache.org/bugzilla/show_bug.cgi?id=58894>
> https://bz.apache.org/bugzilla/show_bug.cgi?id=58894
> Sitemap update:
> <https://bz.apache.org/bugzilla/show_bug.cgi?id=58907>
> https://bz.apache.org/bugzilla/show_bug.cgi?id=58907
>
> any improvements that could be done tell me.
> Sincerely.
> Luis
>
>
> --
> Lucien GENTIS
> UNIVERSITE DE LORRAINE - ESPE
> Centre de Ressources Informatiques
> 5, Rue Paul Richard
> C.O. 3 - MAXEVILLE
> 54528 LAXOU-CEDEX
>
> Tél. 03 72 74 13 28
> Email : lucien.gen...@univ-lorraine.fr
>
>

Re: Pre-retirement banner on all the 2.2.x documentation pages

[Luis Gil]

I see  that is a good point for the 2. 2 Docs.

El mar., 23 de febrero de 2016 11:05, Luca Toscano 
escribió:

> Hi Apache doc writers,
>
> I discussed in dev@ an idea to put the following banner on each
> documentation page of the 2.2 branch:
>
> 
> Please note
> This document refers to the 2.2 version of Apache httpd that is still
> maintained but not actively developed. Please upgrade to the current
> version of Apache httpd to get performance improvements and new features.
> The migration of the configuration files will require a bit of effort but
> it will be definitely worth it in terms of performance and long term
> maintainability.
>
> Upgrading to the current version of Apache httpd (link to
> http://httpd.apache.org/docs/current/upgrading.html)
>
> You may follow this link to go to the current version of this document.
> 
>
> The goal would be to inform and remember to 2.2 users that the migration
> to 2.4 is strongly suggested. I attached a patch to this email to give you
> an idea of what I have in mind.
>
> Main things to discuss since this is a big change:
>
> 1) Is the wording ok? Do we need a different banner?
> 2) I reused the "retirement" scheme that was present since 2.0 to avoid
> code repetition, but let me know if you want me to duplicate it.
> 3) I added the english banner to all the lang.* files, not sure if we need
> translations before proceeding.
>
> Let me know your thoughts and ideas :)
>
> Thanks!
>
> Luca
>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org

-- 

Luis J.G

Re: Accents

[Luis Gil]

Update:
keeping the ISO-8859-1 ( in the  tag) and the UTF-8 in the top of
the encoding of the XML(as shoun in the img attached),  we don't need the
HTML encoding, i have been working on some traslation from now and works
fine.
As you can see in the mailing list i have upload the files to the bugzilla
site (aded as patch).
Regards.
[image: Inline images 2]
Luis.

Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 18 January 2016 at 13:32, André Malo  wrote:

> * Lucien Gentis wrote:
>
> > I only wanted to know if there was a way to enter accented characters in
> > xml source files without having to replace them by their equivalent HTML
> > entities in order they display correctly in html generated files.
>
> Yes, that's certainly possible.
>
> > I checked that with bind.xml.fr in my local svn source tree, but it
> > didn't work, but what you say above point at the header of the xml
> > source files :
> > The one of bind.xml.fr is ,
> > and my text editor encoding is UTF-8.
> > Here is perhaps the solution.
> >
> > I'll try to modify this header when I'll be at home . . .
>
> Lots of editors should have some way to autodetect the encoding from the
> file
> itself. Maybe there's some option in yours, too.
>
> Cheers,
> nd
> --
> my @japh = (sub{q~Just~},sub{q~Another~},sub{q~Perl~},sub{q~Hacker~});
> my $japh = q[sub japh { }]; print join   #
>  [ $japh =~ /{(.)}/] -> [0] => map $_ -> ()  #André Malo #
> => @japh;# http://pub.perlig.de/ #
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
>

ES translation

[Luis Gil]

Hello everyone:
i'm still translating the Documentation into spanish and updating  those of
ES that were translated before, i have added 4 patches to the bugzilla,
here are the links to it.

https://bz.apache.org/bugzilla/show_bug.cgi?id=58887
https://bz.apache.org/bugzilla/show_bug.cgi?id=58907
https://bz.apache.org/bugzilla/show_bug.cgi?id=58875
https://bz.apache.org/bugzilla/show_bug.cgi?id=58894

If any one can review them, i would be glad answering any questions about
it; i have checked building them and, works good!
My Regards and have a nice weekend.

Re: Accents

[Luis Gil]

Hello Lucien & doc-list:
Yes having a nice weekend than you.
Yes you are right as far as i am concerned with the parameters set as the
image attached on my las email, the encoding runs perfect, and as you say,
that's the way it will work for all latin characters as far as i know.

So, shouldn't we add this to the HOW-to contribute translating Apache
documentation page? It will be useful for future contributors i guess.
Have a nice weekend all.
Luis


Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 23 January 2016 at 18:13, Lucien Gentis 
wrote:

> Hello Luis and all at doc@apache,
>
> Hope you have a good weekend !
>
> I finally found a solution to get rid of these HTML entities :
>
>
> All xml files (for example env.xml.fr) must have same effective encoding
> as their first line indicate (for example  encoding="UTF-8" ?>).
>
> This could appear as evident, but for me, it was not the case.
>
> Additionally, as André Malo said,  field in lang files
> (es.xml,...) controls output encoding of HTML files (env.html.fr,...) via
> "bootstrap"option of the build command.
>
>
> For summary, here are the parameters to get rid of HTML entities :
>
> --- If XML file encoding is UTF-8 , its header must be :  version="1.0" encoding="UTF-8" ?>
> --- If you want rewrite your lang file (fr.xml,...) without HTML entities
> and if its encoding is UTF-8, its header must be :  encoding="UTF-8" ?>
>
>
> Finally, output HTML files encoding is controlled by manual.fr.xsl, itself
> controlled by  field of fr.xml : If  field of fr.xml
> contains "UTF-8", manual.fr.xsl will also contain "UTF-8" in its "output
> method" field and its variable "output-encoding", and output HTML files
> encoding will be UTF-8.
>
> Regards
>
> Lucien
>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
>

Re: Thoughts on using HW for httpd?

[Luis Gil]

love it!

El vie., 12 de febrero de 2016 13:20, Daniel Gruno 
escribió:

> Hi folks,
> as some may know, ComDev is trialling a new thing called 'Help Wanted!'
> at https://helpwanted.apache.org/
>
> I've added a few example entries for httpd, and I'm wondering if this is
> something we would want to plug into our web site?
>
> You can see an example web site widget at
> https://helpwanted.apache.org/wtest.html (top one shows httpd)
>
> It's an easy way to identify which tasks we'd love to see someone get
> started on (and has the benefit of being able to assign difficulty
> levels, skills needed etc to a task), and judging from the input on the
> existing tasks, it seems to attract people towards projects.
>
> Thoughts? flames? snark? :)
>
> With regards,
> Daniel.
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
> --

Luis J.G

Any one doing it?

[Luis Gil]

Hello again:
I saw the STATUS file to see if i could dive on any of the points, so i
came a cross on this:
*To Do List*
*===*

*- Update the http://httpd.apache.org/docs-project/docsformat.html
*
*  document to be useful. In particular:*
*Here i came across of something, could i get all the info related to the
links and make it all in the docformat.html?*

   * - Document the translation process.*
*If no one is on this, i can make a draft of it with all the things i had
learned till now.*
*- Generally update it to make it reflect the current reality of how*
*  we work.*
*BTW, why
the http://people.apache.org/~takashi/translation-status/test.html#trunk
 has
been deleted? in my opinion was a nice way for new people that joins the
documentation, as good as looking the BZ page.*
  *  -  Improving the documentation of the documentations' build system*
*   itself (requirements, procedures)*
*I guess this last point its better to create a new page and separate if
from the current page docsformat.html itself i guess.*

Any suggestions or comments will be welcome as well as any ideas on how to
do it, so i can have all the ideas and put them together.

Regards.
Luis.

-- 

Luis J.G

Updated ES Translation to actual head.

[Luis Gil]

Hello:
I have translated and arranged in alphabetically order the file
glossary.xml.es
It has been reviewed as the same as the other files, i am attaching here
all the files.
Now are updated and reviewed.

Have a nice Easter.
Luis.


-- 

Luis J.G


custom-error.xml.es
Description: Binary data


index.xml.es
Description: Binary data


bind.xml.es
Description: Binary data


glossary.xml.es
Description: Binary data


install.xml.es
Description: Binary data


sitemap.xml.es
Description: Binary data


new_features_2_4.xml.es
Description: Binary data

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

Re: Any one doing it?

[Luis Gil]

Hello Lucien:
Here is the link to the File, i know its not inside the manual page,
http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/STATUS?view=markup
 cheers.


Eric, then personal webpages are going to be available soon?
Thank you.


On Thu, 24 Mar 2016 at 13:59 Eric Covener <cove...@gmail.com> wrote:

> On Thu, Mar 24, 2016 at 6:09 AM, Luis Gil <ljgbpfeif...@googlemail.com>
> wrote:
> > BTW, why the
> > http://people.apache.org/~takashi/translation-status/test.html#trunk has
> > been deleted? in my opinion was a nice way for new people that joins the
> > documentation, as good as looking the BZ page.
> > -  Improving the documentation of the documentations' build system
> >itself (requirements, procedures)
> > I guess this last point its better to create a new page and separate if
> from
> > the current page docsformat.html itself i guess.
>
>
> Personal websites need to be migrated by their owners after an infra
> change somewhat recently.
>
> --
> Eric Covener
> cove...@gmail.com
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
> --

Luis J.G

Re: translating English to Japanese

[Luis Gil]

Hello Kimtea and Welcome!

El sáb., 5 de marzo de 2016 9:08, Kazuki Aranami 
escribió:

> Hi
>
> My name is "Kazuki Aranami". Nickname is "kimtea".
> This time, the English document of the Apache HTTP Server,
> we want to translate into Japanese.
>
> I, you have experience with translating English to Japanese.
> Environment is Windows 10 Pro Insider Preview Build 14279
>  (64-bit).
>
> Stable environment of Windows 10 is currently in preparation.
>
>
> I am planning to use the Transifex (www.transifex.com).
> If the OSS, Can you provide the service for free.
> I, on the use of this site, please tell me if you have any problems.
>
> In addition, we are looking for people that will cooperate with
> Japanese localization. Document to perform the translation is
> the Apache HTTP server version 2.4 and the Apache HTTP
> Server vulnerabilities 2.4.
>
> Detailed technical documents will also continue to translation.
>
> Thank you.
>
> ---
>   Kazuki Aranami
>
>   Twitter: http://twitter.com/kimtea
> ---
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
> --

Luis J.G

Re: Any one doing it?

[Luis Gil]

Hello all:
I am modifying the docsformat.mdtext and I have added several things, but
before sending it to the @docs list, I would like to solve some questions
that I´ve got about it:

   1. In the actual transformation section, its says about the SVN 2.2.x
   docs, does that svn is the same as the trunk branch?
   2. It says there that you can get Java from SUN... I had added a link to
   the Oracle page
   http://www.oracle.com/technetwork/java/javase/downloads/index.html would
   that be good?
   3. I have tried to build the pages in local, to see the final result,
but the Perl script keep failing,  any hints

Best regards.
Luis

Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
Twitter : https://twitter.com/luigy_tspg

On 30 March 2016 at 11:50, Luis Gil <ljgbpfeif...@googlemail.com> wrote:

> Good to hear that.
> Thank you Takashi.
>
> Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
> Twitter : https://twitter.com/luigy_tspg
>
> On 30 March 2016 at 11:39, Takashi Sato <taka...@tks.st> wrote:
>
>> Infra said
>>
>> > The new host, home.apache.org, will ONLY be for web space, you will not
>> > have shell access to the machine (but you can copy data to it using SFTP
>> > and your SSH key).
>>
>> so the cron job can not run on home.apache.org.
>>
>> I am trying to set up my server that updates status jsons and send
>> them to home.a.o.
>>
>> There is still a problem that http://home.apache.org/~takashi/ is my
>> personal web site
>> and is not the project's official page.
>>
>> -
>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>
>>
>

Re: Any one doing it?

[Luis Gil]

On 1 April 2016 at 17:50, Yann Ylavic <ylavic@gmail.com> wrote:

> On Fri, Apr 1, 2016 at 5:27 PM, Luis Gil <ljgbpfeif...@googlemail.com>
> wrote:
> >
> > In the actual transformation section, its says about the SVN 2.2.x docs,
> > does that svn is the same as the trunk branch?
>
> No, there is a docs/ directory for every branch (trunk, 2.4, 2.x,
> ...)
>
> The section says:
> "Assuming you already have
> [httpd/httpd/branches/2.2.x/docs/](
> http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/docs/)
> (or the equivalent from another branch) checked out from SVN, ..."
>
> So I would simply s/2.2/2.4/ to update the "recommended" version, but
> the possibility to use another branch is already mentioned.
>

​So better put 2.2/2.4? or just the 2.4 since 2.2 its not maintained? ​


>
> > It says there that you can get Java from SUN... I had added a link to the
> > Oracle page
> > http://www.oracle.com/technetwork/java/javase/downloads/index.html would
> > that be good?
>
> Maybe just s/SUN/Oracle/ would be enough, links die.
>

cool ​


>
> No idea for last point (perl failures)..
>
> Regards,
> Yann.
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
> ​Thank you for the feedback
Luis​

Re: Any one doing it?

[Luis Gil]

On Mon, 4 Apr 2016 at 11:33 Luis Gil <ljgbpfeif...@googlemail.com> wrote:

> Ok... OH god i press too much the S key =O
>
> On Mon, 4 Apr 2016 at 11:19 Lucien Gentis <lucien.gen...@univ-lorraine.fr>
> wrote:
>
>>
>>
>> Le 04/04/2016 10:51, Luis Gil a écrit :
>>
>> Is that a like or dislike ;)
>>
>> El lun., 4 de abril de 2016 9:03, Lucien Gentis <
>> lucien.gen...@univ-lorraine.fr> escribió:
>>
>>>
>>>
>>> Le 01/04/2016 20:04, Luis Gil a écrit :
>>>
>>>
>>>
>>> Linkedin:<http://linkd.in/Ljjt8L>https://linkd.in/Ljjt8L
>>> Twitter : https://twitter.com/luigy_tspg
>>>
>>> On 1 April 2016 at 18:49, Yann Ylavic < <ylavic@gmail.com>
>>> ylavic@gmail.com> wrote:
>>>
>>>> On Fri, Apr 1, 2016 at 6:36 PM, Luca Toscano < <toscano.l...@gmail.com>
>>>> toscano.l...@gmail.com> wrote:
>>>> >
>>>> > +1, let's concentrate on 2.4 :)
>>>>
>>>> You know, there is still many 2.2 around, and some people may have
>>>> backported 2.4 fixes to 2.2 and decide to propose them some days.
>>>> If three PMC members (at least) think a 2.2.32 is worth it, it may
>>>> well be out ;)
>>>>
>>>> But I agree that we should mainly reference 2.4 in the "generic" docs.
>>>>
>>>> Regards,
>>>> Yann.
>>>>
>>>> -
>>>> To unsubscribe, e-mail: <docs-unsubscr...@httpd.apache.org>
>>>> docs-unsubscr...@httpd.apache.org
>>>> For additional commands, e-mail: <docs-h...@httpd.apache.org>
>>>> docs-h...@httpd.apache.org
>>>>
>>>>
>>> Hello:
>>> Check this draft i have made of the docsformat page and tell me how you
>>> see it.
>>>
>>> i attach ass well a diff file so it can be easy to view the changes.
>>> ​
>>>
>>> =-O
>>>
>> Just reread your last sentence :-)
>>
>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>>
>>>
>>> --
>>> Lucien GENTIS
>>> UNIVERSITE DE LORRAINE - ESPE
>>> Centre de Ressources Informatiques
>>> 5, Rue Paul Richard
>>> C.O. 3 - MAXEVILLE
>>> 54528 LAXOU-CEDEX
>>>
>>> Tél. 03 72 74 13 28
>>> Email : lucien.gen...@univ-lorraine.fr
>>>
>>> --
>>
>> Luis J.G
>>
>>
>> --
>> Lucien GENTIS
>> UNIVERSITE DE LORRAINE - ESPE
>> Centre de Ressources Informatiques
>> 5, Rue Paul Richard
>> C.O. 3 - MAXEVILLE
>> 54528 LAXOU-CEDEX
>>
>> Tél. 03 72 74 13 28
>> Email : lucien.gen...@univ-lorraine.fr
>>
>> --
>
> Luis J.G
>


By the way i have made a small change on the page, give it a review.
Regards
Luis
-- 

Luis J.G


docsformat.mdtext
Description: Binary data

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

Re: Any one doing it?

[Luis Gil]

Ok... OH god i press too much the S key =O

On Mon, 4 Apr 2016 at 11:19 Lucien Gentis <lucien.gen...@univ-lorraine.fr>
wrote:

>
>
> Le 04/04/2016 10:51, Luis Gil a écrit :
>
> Is that a like or dislike ;)
>
> El lun., 4 de abril de 2016 9:03, Lucien Gentis <
> lucien.gen...@univ-lorraine.fr> escribió:
>
>>
>>
>> Le 01/04/2016 20:04, Luis Gil a écrit :
>>
>>
>>
>> Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
>> Twitter : https://twitter.com/luigy_tspg
>>
>> On 1 April 2016 at 18:49, Yann Ylavic <ylavic@gmail.com> wrote:
>>
>>> On Fri, Apr 1, 2016 at 6:36 PM, Luca Toscano <toscano.l...@gmail.com>
>>> wrote:
>>> >
>>> > +1, let's concentrate on 2.4 :)
>>>
>>> You know, there is still many 2.2 around, and some people may have
>>> backported 2.4 fixes to 2.2 and decide to propose them some days.
>>> If three PMC members (at least) think a 2.2.32 is worth it, it may
>>> well be out ;)
>>>
>>> But I agree that we should mainly reference 2.4 in the "generic" docs.
>>>
>>> Regards,
>>> Yann.
>>>
>>> -
>>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>>
>>>
>> Hello:
>> Check this draft i have made of the docsformat page and tell me how you
>> see it.
>>
>> i attach ass well a diff file so it can be easy to view the changes.
>> ​
>>
>> =-O
>>
> Just reread your last sentence :-)
>
>
>>
>>
>> -
>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>
>>
>> --
>> Lucien GENTIS
>> UNIVERSITE DE LORRAINE - ESPE
>> Centre de Ressources Informatiques
>> 5, Rue Paul Richard
>> C.O. 3 - MAXEVILLE
>> 54528 LAXOU-CEDEX
>>
>> Tél. 03 72 74 13 28
>> Email : lucien.gen...@univ-lorraine.fr
>>
>> --
>
> Luis J.G
>
>
> --
> Lucien GENTIS
> UNIVERSITE DE LORRAINE - ESPE
> Centre de Ressources Informatiques
> 5, Rue Paul Richard
> C.O. 3 - MAXEVILLE
> 54528 LAXOU-CEDEX
>
> Tél. 03 72 74 13 28
> Email : lucien.gen...@univ-lorraine.fr
>
> --

Luis J.G

Re: update r1737084

[Luis Gil]

Thank you.

i will close now the bugzilla report.

All looks fine.


Have a nice day @docs

Luis .

El mié., 30 de marzo de 2016 13:13, Yann Ylavic <ylavic@gmail.com>
escribió:

> On Wed, Mar 30, 2016 at 11:44 AM, Luis Gil <ljgbpfeif...@googlemail.com>
> wrote:
> > Hello Yann:
> >
> > Can you as a commiter, check for the spanish html documents and review
> the
> > bugzilla so we can close the issues?:
> >
> > https://bz.apache.org/bugzilla/show_bug.cgi?id=58969
> > the xml file is in the repo, but not the html one :( (a build is
> required )
> > bind.html.es
> >
> > and the new_features_2_4.html file in html format is not in the repo :/
> > could you check it please.
>
> Done in r1737096, thanks for the follow up.
> Browsing https://httpd.apache.org/docs/trunk/es/ now shows the new files.
> Please close the bugzilla report if it works for you.
>
> Regards,
> Yann.
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
> --

Luis J.G

Re: Any one doing it?

[Luis Gil]

Good to hear that.
Thank you Takashi.

Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 30 March 2016 at 11:39, Takashi Sato  wrote:

> Infra said
>
> > The new host, home.apache.org, will ONLY be for web space, you will not
> > have shell access to the machine (but you can copy data to it using SFTP
> > and your SSH key).
>
> so the cron job can not run on home.apache.org.
>
> I am trying to set up my server that updates status jsons and send
> them to home.a.o.
>
> There is still a problem that http://home.apache.org/~takashi/ is my
> personal web site
> and is not the project's official page.
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
>

Re: Updated ES Translation to actual head.

[Luis Gil]

El 30/3/2016 9:30, "Luca Toscano"  escribió:
>
> Hi Yann,
>
>
> 2016-03-29 22:36 GMT+02:00 Yann Ylavic :
>>
>>
>> Thanks Luis, looks good, committed in r1737042.
>> I couldn't find any reference to the reviewer, Sergio Ramos, in any
>> previous commit, is he already a contributor of the existing spanish
>> translation?
>
>
> I think that we have a chicken/egg situation with people interested in
translations: we set a very reasonable quality bar (review requested) but
we don't have enough reviewers among committers to provide a quick
feedback. It has been discussed several times and we are still a bit slow
in processing translation patches, potentially driving away talented people
that wants to work for the httpd project.
>
> We could reach the compromise of accepting reviewers external to the
project stating it clearly with a banner on top of the translated pages, or
maybe just a note somewhere in http://httpd.apache.org/docs.
>
> Luca

El 29/3/2016 22:52, "Yann Ylavic"  escribió:
>
> On Tue, Mar 29, 2016 at 10:36 PM, Yann Ylavic 
wrote:
> >
> > Please next time, provide some patches (diffs) relative to the
> > existing trunk sources, it's easier to review and it also allows to
> > detect any change between your proposed version and the one in the
> > repository (either because there was a change in the meantime, or your
> > reference was outdated).
>
> Also (and sorry for being a bit picky :p ), we try to keep source
> files (including xml ones) lines under the 80 characters limit, which
> also helps readabilty.
> This is not an overly strict rule though, some URLs or references may
> inevitably not fit, that's a good practice for shared contributions.
> If you could apply this for next submissions (and ideally provide a
> patch for the existing lines which exceed this limit :), it would be
> really great.
>
> >
> > Nice work, thanks again.
> >
> > Regards,
> > Yann.
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>

Hello Yann:
I'm sorry if I left some of the lines with more than 80, I know about it in
a previous  email, and I tried to be careful not to overpass  that limit
but I can see I left some :/
It won't be any problem  on the next patches
Thank you for the commit and the feedback.
He Is a friend if mine he just reviewed the files, he's not in the project.

I agree with Luca the actual translation process is very slow, in my point
of view.

Have a nice day @docs

update r1737084

[Luis Gil]

Hello Yann:

Can you as a commiter, check for the spanish html documents and review the
bugzilla so we can close the issues?:

https://bz.apache.org/bugzilla/show_bug.cgi?id=58969
the xml file is in the repo, but not the html one :( (a build is required )
bind.html.es

and the new_features_2_4.html file in html format is not in the repo :/
could you check it please.
thanck you.

Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

Re: Updated ES Translation to actual head.

[Luis Gil]

PING @docs
On Thu, 24 Mar 2016 at 10:45 Luis Gil <ljgbpfeif...@googlemail.com> wrote:

> Hello:
> I have translated and arranged in alphabetically order the file
> glossary.xml.es
> It has been reviewed as the same as the other files, i am attaching here
> all the files.
> Now are updated and reviewed.
>
> Have a nice Easter.
> Luis.
>
>
> --
>
> Luis J.G
>
-- 

Luis J.G

Re: Any one doing it?

[Luis Gil]

Thanks  for the feedback, and yes it should be added  the script to the
crontab, I don't know neither if we can do that.
Regards

El mar., 29 de marzo de 2016 7:34, Christophe JAILLET <
christophe.jail...@wanadoo.fr> escribió:

> Le 24/03/2016 13:59, Eric Covener a écrit :
> > On Thu, Mar 24, 2016 at 6:09 AM, Luis Gil <ljgbpfeif...@googlemail.com>
> wrote:
> >> BTW, why the
> >> http://people.apache.org/~takashi/translation-status/test.html#trunk
> has
> >> been deleted? in my opinion was a nice way for new people that joins the
> >> documentation, as good as looking the BZ page.
> >>  -  Improving the documentation of the documentations' build system
> >> itself (requirements, procedures)
> >> I guess this last point its better to create a new page and separate if
> from
> >> the current page docsformat.html itself i guess.
> >
> > Personal websites need to be migrated by their owners after an infra
> > change somewhat recently.
> >
>
> The upgrade has been performed and this page (i.e.
> ~takashi/translation-status/test.html#trunk) is online again.
>
> Thx infra.
>
>
> It is now hosted on home.apache.org.
> people.apache.org should be removed in a near future.
>
> However, the output of the script does not seem to be updated anymore.
> I guess that a cron job should be adjusted for that, but I'm unsure that
> this can be done on the new location.
>
>
>
> CJ
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
> --

Luis J.G

Re: Any one doing it?

[Luis Gil]

In my opinion i do agree with it, but i dont know how many people is
currently working on the English 2.0 doc version.

El lun., 4 de abril de 2016 22:35, Marion & Christophe JAILLET <
christophe.jail...@wanadoo.fr> escribió:

> Great ! Thx :)
>
> Maybe jobs for 2.0 could be removed now to save a few cycles? I don't
> think anyone will update these translations now.
>
> CJ
>
> Le 04/04/2016 17:47, Takashi Sato a écrit :
> > Now http://people.apache.org/~takashi/translation-status/test.html
> > updates hourly.
> > My cron script transfers JSONs from minotaur.a.o to home.a.o.
> >
> > -
> > To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> > For additional commands, e-mail: docs-h...@httpd.apache.org
> >
> >
>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
> --

Luis J.G

Website documentation project

[Luis Gil]

Hello @docs
Sorry for being missing for a while ;)
Commit nº *986524/**986527* of the current site in collaboration with
Lucien Gentis. ( i have reviewed his files), He did a great job, and
because i loved what he has done, (plus my bit of work)  I have decided to
commit it to production.
Lately we had mention a change, in a thread of the mailing list, on how the
Doc translation can be done for new contrib so its easier for them to join
us.
This changes are now ONLINE :)
Check them out and tell us here if we missed up something.
And a gain nice work to all.
Regards.

PD.: i might review it in the staged still, i have encountered some
markdown errors i hadn´t realize before.
-- 

Luis J.G

FAQ in the docs-proyect

[Luis Gil]

Hello:
I have seen the FAQ page is not any more in the repo (now is in the wiki),
so i wonder if i can copy it from the Wiki and make the translation of it
as index.xml.es file under the faq/ dir.
Is it possible?.
Regards.

-- 

Luis J.G

updated styles

[Luis Gil]

Hello @docs:
I as mention in other thread we are adding the *"bug check list"* so i made
my self to update the style in the ES translation and i came  across with
this in the English version :

 Google Search 
Index 
Home 

Should not it be removed?

Regards!
-- 

Luis J.G

Re: FAQ in the docs-proyect

[Luis Gil]

Great, then if i got time i will take a closer look to the wiki FAQ so we
can bring it *here* ;)
El 26/4/2016 15:36, "Rich Bowen" <rbo...@rcbowen.com> escribió:

>
>
> On 04/25/2016 09:33 PM, Luis Gil wrote:
> > Actually i was thinking about some filtering, or maybe add some if
> > needed, but OFC i will not do work that it will be in vain...
>
> It's not in vain. We removed the FAQ because it was garbage, not because
> we don't want an FAQ.
>
> Also, the wiki was initially created (at least, in my mind) to provide
> scratch space for the official docs. That is, we draft it *there* and we
> then bring it *here* when it's done. That ended up not happening, but
> it's still how I tend to think about it.
>
> --Rich
>
> >
> >
> > On Mon, 25 Apr 2016 at 13:47 Rich Bowen <rbo...@rcbowen.com
> > <mailto:rbo...@rcbowen.com>> wrote:
> >
> > History: we dropped the FAQ page because it was so grossly out of
> date
> > that it wasn't readily salvageable. I don't object to Frequently
> Asked
> > Questions pages if they are indeed frequently asked questions. What
> we
> > had were not, and many of the answers were bad.
> >
> > I haven't looked at the one in the Wiki for a while. I don't think
> it's
> > likely that we want to copy it wholesale, but, perhaps, use a little
> > more filtering.
> >
> > On 04/25/2016 07:28 AM, Luis Gil wrote:
> > > Hello:
> > > I have seen the FAQ page is not any more in the repo (now is in the
> > > wiki), so i wonder if i can copy it from the Wiki and make the
> > > translation of it as index.xml.es <http://index.xml.es>
> > <http://index.xml.es> file under the
> > > faq/ dir.
> > > Is it possible?.
> > > Regards.
> > >
> > > --
> > >
> > > Luis J.G
> > >
> >
> >
> > --
> > Rich Bowen - rbo...@rcbowen.com <mailto:rbo...@rcbowen.com> -
> @rbowen
> > http://apachecon.com/ - @apachecon
> >
> > --
> >
> > Luis J.G
> >
>
>
> --
> Rich Bowen - rbo...@rcbowen.com - @rbowen
> http://apachecon.com/ - @apachecon
>
>

Re: FAQ in the docs-proyect

[Luis Gil]

Actually i was thinking about some filtering, or maybe add some if needed,
but OFC i will not do work that it will be in vain...


On Mon, 25 Apr 2016 at 13:47 Rich Bowen <rbo...@rcbowen.com> wrote:

> History: we dropped the FAQ page because it was so grossly out of date
> that it wasn't readily salvageable. I don't object to Frequently Asked
> Questions pages if they are indeed frequently asked questions. What we
> had were not, and many of the answers were bad.
>
> I haven't looked at the one in the Wiki for a while. I don't think it's
> likely that we want to copy it wholesale, but, perhaps, use a little
> more filtering.
>
> On 04/25/2016 07:28 AM, Luis Gil wrote:
> > Hello:
> > I have seen the FAQ page is not any more in the repo (now is in the
> > wiki), so i wonder if i can copy it from the Wiki and make the
> > translation of it as index.xml.es <http://index.xml.es> file under the
> > faq/ dir.
> > Is it possible?.
> > Regards.
> >
> > --
> >
> > Luis J.G
> >
>
>
> --
> Rich Bowen - rbo...@rcbowen.com - @rbowen
> http://apachecon.com/ - @apachecon
>
> --

Luis J.G

HELP

[Luis Gil]

Hi:
does some one has encountered this error befor?

when i do a commit, it tells me that
“Inconsistent line ending style”
i have read in the stafkoverflow forum and its the Windows or unix like EOL
and i have fixed in the main xml file but, the one its generated with the
build script  its not "valid " for the svn on the commit...
any tips to fix this?
Many thanks.
-- 

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

[Luis Gil]

On Tue, 10 May 2016 at 16:02 Eric Covener <cove...@gmail.com> wrote:

> On Tue, May 10, 2016 at 6:58 AM, Luis Gil <ljgbpfeif...@googlemail.com>
> 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

Re: Spanish Apache httpd 2.4's modules development guide

[Luis Gil]

Hello Valen:
If  You want we could add this to the official docs page, you had made a
great work!
Greetings


Buenas Valen:
He visto tu trabajo y la verda que esta muy bien explicado, si quieres
podemos incluirlo en la documentación oficial.
Salu2!

On Mon, 9 May 2016 at 18:08 Valen BG  wrote:

> Hi, recently I've been playing with Apache httpd's modules and
> particularly the info in this guide
> . I've made a
> module development guide completely in spanish that may be useful for you.
> If you want to check it out, I've posted it in my GitHub, along with the
> example code and other useful stuff:
>
> http://github.com/valenbg1/auth-example-mod-apache
>
> Happy module coding! :)
>
> --
>
> Buenas, recientemente he estado aprendiendo sobre los módulos de Apache
> httpd y particularmente la información de esta guía
> . He escrito
> una guía para desarrollar módulos completamente en español que os podría
> resultar útil. Si queréis echarle un vistazo, está colgada en mi GitHub,
> junto con el código de ejemplo y otras cosas útiles:
>
> http://github.com/valenbg1/auth-example-mod-apache
>
> Espero que os sirva de ayuda :)
>
-- 

Luis J. Gil de Bernabé Pfeiffer.

Re: Doc translation: what about a new workflow?

[Luis Gil]

Hello
Marion & Christophe:
Thank you on the first hand.

Linkedin:   https://linkd.in/Ljjt8L
Twitter : https://twitter.com/luigy_tspg

On 17 April 2016 at 07:20,
Marion & Christophe JAILLET <christophe.jail...@wanadoo.fr> wrote:
>
> Hi docs@,
>
> a few weeks ago someone, a discussion [1] has started about using a web
based application in order to translate our documentation.
> The proposal was about Transifex [2].
>
> Another tool that looks similar is provided by the Apache Foundation
itself: https://translate.apache.org/
> It works with Pootle. (see [3] which is the version used on t.a.o)
>
> I don't know yet if our doc format is convenient for it.
> At least, it can use .po files.
> Tools exist to convert docbook (more or less our doc format) to .po
files, handle translation and generate back some docbook document.
> I have already used something called 'po4a' for such a process.
>
> The workflow would be:
>main documentation in XML files --> generate/manage pot file -->
generate/manage po files --> translate using t.a.o --> generate updated XML
files for each languages --> generate html/pdf... as we actually do
>
>
> The pros:
> - IMHO, following changes with po files is easier for translators
> - trunk/2.4.x are mainly the same files. They could be merged in the
same po files to avoid duplication of translation effort
> - using po files keeps the document structure itself (formatting,
links, ...). So the translator only has to focus on the translation of the
text itself
> - translating is easier and can be shared easily between different
people
> - easy access to translation statistic
> - svn integration
>
> The cons:
> - the translator doesn't have a global view of the file he is working
on
> - new tools and new intermediate file format
> - more complex doc generation process
>
>
> Anyway, I think that our translation workflow is too complex.
> Apart from the French translation (huge thanks, Lucien) and Spanish which
sees some interest and looks promising (Thanks and welcome Luis),
everything else is more or less dead.
> So anything that ease access to new translators is a win.
>
>
>
> We would like to have your feedback about the actual doc translation
process:
> - Do you think that using XML files for the translation is convenient?
Pros, Cons...
> - Do you think that using .po files would help to keep track of
translation changes?
> - Do you think that using a web based interface for translation would be
a win?
> Any thought?
>
>
> CJ
>
>
> [1] http://marc.info/?t=14571654492=1=2
> [2] http://www.transifex.com
> [3] http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/
>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>


On the other hand, I want to share my opinion over this.
The way we are translating things now @httpd looks good, i mean the xml
files (for me was easy to follow up the format etc) and the build process
is totally automated ( o.f.c. we would need to update stuff).

But the main thing for keeping track and getting things going on the
translation, (for non committers its hard).
Files in the mailing list sometimes get lost, on the threads.

So talking about what you suggest, Transifex its good, but how we will
integrate the *.po files and make the Jenkins or what ever (i actually know
how we build the web, just when we do the ./build ) anyway we should not
discard this new stuff, at least if it will make our workflow easy and
faster.

If we are integrating Pootle, i'm not sure if you need to learn too python
(Django), i have been using the framework and its very flexible and it can
i think integrarte with what we are doing, but the thing is, we need to
create the Django backend and structure for the web, and... well i'm not
sure how much time we will need on this (correct me if i'm wrong)

so resuming i see the following:

   1. Transifex will be a pain in the ass for ASF because the build process
   i guess.
   2. Pootle it could be the best way if we would like to move forwards, in
   the way Django works.
   3. We will need to update the backend (i guess) to integrate this tools,
   maybe use Jenkins or other automate deploy software.

Best regards.
Luis Gil de Bernabé.
PD: if at any time will this be going to be any option, i would be pleased
to help on the back-end work ;)

-- 

Luis J.G

Re: Doc translation: what about a new workflow?

[Luis Gil]

Hello
I think the modification should be included in translation.mdtext?
Regards

El mié., 20 de abril de 2016 10:18, Lucien Gentis <
lucien.gen...@univ-lorraine.fr> escribió:

>
>
> Le 20/04/2016 02:16, Rich Bowen a écrit :
>
>
> On Apr 18, 2016 08:57, "Lucien Gentis" <lucien.gen...@univ-lorraine.fr>
> wrote:
> >
> >
> >
> > As a beginning, how about adding an item "Translation" in "Want to
> contribute to the Apache HTTP Server?" on http://httpd.apache.org/ ?
> > This item could contain a call not only for translators , but also for
> Reviewers of the doc that "has not been reviewed"  (as proposed below)
>
> That document is here:
> http://httpd.apache.org/docs-project/translations.html
>
> Yes, it can be greatly improved.
>
> >
>
>
> I agree.
>
> Luis Gil has begun to improve this part of the documentation in his bug
> report :
>
> https://bz.apache.org/bugzilla/show_bug.cgi?id=59341
>
> So I go on there
>
> --
> Lucien GENTIS
> UNIVERSITE DE LORRAINE - ESPE
> Centre de Ressources Informatiques
> 5, Rue Paul Richard
> C.O. 3 - MAXEVILLE
> 54528 LAXOU-CEDEX
>
> Tél. 03 72 74 13 28
> Email : lucien.gen...@univ-lorraine.fr
>
> --

Luis J.G

Re: Any one doing it?

[Luis Gil]

Hello,
Is it ok to submmit this patch?

On Thu, 7 Apr 2016 at 17:22 Luis Gil <ljgbpfeif...@googlemail.com> wrote:

> Thank you Lucien nice changes,
> I have checked now the URL [IBM
> developerWorks](http://www-106.ibm.com/developerworks/xml/library/x-emacs/).
> and its actually not working but i have found this:
> i hve not much idea with emacs, so any one using it, which should be
> better on this ?
> https://www.emacswiki.org/emacs/CategoryXML
> I think if we change thar URL and we accept all this revision and changes,
> it would be good to put it online.
> Regards.
> Luis
>
>
>
> On Thu, 7 Apr 2016 at 16:33 Lucien Gentis <lucien.gen...@univ-lorraine.fr>
> wrote:
>
>> So here is attached a change suggestion for your file.
>>
>> I only looked at the translation part.
>>
>>
>> Lucien
>>
>>
>> Le 04/04/2016 11:44, Lucien Gentis a écrit :
>>
>> Anyway, I'll take a look at your page, . . . , as well
>>
>> Cheers
>>
>> Lucien
>>
>> Le 04/04/2016 11:38, Luis Gil a écrit :
>>
>>
>>
>> On Mon, 4 Apr 2016 at 11:33 Luis Gil <ljgbpfeif...@googlemail.com> wrote:
>>
>>> Ok... OH god i press too much the S key =O
>>>
>>> On Mon, 4 Apr 2016 at 11:19 Lucien Gentis <
>>> lucien.gen...@univ-lorraine.fr> wrote:
>>>
>>>>
>>>>
>>>> Le 04/04/2016 10:51, Luis Gil a écrit :
>>>>
>>>> Is that a like or dislike ;)
>>>>
>>>> El lun., 4 de abril de 2016 9:03, Lucien Gentis <
>>>> lucien.gen...@univ-lorraine.fr> escribió:
>>>>
>>>>>
>>>>>
>>>>> Le 01/04/2016 20:04, Luis Gil a écrit :
>>>>>
>>>>>
>>>>>
>>>>> Linkedin:   https://linkd.in/Ljjt8L
>>>>> Twitter : https://twitter.com/luigy_tspg
>>>>>
>>>>> On 1 April 2016 at 18:49, Yann Ylavic <ylavic@gmail.com> wrote:
>>>>>
>>>>>> On Fri, Apr 1, 2016 at 6:36 PM, Luca Toscano <toscano.l...@gmail.com>
>>>>>> wrote:
>>>>>> >
>>>>>> > +1, let's concentrate on 2.4 :)
>>>>>>
>>>>>> You know, there is still many 2.2 around, and some people may have
>>>>>> backported 2.4 fixes to 2.2 and decide to propose them some days.
>>>>>> If three PMC members (at least) think a 2.2.32 is worth it, it may
>>>>>> well be out ;)
>>>>>>
>>>>>> But I agree that we should mainly reference 2.4 in the "generic" docs.
>>>>>>
>>>>>> Regards,
>>>>>> Yann.
>>>>>>
>>>>>> -
>>>>>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>>>>>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>>>>>
>>>>>>
>>>>> Hello:
>>>>> Check this draft i have made of the docsformat page and tell me how
>>>>> you see it.
>>>>>
>>>>> i attach ass well a diff file so it can be easy to view the changes.
>>>>> ​
>>>>>
>>>>> =-O
>>>>>
>>>> Just reread your last sentence :-)
>>>>
>>>>
>>>>>
>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>>>>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>>>>
>>>>>
>>>>> --
>>>>> Lucien GENTIS
>>>>> UNIVERSITE DE LORRAINE - ESPE
>>>>> Centre de Ressources Informatiques
>>>>> 5, Rue Paul Richard
>>>>> C.O. 3 - MAXEVILLE
>>>>> 54528 LAXOU-CEDEX
>>>>>
>>>>> Tél. 03 72 74 13 28
>>>>> Email : lucien.gen...@univ-lorraine.fr
>>>>>
>>>>> --
>>>>
>>>> Luis J.G
>>>>
>>>>
>>>> --
>>>> Lucien GENTIS
>>>> UNIVERSITE DE LORRAINE - ESPE
>>>> Centre de Ressources Informatiques
>>>> 5, Rue Paul Richard
>>>> C.O. 3 - MAXEVILLE
>>>> 54528 LAXOU-CEDEX
>>>>
>>>> Tél. 03 72 74 13 28
>>>> Email : lucien.gen...@univ-lorraine.fr
>>>>
>>>> --
>>>
>>> Luis J.G
>>>
>>
>>
>> By the way i have made a small change on the page, give it a review.
>> Regards
>> Luis
>> --
>>
>> Luis J.G
>>
>>
>> -
>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>
>>
>> --
>> Lucien GENTIS
>> UNIVERSITE DE LORRAINE - ESPE
>> Centre de Ressources Informatiques
>> 5, Rue Paul Richard
>> C.O. 3 - MAXEVILLE
>> 54528 LAXOU-CEDEX
>>
>> Tél. 03 72 74 13 28
>> Email : lucien.gen...@univ-lorraine.fr
>>
>>
>> --
>> Lucien GENTIS
>> UNIVERSITE DE LORRAINE - ESPE
>> Centre de Ressources Informatiques
>> 5, Rue Paul Richard
>> C.O. 3 - MAXEVILLE
>> 54528 LAXOU-CEDEX
>>
>> Tél. 03 72 74 13 28
>> Email : lucien.gen...@univ-lorraine.fr
>>
>>
>> -
>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: docs-h...@httpd.apache.org
>
> --
>
> Luis J.G
>
-- 

Luis J.G

Re: Important SSL ciphers undocumented

[Luis Gil de Bernabé]

Hi,
i wouldn't recommend you to use the 1.0.1f version, since it has a CVE-2016-2107



On 9 June 2016 at 09:19, Hildegard Meier  wrote:
>
> Hello,
>
> regarding the page
>
> https://httpd.apache.org/docs/current/mod/mod_ssl.html#sslciphersuite
>
> (using Apache 2.4.7 and openssl 1.0.1f)
>
> I am missing some ciphers (or aliases?), which are really important to 
> mention, I think, since they provide better security:
>
> AESCGM (no mentioning of CGM at all)
>
> ECDHE
>
> I would suggest the sentence "Newer openssl versions may include additional 
> ciphers." to be written _bold_, to pretend confusion.
>
>
> I would suggest to add a column "available with openssl version" in the tag 
> table.
>
> It's confusing for me what is the relation between DHE and EDH. E.g.

you can see here (second comment, for me its a good explanation)
http://openssl.6102.n7.nabble.com/EDH-vs-DHE-which-specifications-use-the-term-quot-EDH-quot-td47752.html


>
> openssl ciphers -v 'DHE'
> Error in cipher list
> 139664124364448:error:1410D0B9:SSL routines:SSL_CTX_set_cipher_list:no cipher 
> match:ssl_lib.c:1314:


try to update your openssl ;)
i have tried to do as you say and it gives me  the lists as folow :
apache@ubuntu:~$ openssl ciphers -v 'DHE'
DHE-DSS-AES256-GCM-SHA384 TLSv1.2 Kx=DH   Au=DSS  Enc=AESGCM(256) Mac=AEAD
DHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=DH   Au=RSA  Enc=AESGCM(256) Mac=AEAD
DHE-RSA-AES256-SHA256   TLSv1.2 Kx=DH   Au=RSA  Enc=AES(256)  Mac=SHA256
DHE-DSS-AES256-SHA256   TLSv1.2 Kx=DH   Au=DSS  Enc=AES(256)  Mac=SHA256
DHE-RSA-AES256-SHA  SSLv3 Kx=DH   Au=RSA  Enc=AES(256)  Mac=SHA1
DHE-DSS-AES256-SHA  SSLv3 Kx=DH   Au=DSS  Enc=AES(256)  Mac=SHA1
DHE-RSA-CAMELLIA256-SHA SSLv3 Kx=DH   Au=RSA  Enc=Camellia(256) Mac=SHA1
DHE-DSS-CAMELLIA256-SHA SSLv3 Kx=DH   Au=DSS  Enc=Camellia(256) Mac=SHA1
DHE-DSS-AES128-GCM-SHA256 TLSv1.2 Kx=DH   Au=DSS  Enc=AESGCM(128) Mac=AEAD
DHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=DH   Au=RSA  Enc=AESGCM(128) Mac=AEAD
DHE-RSA-AES128-SHA256   TLSv1.2 Kx=DH   Au=RSA  Enc=AES(128)  Mac=SHA256
DHE-DSS-AES128-SHA256   TLSv1.2 Kx=DH   Au=DSS  Enc=AES(128)  Mac=SHA256
DHE-RSA-AES128-SHA  SSLv3 Kx=DH   Au=RSA  Enc=AES(128)  Mac=SHA1
DHE-DSS-AES128-SHA  SSLv3 Kx=DH   Au=DSS  Enc=AES(128)  Mac=SHA1
DHE-RSA-SEED-SHASSLv3 Kx=DH   Au=RSA  Enc=SEED(128) Mac=SHA1
DHE-DSS-SEED-SHASSLv3 Kx=DH   Au=DSS  Enc=SEED(128) Mac=SHA1
DHE-RSA-CAMELLIA128-SHA SSLv3 Kx=DH   Au=RSA  Enc=Camellia(128) Mac=SHA1
DHE-DSS-CAMELLIA128-SHA SSLv3 Kx=DH   Au=DSS  Enc=Camellia(128) Mac=SHA1
EDH-RSA-DES-CBC3-SHASSLv3 Kx=DH   Au=RSA  Enc=3DES(168) Mac=SHA1
EDH-DSS-DES-CBC3-SHASSLv3 Kx=DH   Au=DSS  Enc=3DES(168) Mac=SHA1


>
>
> openssl ciphers -v 'EDH'
> DHE-DSS-AES256-GCM-SHA384 TLSv1.2 Kx=DH   Au=DSS  Enc=AESGCM(256) Mac=AEAD
> [...]
>
> So querying DHE gives an error, and querying EDH outputs DHE ciphers ? Why 
> that?

and doing  your query above:

apache@ubuntu:~$ openssl ciphers -v 'EDH'
DHE-DSS-AES256-GCM-SHA384 TLSv1.2 Kx=DH   Au=DSS  Enc=AESGCM(256) Mac=AEAD
DHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=DH   Au=RSA  Enc=AESGCM(256) Mac=AEAD
DHE-RSA-AES256-SHA256   TLSv1.2 Kx=DH   Au=RSA  Enc=AES(256)  Mac=SHA256
DHE-DSS-AES256-SHA256   TLSv1.2 Kx=DH   Au=DSS  Enc=AES(256)  Mac=SHA256
DHE-RSA-AES256-SHA  SSLv3 Kx=DH   Au=RSA  Enc=AES(256)  Mac=SHA1
DHE-DSS-AES256-SHA  SSLv3 Kx=DH   Au=DSS  Enc=AES(256)  Mac=SHA1
DHE-RSA-CAMELLIA256-SHA SSLv3 Kx=DH   Au=RSA  Enc=Camellia(256) Mac=SHA1
DHE-DSS-CAMELLIA256-SHA SSLv3 Kx=DH   Au=DSS  Enc=Camellia(256) Mac=SHA1
DHE-DSS-AES128-GCM-SHA256 TLSv1.2 Kx=DH   Au=DSS  Enc=AESGCM(128) Mac=AEAD
DHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=DH   Au=RSA  Enc=AESGCM(128) Mac=AEAD
DHE-RSA-AES128-SHA256   TLSv1.2 Kx=DH   Au=RSA  Enc=AES(128)  Mac=SHA256
DHE-DSS-AES128-SHA256   TLSv1.2 Kx=DH   Au=DSS  Enc=AES(128)  Mac=SHA256
DHE-RSA-AES128-SHA  SSLv3 Kx=DH   Au=RSA  Enc=AES(128)  Mac=SHA1
DHE-DSS-AES128-SHA  SSLv3 Kx=DH   Au=DSS  Enc=AES(128)  Mac=SHA1
DHE-RSA-SEED-SHASSLv3 Kx=DH   Au=RSA  Enc=SEED(128) Mac=SHA1
DHE-DSS-SEED-SHASSLv3 Kx=DH   Au=DSS  Enc=SEED(128) Mac=SHA1
DHE-RSA-CAMELLIA128-SHA SSLv3 Kx=DH   Au=RSA  Enc=Camellia(128) Mac=SHA1
DHE-DSS-CAMELLIA128-SHA SSLv3 Kx=DH   Au=DSS  Enc=Camellia(128) Mac=SHA1
EDH-RSA-DES-CBC3-SHASSLv3 Kx=DH   Au=RSA  Enc=3DES(168) Mac=SHA1
EDH-DSS-DES-CBC3-SHASSLv3 Kx=DH   Au=DSS  Enc=3DES(168) Mac=SHA1

As you can see, it gives me the same result, nothing changes...
 but, if you try a wrong query, for exapmle 'E' and then try out 'DEH'
that will give you an error... strange but true, you should think in
opne  a bugg issue  to the openssl team maybe im not sure what is
this; i was just messing around with openssl and found that weird
behaviour.

>
>
>
> I have read this documentation about the SSLCiphersuite 

Build fails :(

[Luis Gil de Bernabé]

hello folks:
I have done the "*build es*" and one of the files is giving me errors on
the build, and chrome prompts me out the following error message:
This page contains the following errors:
error on line 53 at column 1: Extra content at the end of the document
Below is a rendering of the page up to the first error.


That line that says there is the end of the file... so i don´t get this
stupid error :/
And doing the *validate-xhtml* i got: \quickreference.html.es:
org.xml.sax.SAXParseException: XML document structures must start and end
within the same entity.
quickreference.html.es is not a valid XML document
And i have tried to *clean* up again and re build it but nothing
happends...
Cheers


Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

Re: Build fails :(

[Luis Gil de Bernabé]

The branch is trunk.
The main steps i follow up to do the build is
1- build validate-xml
2- build es
3- build validate-xhtml
If i got fails i use to build clean and go back to step 1
The command you are suggesting is "build make validate-xml"?
Thanks for an other point of view.
(We might gather a FAQ for the documentation process in a no long future ;)
)
El 7/6/2016 14:36, "Jeff Trawick" <traw...@gmail.com> escribió:

> On Tue, Jun 7, 2016 at 7:29 AM, Luis Gil de Bernabé <
> ljgbpfeif...@googlemail.com> wrote:
>
>> hello folks:
>> I have done the "*build es*" and one of the files is giving me errors on
>> the build, and chrome prompts me out the following error message:
>> This page contains the following errors:
>> error on line 53 at column 1: Extra content at the end of the document
>> Below is a rendering of the page up to the first error.
>>
>>
>> That line that says there is the end of the file... so i don´t get this
>> stupid error :/
>> And doing the *validate-xhtml* i got: \quickreference.html.es:
>> org.xml.sax.SAXParseException: XML document structures must start and end
>> within the same entity.
>> quickreference.html.es is not a valid XML document
>> And i have tried to *clean* up again and re build it but nothing
>> happends...
>> Cheers
>>
>>
>> Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
>> Twitter : https://twitter.com/luigy_tspg
>>
>
> Is this trunk or 2.4.x branch?
>
> "make validate-xml" from the top directory as well as "./build.sh es" from
> the docs/manual/build directory both work for me from both branches, but I
> guess this isn't what you are doing.  What are you doing differently?
>
> (I'm no expert here, but sometimes a different set of eyeballs will help;
> I've seen that validation error in the past and had to find the issue.)
>
> --
> Born in Roswell... married an alien...
> http://emptyhammock.com/
>
>

Re: Build fails :(

[Luis Gil de Bernabé]

Interesting and strange at same time.
So i guess its solved?
El 7/6/2016 14:59, "Lucien Gentis" <lucien.gen...@univ-lorraine.fr>
escribió:

> I launched the same commands as yours and got no error.
>
> As well, your HTML online page (
> http://httpd.apache.org/docs/trunk/es/mod/quickreference.html) displays
> without error with Firefox 46 0.1.
>
> Le 07/06/2016 à 14:41, Luis Gil de Bernabé a écrit :
>
> The branch is trunk.
> The main steps i follow up to do the build is
> 1- build validate-xml
> 2- build es
> 3- build validate-xhtml
> If i got fails i use to build clean and go back to step 1
> The command you are suggesting is "build make validate-xml"?
> Thanks for an other point of view.
> (We might gather a FAQ for the documentation process in a no long future
> ;) )
> El 7/6/2016 14:36, "Jeff Trawick" <traw...@gmail.com> escribió:
>
>> On Tue, Jun 7, 2016 at 7:29 AM, Luis Gil de Bernabé <
>> ljgbpfeif...@googlemail.com> wrote:
>>
>>> hello folks:
>>> I have done the "*build es*" and one of the files is giving me errors
>>> on the build, and chrome prompts me out the following error message:
>>> This page contains the following errors:
>>> error on line 53 at column 1: Extra content at the end of the document
>>> Below is a rendering of the page up to the first error.
>>>
>>>
>>> That line that says there is the end of the file... so i don´t get this
>>> stupid error :/
>>> And doing the *validate-xhtml* i got: \quickreference.html.es:
>>> org.xml.sax.SAXParseException: XML document structures must start and end
>>> within the same entity.
>>> quickreference.html.es is not a valid XML document
>>> And i have tried to *clean* up again and re build it but nothing
>>> happends...
>>> Cheers
>>>
>>>
>>> Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
>>> Twitter : https://twitter.com/luigy_tspg
>>>
>>
>> Is this trunk or 2.4.x branch?
>>
>> "make validate-xml" from the top directory as well as "./build.sh es"
>> from the docs/manual/build directory both work for me from both branches,
>> but I guess this isn't what you are doing.  What are you doing differently?
>>
>> (I'm no expert here, but sometimes a different set of eyeballs will help;
>> I've seen that validation error in the past and had to find the issue.)
>>
>> --
>> Born in Roswell... married an alien...
>> http://emptyhammock.com/
>>
>>
> --
> Lucien GENTIS
> UNIVERSITE DE LORRAINE - ESPE
> Centre de Ressources Informatiques
> 5, Rue Paul Richard
> C.O. 3 - MAXEVILLE
> 54528 LAXOU-CEDEX
>
> Tél. 03 72 74 13 28
> Email : lucien.gen...@univ-lorraine.fr
>
>

Re: Build fails :(

[Luis Gil de Bernabé]

Still the same, even with that space in between the lines.(i guess, from my
experience, that ws does not create an error)
El 7/6/2016 14:11, "Lucien Gentis" <lucien.gen...@univ-lorraine.fr>
escribió:

> Hello Luis,
>
> Don't know if it could create an error, but your quickreference.
> <http://quickreference.html.es/>xml.es is the one which doesn't have an
> empty line between license paragraph and the line :
>
> 
>
> Le 07/06/2016 à 13:59, Luis Gil de Bernabé a écrit :
>
>
> On 7 June 2016 at 13:52, Jeff Trawick <traw...@gmail.com> wrote:
>
>> On 6/7/2016 7:29:07 AM, Luis Gil de Bernabé <ljgbpfeif...@googlemail.com>
>> wrote:
>> hello folks:
>> I have done the "*build es*" and one of the files is giving me errors on
>> the build, and chrome prompts me out the following error message:
>> This page contains the following errors:
>> error on line 53 at column 1: Extra content at the end of the document
>> Below is a rendering of the page up to the first error.
>>
>>
>> That line that says there is the end of the file... so i don´t get this
>> stupid error :/
>> And doing the *validate-xhtml* i got: \quickreference.html.es:
>> org.xml.sax.SAXParseException: XML document structures must start and end
>> within the same entity.
>> quickreference.html.es is not a valid XML document
>> And i have tried to *clean* up again and re build it but nothing
>> happends...
>> Cheers
>>
>> *Jeff Trawick:*
>>
>> The xml source needs some change.  There's a syntax or semantic error
>> (e.g., paragraph within paragraph).
>>
>>
>>
>> Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
>> Twitter : https://twitter.com/luigy_tspg
>>
>>
> ​Hello Jeff:
> I'm confused about this, it got the same structure as the normal *xml*
> file​; so i don´t understand what you are saying, i might be missing
> something, could you explain it (sorry to bother)
> ​thx​
>
>
>
> --
> Lucien GENTIS
> UNIVERSITE DE LORRAINE - ESPE
> Centre de Ressources Informatiques
> 5, Rue Paul Richard
> C.O. 3 - MAXEVILLE
> 54528 LAXOU-CEDEX
>
> Tél. 03 72 74 13 28
> Email : lucien.gen...@univ-lorraine.fr
>
>

Re: Build fails :(

[Luis Gil de Bernabé]

On 7 June 2016 at 13:52, Jeff Trawick <traw...@gmail.com> wrote:

> On 6/7/2016 7:29:07 AM, Luis Gil de Bernabé <ljgbpfeif...@googlemail.com>
> wrote:
> hello folks:
> I have done the "*build es*" and one of the files is giving me errors on
> the build, and chrome prompts me out the following error message:
> This page contains the following errors:
> error on line 53 at column 1: Extra content at the end of the document
> Below is a rendering of the page up to the first error.
>
>
> That line that says there is the end of the file... so i don´t get this
> stupid error :/
> And doing the *validate-xhtml* i got: \quickreference.html.es:
> org.xml.sax.SAXParseException: XML document structures must start and end
> within the same entity.
> quickreference.html.es is not a valid XML document
> And i have tried to *clean* up again and re build it but nothing
> happends...
> Cheers
>
> *Jeff Trawick:*
>
> The xml source needs some change.  There's a syntax or semantic error
> (e.g., paragraph within paragraph).
>
>
>
> Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
> Twitter : https://twitter.com/luigy_tspg
>
>
​Hello Jeff:
I'm confused about this, it got the same structure as the normal *xml*
file​; so i don´t understand what you are saying, i might be missing
something, could you explain it (sorry to bother)
​thx​

Re: Spanish Apache httpd 2.4's modules development guide

[Luis Gil de Bernabé]

Hi Valen:
I'm so sorry, I was unable to do it due to a work load, this weekend I will
manage to send it to the official website.
My apologies.
Regards.

El jue., 26 de mayo de 2016 17:41, Valen BG 
escribió:

> Hi, should then we add my work to the official docs page?.
>
> Regards.
>
> --
>
> Subject: RE: Spanish Apache httpd 2.4's modules development guide
> From: Valen BG (valentin_gom...@hotmail.com)
> Date: May 11, 2016 8:07:34 am
>
>
> Hi Luis, totally OK with that. If there's any changes / adaptation to do
> I'm
> open to proposals.
>
>
>
> Regards, Valen BG.
>
>
>
> --
>
>
>
> Buenas Luis, totalmente de acuerdo. Si hay algún cambio o adaptación que
> hacer
> estoy abierto a propuestas.
>
>
>
> Un saludo, Valen BG.
>
>
> --
>
> From: ljgbpfeif...@googlemail.com
>
> Date: Tue, 10 May 2016 14:18:24 +
>
> Subject: Re: Spanish Apache httpd 2.4's modules development guide
>
> To: docs@httpd.apache.org
>
>
>
> Hello Valen:If You want we could add this to the official docs page, you
> had
> made a great work!Greetings
>
>
>
> **
>
>
>
> Buenas Valen: He visto tu trabajo y la verda que esta muy bien explicado,
> si quieres podemos incluirlo en la documentación oficial.Salu2!
>
>
> --
>
> *On Mon, 9 May 2016 at 18:08 Valen BG  > wrote: *
>
> Hi, recently I've been playing with Apache httpd's modules and
> particularly the
> info in this guide. I've made a module development guide completely in
> spanish
> that may be useful for you. If you want to check it out, I've posted it in
> my
> GitHub, along with the example code and other useful stuff:
> http://github.com/valenbg1/auth-example-mod-apache
>
> Happy module coding! :)
>
>
>
> *--*
>
>
>
> Buenas, recientemente he estado aprendiendo sobre los módulos de Apache
> httpd y
> particularmente la información de esta guía. He escrito una guía para
> desarrollar módulos completamente en español que os podría resultar útil.
> Si
> queréis echarle un vistazo, está colgada en mi GitHub, junto con el código
> de
> ejemplo y otras cosas útiles:
> http://github.com/valenbg1/auth-example-mod-apache
>
> Espero que os sirva de ayuda :)
>
> --

Luis J. Gil de Bernabé Pfeiffer.

Re: Changes not displaying in production

[Luis Gil de Bernabé]

Yes,  I will check
​now ​
what I had made wrong.
Thank
​ you !​


El vie., 20 de mayo de 2016 15:35, Lucien Gentis <
lucien.gen...@univ-lorraine.fr> escribió:

> Hi luis,
> new_features_2_2.html does not contain your language (es)
>
> It's probably a build problem.
>
> Did you follow these steps :
>
>
>- cd /manual
>- svn add new_features_2_2.xml.es
>- copy the build folder (the one that contains build.sh) in
>/manual
>- cd /manual/build
>- ./build.sh validate-xml
>- cd 
>- svn commit
>- cd /manual/build
>- ./build.sh es
>- ./build.sh validate-xhtml
>    - cd 
>- svn commit
>
>
>
> Le 20/05/2016 à 14:13, Luis Gil de Bernabé a écrit :
>
> Hi again:
> Sorry if my last email was a bit confused.
> I will explain better here the issue:
> Recently this week i had committed the new_features_2_2.xml.es file. I
> wanted to review if it was ok and running in the production website so i
> checked http://httpd.apache.org/docs/trunk/new_features_2_2.html but
> still in english so i apend at the end of the url a ".es" as follows
> http://httpd.apache.org/docs/trunk/new_features_2_2.html.es and i got the
> changes maded and in the repo.
> Does any one knows  what is going on?
> Did i make something wrong?
> Regards.
>
> El jue., 19 de mayo de 2016 19:08, Luis Gil de Bernabé <
> ljgbpfeif...@googlemail.com> escribió:
>
>> Hello there!
>>
>>
>> Recently thus week I had committed several changes of the trunk repo of
>> the documentation, and I'm still seeing the English version of it.
>> Any one knows  why this I happening?
>> Regards
>>
>> PD: I was thinking that it could be because the migration but I'm not
>> sure.
>> --
>>
>> Luis J. Gil de Bernabé Pfeiffer.
>>
> --
>
> Luis J. Gil de Bernabé Pfeiffer.
>
>
> --
> Lucien GENTIS
> UNIVERSITE DE LORRAINE - ESPE
> Centre de Ressources Informatiques
> 5, Rue Paul Richard
> C.O. 3 - MAXEVILLE
> 54528 LAXOU-CEDEX
>
> Tél. 03 72 74 13 28
> Email : lucien.gen...@univ-lorraine.fr
>
>

Re: Changes not displaying in production

[Luis Gil de Bernabé]

Solved,
here is how, i forgot to commit the normal html file, i dint know that when
its rebuild it will change to add the new language ;)
Cheers have a nice weekend!

Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
Twitter : https://twitter.com/luigy_tspg

On 21 May 2016 at 08:44, Luis Gil de Bernabé <ljgbpfeif...@googlemail.com>
wrote:

> Yes,  I will check
> ​now ​
> what I had made wrong.
> Thank
> ​ you !​
>
>
> El vie., 20 de mayo de 2016 15:35, Lucien Gentis <
> lucien.gen...@univ-lorraine.fr> escribió:
>
>> Hi luis,
>> new_features_2_2.html does not contain your language (es)
>>
>> It's probably a build problem.
>>
>> Did you follow these steps :
>>
>>
>>- cd /manual
>>- svn add new_features_2_2.xml.es
>>- copy the build folder (the one that contains build.sh) in
>>/manual
>>- cd /manual/build
>>- ./build.sh validate-xml
>>- cd 
>>- svn commit
>>    - cd /manual/build
>>- ./build.sh es
>>- ./build.sh validate-xhtml
>>- cd 
>>- svn commit
>>
>>
>>
>> Le 20/05/2016 à 14:13, Luis Gil de Bernabé a écrit :
>>
>> Hi again:
>> Sorry if my last email was a bit confused.
>> I will explain better here the issue:
>> Recently this week i had committed the new_features_2_2.xml.es file. I
>> wanted to review if it was ok and running in the production website so i
>> checked http://httpd.apache.org/docs/trunk/new_features_2_2.html but
>> still in english so i apend at the end of the url a ".es" as follows
>> http://httpd.apache.org/docs/trunk/new_features_2_2.html.es and i got
>> the changes maded and in the repo.
>> Does any one knows  what is going on?
>> Did i make something wrong?
>> Regards.
>>
>> El jue., 19 de mayo de 2016 19:08, Luis Gil de Bernabé <
>> ljgbpfeif...@googlemail.com> escribió:
>>
>>> Hello there!
>>>
>>>
>>> Recently thus week I had committed several changes of the trunk repo of
>>> the documentation, and I'm still seeing the English version of it.
>>> Any one knows  why this I happening?
>>> Regards
>>>
>>> PD: I was thinking that it could be because the migration but I'm not
>>> sure.
>>> --
>>>
>>> Luis J. Gil de Bernabé Pfeiffer.
>>>
>> --
>>
>> Luis J. Gil de Bernabé Pfeiffer.
>>
>>
>> --
>> Lucien GENTIS
>> UNIVERSITE DE LORRAINE - ESPE
>> Centre de Ressources Informatiques
>> 5, Rue Paul Richard
>> C.O. 3 - MAXEVILLE
>> 54528 LAXOU-CEDEX
>>
>> Tél. 03 72 74 13 28
>> Email : lucien.gen...@univ-lorraine.fr
>>
>>

Changes not displaying in production

[Luis Gil de Bernabé]

Hello there!


Recently thus week I had committed several changes of the trunk repo of the
documentation, and I'm still seeing the English version of it.
Any one knows  why this I happening?
Regards

PD: I was thinking that it could be because the migration but I'm not sure.
-- 

Luis J. Gil de Bernabé Pfeiffer.

Re: Changes not displaying in production

[Luis Gil de Bernabé]

Hi again:
Sorry if my last email was a bit confused.
I will explain better here the issue:
Recently this week i had committed the new_features_2_2.xml.es file. I
wanted to review if it was ok and running in the production website so i
checked http://httpd.apache.org/docs/trunk/new_features_2_2.html but still
in english so i apend at the end of the url a ".es" as follows
http://httpd.apache.org/docs/trunk/new_features_2_2.html.es and i got the
changes maded and in the repo.
Does any one knows  what is going on?
Did i make something wrong?
Regards.

El jue., 19 de mayo de 2016 19:08, Luis Gil de Bernabé <
ljgbpfeif...@googlemail.com> escribió:

> Hello there!
>
>
> Recently thus week I had committed several changes of the trunk repo of
> the documentation, and I'm still seeing the English version of it.
> Any one knows  why this I happening?
> Regards
>
> PD: I was thinking that it could be because the migration but I'm not sure.
> --
>
> Luis J. Gil de Bernabé Pfeiffer.
>
-- 

Luis J. Gil de Bernabé Pfeiffer.

Re: Fwd: Broken link on Apache.org

[Luis Gil de Bernabé]

Hi,
I am trying to  fix all the links on the Spanish translation,  the
English links should be checked too.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59316
As recomended in the bug thread.
Cheers!



Linkedin:   https://linkd.in/Ljjt8L
Twitter : https://twitter.com/luigy_tspg


On 15 May 2016 at 10:59, Luca Toscano  wrote:
> [re-arranged email thread]
>
> 2016-05-13 23:46 GMT+02:00 Rich Bowen :
>>
>>
>> On May 12, 2016 7:44 PM, "Eric Covener"  wrote:
>>>
>>> -- Forwarded message --
>>> From: David Nalley 
>>> Date: Thu, May 12, 2016 at 7:40 PM
>>> Subject: Re: Broken link on Apache.org
>>> To: Jerry Lucas , d...@httpd.apache.org
>>> Cc: webmas...@apache.org
>>>
>>>
>>> Hi Jerry,
>>>
>>> Thanks for your report. I've forwarded this on to the Apache httpd
>>> project who is responsible for maintaining that specific website.
>>>
>>> Thanks,
>>>
>>> --David
>>>
>>> On Thu, May 12, 2016 at 6:16 PM, Jerry Lucas  wrote:
>>> > Hello Webmaster,
>>> >
>>> >
>>> >
>>> > I found a broken link on the web page at
>>> > http://httpd.apache.org/docs/current/misc/rewriteguide.html  Maybe it
>>> > should
>>> > be https://httpd.apache.org/docs/current/rewrite/
>>> >
>>> >
>>> >
>>> > I was doing some reading about setting up a 301 Redirect on my website
>>> > and I
>>> > watched an educational video from Google at
>>> > https://support.google.com/webmasters/answer/93633  The bottom of the
>>> > Google
>>> > article points to two outdated version links on Apache.org at
>>> > https://httpd.apache.org/docs/2.0/howto/htaccess.html  and
>>> > https://httpd.apache.org/docs/2.0/misc/rewriteguide.html   Those pages
>>> > announce at the top that they are old versions and direct the user to
>>> > the
>>> > current version.  But the link to the new rewrite guide page is broken
>>> > where
>>> > it reads:  You may follow this link to go to the current version of
>>> > this
>>> > document.
>
>
>> We'd need to work with infra to redirect that url. That page is long gone.
>
>
> I tried to leave a comment in the Google page, they link directly to 2.0
> docs (rather than current) so I suspect that page is very very old. I
> wouldn't be inclined to put an extra link in the 2.0 doc because to do a
> complete work we'd need to track down also all the other similar use cases.
> It might be easier to follow up properly with Google to fix their doc.. but
> this is of course IMHO :)
>
> Luca

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

Re: i hope to join japanese transration team

[Luis Gil de Bernabé]

Greeting and welcome to the comunity
Hope to help you
Regards

El 22 jul. 2016 16:29, "whywaita"  escribió:

> Hi Rich!
>
> Thanks for the replies & teach.
>
> I was successful contacts with the Japan team.
> https://twitter.com/tkusano/status/756439996978999297
> I wait a few days.
>
> Thank you! :)
>
> On 2016年7月22日 at 2:24:03, Rich Bowen (rbo...@rcbowen.com) wrote:
>
> Welcome!
>
> The docs about editing the docs are here:
> http://httpd.apache.org/docs-project/
>
> As we're not sure what your level of expertise is, please do feel free
> to ask for any assistance you need here. We would absolutely love to see
> the Japanese documentation updated, as they are rather far behind trunk.
>
> --Rich
>
> On 07/21/2016 12:57 PM, whywaita wrote:
> > Dear httpd docs contributors!
> >
> > I hope to join japanese transration team.
> > I found mistake in japanese documents.
> > I want to fix this mistake.
> >
> > Best Regard.
> >
> > --
> > 日本語のhttpdドキュメントに間違いがある事を発見したので、
> > これを修正すべく、日本語チームへの参加をお願いしたいです。
> >
> > よろしくお願いします。
> > 
> > Name: whywaita
> > Email: whywa...@whywrite.it 
> >
> > Site: https://whywrite.it
>
>
> --
> Rich Bowen - rbo...@rcbowen.com - @rbowen
> http://apachecon.com/ - @apachecon
>
> 
> Name: whywaita
> Email: whywa...@whywrite.it
>
> Site: https://whywrite.it
>

Re: [HELP] with error when building : ​org.xml.sax.SAXParseException: XML document structures must start and end within the same entity.

[Luis Gil de Bernabé]

Im afraid no i dont have a svn diff file

El 12 ago. 2016 21:30, "Rich Bowen" <rbo...@rcbowen.com> escribió:

>
>
> On 08/12/2016 07:13 AM, Luis Gil de Bernabé wrote:
> > H
> > ​ello Team:
> > How are you hollydays ;) i guess they going well.
> > I got a question on the build process and guessing not documented this
> > error is as follows:
> >
> > validate-xhtml:
> > [xmlvalidate]
> > E:\Repositorios\APACHE-DOC\httpd-doc\httpd-trunk2-redo\manual\mod\
> directives.html.es:24:206:
> > XML document structures must start and end within the same entity.
> > [xmlvalidate] Could not validate document
> > E:\Repositorios\APACHE-DOC\httpd-doc\httpd-trunk2-redo\manual\mod\
> directives.html.es
> > <http://directives.html.es>: org.xml.sax.SAXParseException: XML document
> > structures must start and end within the same entity.
> > [xmlvalidate]
> > E:\Repositorios\APACHE-DOC\httpd-doc\httpd-trunk2-redo\manual\mod\
> > ​​
> > directives.html.es <http://directives.html.es> is not a valid XML
> document
> > [xmlvalidate]
> > E:\Repositorios\APACHE-DOC\httpd-doc\httpd-trunk2-redo\manual\mod\
> > ​​
> > quickreference.html.es:53:1: XML document structures must start and end
> > within the same entity.
> > [xmlvalidate] Could not validate document
> > E:\Repositorios\APACHE-DOC\httpd-doc\httpd-trunk2-redo\manual\mod\
> quickreference.html.es
> > <http://quickreference.html.es>: *
> > ​​
> > org.xml.sax.SAXParseException:* XML document structures must start and
> > end within the same entity.
> > [xmlvalidate]
> > E:\Repositorios\APACHE-DOC\httpd-doc\httpd-trunk2-redo\manual\mod\
> quickreference.html.es
> > <http://quickreference.html.es> is not a valid XML document
> > [xmlvalidate] 726 file(s) have been successfully validated.
> >
> > ​Does some one got this error before and how can it be fixed?
>
> No, I don't get that error with what's currently in trunk. Do you have
> some `svn diff` in your working copy?
>
>
> > because i am concerned the xml file related to the HTML one its just a
> > few lines and then it generates a frame for the "index" at least in the
> > ​
> > *quickreference.html*
> >
> > And the same with the other file the xml its just a few lines and then
> > it generates a frame for the index of all directives
> > Any hint on this point? ​
> >
> > Thank you in advance.
> >
> >
> >
> > Linkedin:   https://linkd.in/Ljjt8L
> > Twitter : https://twitter.com/luigy_tspg
> >
> >
> >
> > -
> > To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> > For additional commands, e-mail: docs-h...@httpd.apache.org
> >
>
>
> --
> Rich Bowen - rbo...@rcbowen.com - @rbowen
> http://apachecon.com/ - @apachecon
>
>

Re: How to patch the docs

[Luis Gil de Bernabé]

El 15 jul. 2016 21:11, "Rich Bowen"  escribió:
>
> I periodically give a presentation on documentation - how to make your
> docs not suck, how to work with users to solve their problems, how to
> make it easier for people to contribute to the docs.
>
> I often give advice that we are not following in this docs project. Some
> of these are historical (I strongly encourage people to avoid formats
> like docbook that have a towering barrier to entry) but others are just
> laziness and lack of time. For example, implementing the comment system
> was something that I recommended, and Humbedooh implemented, but we're
> not leveraging to its full potential just because there are *thousands*
> of comments, and it takes time to get through them all.
>
> Anyways, I recently tried to contribute a docs patch to another Apache
> project, and ended up giving up in frustration, because I couldn't
> figure out how to do it, and didn't want to have to join a bunch of
> mailing lists just to fix a typo. In the process, I started wondering
> how hard it is to submit a patch to the httpd docs. If, say, I found a
> typo, what do I do?
>
> (Contrariwise, I was able to submit a patch to the Mesos docs with very
> little work, because they not only made it obvious where to do it, but
> were also polite and helpful when I did it wrong the first time.)
>
> Something that I recommend in my presentation is simple - tell me in the
> doc how to edit/patch the doc. For example, on my work website -
> http://rdoproject.org/ - you'll see an "edit on github" banner on every
> page. Simple and easy.
>
> For our docs, I'd like to have something on each page of the docs that
> indicates how one might patch the docs. This could simply be a link to
> http://httpd.apache.org/docs-project/ or it could be a link to the
> ticketing system. Patching our docs is, unfortunately, rather more
> complicated than just a link to Github, but any barrier that we can
> remove would be good.
>
> Any objections to my making a change to that effect to the docs build
> template?
>
> --
> 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
>

Hello Rich,
I understand your point i was on tye same situation some months ago, and i
was able to edit the webpage were it explains how to contribute, in my
opinion i think we need to reedit the main page
http://httpd.apache.org/docs-project/ because its a bit confusing(at least
it was for me).
You can count on me to help you on this.
Regards

Re: Spanish translation: httpd-trunk/docs/manual/howto/reverse_proxy.xml.es

[Luis Gil de Bernabé]

I will review it this afternoon thank you and great work !! 

El lun., 23 ene. 2017 15:51, Daniel  escribió:

> Hello,
>
> I translated:
> httpd-trunk/docs/manual/howto/reverse_proxy.xml.es
>
> Find the translation attached to this email.
>
>
> --
> *Daniel Ferradal*
> IT Specialist
>
> email dferradal at gmail.com
> linkedin es.linkedin.com/in/danielferradal
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org

-- 

Luis J. Gil de Bernabé Pfeiffer.

Re: Spanish Translation: docs/manual/howto.ssi.xml.es

[Luis Gil de Bernabé]

Thank you Rich, we will try our best :)

Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 18 February 2017 at 18:01, Rich Bowen  wrote:

> That document was originally an article in a magazine back in 1996 or
> something. Please feel free to update any of those sections that sounds
> like that. Almost everything in the howto directory is like that, although
> most of it has been updated more recently.
>
> On Feb 13, 2017 6:07 AM, "Daniel"  wrote:
>
>> Hello,
>>
>> Here is the Spanish translation for docs/manual/howto/ssi.es.xml
>>
>> In the original English version I found some "bloggy" comments, no big
>> deal, but I I had a bit of an issue translating them:
>>
>> Bloggy comments:
>> 1.The function can be one of a number of things, and we'll talk
>> some more about most of these in the next installment of this
>> series."
>>
>> Since I can't determine which is the "next installment" I decided to omit
>> this comment in the translation turning it into a bit of a more generic
>> statement.
>>
>> Which I decided to translate like:
>> Esta función es una de tantas, y hablaremos de algunas de ellas más
>> adelante
>>
>> Which would be like: "This function is one of many and we'll talk about
>> some of them later on (or ahead)."
>>
>> 2.I expect that I'll have an article some time in the coming
>> months about using SSI with small CGI programs.
>>
>> I decided to ommit this comment completely, as this seems a reference
>> from an outside source, perhaps a blog or similar.
>>
>> If I'm screwing up or misinterpreting, please let me know!
>> 
>>
>> There is also the case where a keyword ("config") is being used as a verb
>> in the same sentence , which may yield neat results in english but
>> translation to Spanish does not end well. (verb "configurar" in Spanish,
>> "config" can't be used as verb in Spanish so I can't use it, maybe this
>> play could be used if we were refering to the noum, such as configuration,
>> which in Spanish would be easier to refer to as "config", but not with a
>> verb like the meaning of the original sentences in english for this doc.)
>>
>> 1º In addition to being able to config the time
>> format, you can also config two other things.
>>
>> 2º And you can config the format in which file
>> sizes are returned
>>
>> for these I removed the  tags and used the verb directly, since
>> there are enough examples already in the whole document which refer to
>> config function, so I really found no need to work around this
>> way of using verb/keyword at the same time in Spanish, besides the results
>> of trying it in Spanish are not optimal.
>>
>>
>>
>> --
>> *Daniel Ferradal*
>> IT Specialist
>>
>> email dferradal at gmail.com
>> linkedin es.linkedin.com/in/danielferradal
>>
>>
>> -
>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>
>

Re: Spanish translation: httpd-trunk/docs/manual/howto/public_html.xml.es

[Luis Gil de Bernabé]

Thank you Daniel !!! :)

Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 13 January 2017 at 14:57, Daniel  wrote:

> Hello,
>
> I translated:
> httpd-trunk/docs/manual/howto/public_html.xml.es
>
> Find the translation attached to this email.
>
> Note: I switched my subscribed email at docs@ from dan...@ezra-s.net to
> dferra...@gmail.com (the former is just an alias that is causing me more
> hassle at gmail than anything, so I'm using my main email here now).
>
> --
> *Daniel Ferradal*
> IT Specialist
>
> email dferradal at gmail.com
> linkedin es.linkedin.com/in/danielferradal
>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>

Re: [HELP] with error when building : ​org.xml.sax.SAXParseException: XML document structures must start and end within the same entity.

[Luis Gil de Bernabé]

Nop, i just can diff it with the repo last version of the file.

Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
Twitter : https://twitter.com/luigy_tspg

On 17 August 2016 at 01:38, Rich Bowen <rbo...@rcbowen.com> wrote:

> On Aug 12, 2016 11:33 PM, "Luis Gil de Bernabé" <
> ljgbpfeif...@googlemail.com> wrote:
> >
> > Im afraid no i dont have a svn diff file
> >
>
> What I mean is, if you type 'svn diff' at the command line, does it show
> any local changes.
>
> >
> > El 12 ago. 2016 21:30, "Rich Bowen" <rbo...@rcbowen.com> escribió:
> >>
> >>
> >>
> >> On 08/12/2016 07:13 AM, Luis Gil de Bernabé wrote:
> >> > H
> >> > ​ello Team:
> >> > How are you hollydays ;) i guess they going well.
> >> > I got a question on the build process and guessing not documented this
> >> > error is as follows:
> >> >
> >> > validate-xhtml:
> >> > [xmlvalidate]
> >> > E:\Repositorios\APACHE-DOC\httpd-doc\httpd-trunk2-redo\manual\mod\
> directives.html.es:24:206:
> >> > XML document structures must start and end within the same entity.
> >> > [xmlvalidate] Could not validate document
> >> > E:\Repositorios\APACHE-DOC\httpd-doc\httpd-trunk2-redo\manual\mod\
> directives.html.es
> >> > <http://directives.html.es>: org.xml.sax.SAXParseException: XML
> document
> >> > structures must start and end within the same entity.
> >> > [xmlvalidate]
> >> > E:\Repositorios\APACHE-DOC\httpd-doc\httpd-trunk2-redo\manual\mod\
> >> > ​​
> >> > directives.html.es <http://directives.html.es> is not a valid XML
> document
> >> > [xmlvalidate]
> >> > E:\Repositorios\APACHE-DOC\httpd-doc\httpd-trunk2-redo\manual\mod\
> >> > ​​
> >> > quickreference.html.es:53:1: XML document structures must start and
> end
> >> > within the same entity.
> >> > [xmlvalidate] Could not validate document
> >> > E:\Repositorios\APACHE-DOC\httpd-doc\httpd-trunk2-redo\manual\mod\
> quickreference.html.es
> >> > <http://quickreference.html.es>: *
> >> > ​​
> >> > org.xml.sax.SAXParseException:* XML document structures must start
> and
> >> > end within the same entity.
> >> > [xmlvalidate]
> >> > E:\Repositorios\APACHE-DOC\httpd-doc\httpd-trunk2-redo\manual\mod\
> quickreference.html.es
> >> > <http://quickreference.html.es> is not a valid XML document
> >> > [xmlvalidate] 726 file(s) have been successfully validated.
> >> >
> >> > ​Does some one got this error before and how can it be fixed?
> >>
> >> No, I don't get that error with what's currently in trunk. Do you have
> >> some `svn diff` in your working copy?
> >>
> >>
> >> > because i am concerned the xml file related to the HTML one its just a
> >> > few lines and then it generates a frame for the "index" at least in
> the
> >> > ​
> >> > *quickreference.html*
> >> >
> >> > And the same with the other file the xml its just a few lines and then
> >> > it generates a frame for the index of all directives
> >> > Any hint on this point? ​
> >> >
> >> > Thank you in advance.
> >> >
> >> >
> >> >
> >> > Linkedin:   https://linkd.in/Ljjt8L
> >> > Twitter : https://twitter.com/luigy_tspg
> >> >
> >> >
> >> >
> >> > -
> >> > To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> >> > For additional commands, e-mail: docs-h...@httpd.apache.org
> >> >
> >>
> >>
> >> --
> >> Rich Bowen - rbo...@rcbowen.com - @rbowen
> >> http://apachecon.com/ - @apachecon
> >>
>

Re: Translations (IRC conversation)

[Luis Gil de Bernabé]

Hello Daniel
And of course welcome, here its a useful link to keep track on the
translation status of the branches:
http://people.apache.org/~takashi/translation-status/test.html

:)
Si tienes alguna duda, como trductor Español también no dudes en
contactarme.
Regards.


Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 20 October 2016 at 09:50, Daniel  wrote:

> Hello,
>
> I'm Daniel Ferradal, as Richard Bowen says, I plan to help translating to
> Spanish in the best way I can.
>
> To me this is all new, so when I saw in the httpd.apache.org which is the
> method you guys use to define the documentation, I did a checkout of
> httpd-2.4 and trunk and saw 2.4 had fewer translations, and so I thought it
> would be a good place to start.
>
> As Richard mentions, right now this is the list of trunk "html.es" files,
> the ones marked with * are not present in httpd-2.4.
> ./httpd-trunk/docs/manual/handler.html.es
> ./httpd-trunk/docs/manual/howto/auth.html.es *
> ./httpd-trunk/docs/manual/howto/access.html.es *
> ./httpd-trunk/docs/manual/invoking.html.es *
> ./httpd-trunk/docs/manual/new_features_2_2.html.es *
> ./httpd-trunk/docs/manual/glossary.html.es *
> ./httpd-trunk/docs/manual/index.html.es
> ./httpd-trunk/docs/manual/filter.html.es
> ./httpd-trunk/docs/manual/mpm.html.es
> ./httpd-trunk/docs/manual/programs/index.html.es
> ./httpd-trunk/docs/manual/faq/index.html.es
> ./httpd-trunk/docs/manual/custom-error.html.es
> ./httpd-trunk/docs/manual/sitemap.html.es
> ./httpd-trunk/docs/manual/stopping.html.es
> ./httpd-trunk/docs/manual/new_features_2_4.html.es *
> ./httpd-trunk/docs/manual/bind.html.es *
> ./httpd-trunk/docs/manual/mod/core.html.es
> ./httpd-trunk/docs/manual/mod/quickreference.html.es
> ./httpd-trunk/docs/manual/mod/directives.html.es
> ./httpd-trunk/docs/manual/mod/index.html.es
> ./httpd-trunk/docs/manual/install.html.es
>
> Seeing the difference I started translating one sample in httpd-2.4, if
> you guys like it I will just keep on working with trunk, httpd-2.4 or
> whatever you guys prefer.
>
> In my humble opinion it would be good to have all actual documentation, at
> least for 2.4 translated, since that's probably the most used docs, but
> just tell me where to point and I'll go. Rich told me to concentrate on
> trunk before anything else but if you want to point me to specific files,
> just tell me.
>
> Here is my first sample (bind.xml.es for httpd-2.4) , hope you guys like
> it:
>
>
>
>
> 2016-10-19 15:24 GMT+02:00 Rich Bowen :
>
>> (Summarizing a conversation from IRC)
>>
>> ezra-s (Daniel Ferradal) is beginning to work on our Spanish docs
>> translation. This led to discussion of a number of points surrounding
>> translations:
>>
>> * There are some (numerous?) .es files in 2.4 that are not in trunk.
>> These need to be identified, and where appropriate, copied/moved into
>> trunk, so that they are not lost in the future. Translation work should
>> (usually) happen in trunk first, and then be (intelligently - of course
>> some stuff is trunk-only) copied to 2.4 and possibly (?) 2.2. We have
>> apparently done a poor job of communicating and policing this, and need
>> to update our translation docs accordingly. The usual catchphrase is,
>> Upstream First.
>>
>> * We have translations that are grossly out of date. We should drop
>> them. It remains only to define what "tool old" means? If a translation
>> hasn't been touched since 2.4.0, I would recommend dropping it.
>> Discussion?
>>
>> * It also occurs to me that we should make specific recommendations of
>> which docs should be translated first. For example, I think that the
>> "Getting Started" doc, and the "HowTo" docs, would be good places to
>> start, while the module docs, being more about technical detail and
>> having a less conversational style, would come later.
>>
>> * All of this hinges on actually getting translators. It *seems* that
>> this used to be easier, but lately we have really stunk at attracting
>> new translators. I think that this might be because our review process
>> is so rigorous, and it's hard to find reviewers. But for certain
>> languages (Spanish, French, Japanese, Chinese, Russian) it would seem
>> that we have an enormous pool of users to draw from. Perhaps time to do
>> some recruiting on users@? I believe we should first address the above
>> items, though, so that they're coming into a well-documented encouraging
>> environment, rather than picking up a lot of abandoned partially
>> translated things. Indeed, it might be good to go ahead and drop entire
>> languages from trunk, so that a new translator has a clean slate to work
>> with. I know I find that less frustrating, myself.
>>
>> Please discuss, so I'm not just talking to myself. :-)
>>
>>
>> --
>> Rich Bowen - rbo...@rcbowen.com - @rbowen
>> http://apachecon.com/ - @apachecon
>>
>>
>
>
> --
> *Daniel Ferradal*
> IT Specialist
>
> email 

Re: Translations (IRC conversation)

[Luis Gil de Bernabé]

Hello Rich,
According to the first point could be may fault? im not sure, because i
have been working on the trunk since early beginning, and i migrate some
files to the 2.4 and older doc versions when i don´t forget of course haha.

Old stuff point, in my opinion it depends on how old this is, if its more
than 1 year maybe its too old? we have to set a "pass time" maybe.

The point you make suggesting to start on the How to and G.S guides, you
actually read my mind, (i´m actually doing so) but of course i did´t
started whit the files that were already outdated ;). for the new people
that join the community we should added to our starting guide of the doc
project, right?
hope to write more.
Have a nice day fellows


Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 19 October 2016 at 15:24, Rich Bowen  wrote:

> (Summarizing a conversation from IRC)
>
> ezra-s (Daniel Ferradal) is beginning to work on our Spanish docs
> translation. This led to discussion of a number of points surrounding
> translations:
>
> * There are some (numerous?) .es files in 2.4 that are not in trunk.
> These need to be identified, and where appropriate, copied/moved into
> trunk, so that they are not lost in the future. Translation work should
> (usually) happen in trunk first, and then be (intelligently - of course
> some stuff is trunk-only) copied to 2.4 and possibly (?) 2.2. We have
> apparently done a poor job of communicating and policing this, and need
> to update our translation docs accordingly. The usual catchphrase is,
> Upstream First.
>
> * We have translations that are grossly out of date. We should drop
> them. It remains only to define what "tool old" means? If a translation
> hasn't been touched since 2.4.0, I would recommend dropping it. Discussion?
>
> * It also occurs to me that we should make specific recommendations of
> which docs should be translated first. For example, I think that the
> "Getting Started" doc, and the "HowTo" docs, would be good places to
> start, while the module docs, being more about technical detail and
> having a less conversational style, would come later.
>
> * All of this hinges on actually getting translators. It *seems* that
> this used to be easier, but lately we have really stunk at attracting
> new translators. I think that this might be because our review process
> is so rigorous, and it's hard to find reviewers. But for certain
> languages (Spanish, French, Japanese, Chinese, Russian) it would seem
> that we have an enormous pool of users to draw from. Perhaps time to do
> some recruiting on users@? I believe we should first address the above
> items, though, so that they're coming into a well-documented encouraging
> environment, rather than picking up a lot of abandoned partially
> translated things. Indeed, it might be good to go ahead and drop entire
> languages from trunk, so that a new translator has a clean slate to work
> with. I know I find that less frustrating, myself.
>
> Please discuss, so I'm not just talking to myself. :-)
>
>
> --
> Rich Bowen - rbo...@rcbowen.com - @rbowen
> http://apachecon.com/ - @apachecon
>
>

Re: httpd-trunk/docs/manual/howto/index.xml.es Spanish translation

[Luis Gil de Bernabé]

Hello Daniel:
The file has been reviewed and committed the change to repo at revision:
1766312

Thank you.


Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
Twitter : https://twitter.com/luigy_tspg

On 23 October 2016 at 21:45, Luis Gil de Bernabé <
ljgbpfeif...@googlemail.com> wrote:

> Hello Daniel:
> Thank you for the contribution.
> I will review it as part of the Spanish Team commiter translators.
> Have a nice day.
>
>
> Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
> Twitter : https://twitter.com/luigy_tspg
>
> On 23 October 2016 at 15:07, Daniel <dan...@ezra-s.net> wrote:
>
>> Hello,
>>
>> I translated index.xml from manual/howto to spanish:
>>
>> httpd-trunk/docs/manual/howto/index.xml.es
>>
>> I'll continue picking files for which I see no translation and send them
>> to the mailing list, unless you guide me in other direction.
>>
>> --
>> *Daniel Ferradal*
>> IT Specialist
>>
>> email daniel at ezra-s.net
>> linkedin es.linkedin.com/in/danielferradal
>>
>>
>> -
>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>
>
>

Re: httpd-trunk/docs/manual/howto/index.xml.es Spanish translation

[Luis Gil de Bernabé]

Hello Daniel:
Thank you for the contribution.
I will review it as part of the Spanish Team commiter translators.
Have a nice day.


Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 23 October 2016 at 15:07, Daniel  wrote:

> Hello,
>
> I translated index.xml from manual/howto to spanish:
>
> httpd-trunk/docs/manual/howto/index.xml.es
>
> I'll continue picking files for which I see no translation and send them
> to the mailing list, unless you guide me in other direction.
>
> --
> *Daniel Ferradal*
> IT Specialist
>
> email daniel at ezra-s.net
> linkedin es.linkedin.com/in/danielferradal
>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>

Strange behaveur

[Luis Gil de Bernabé]

hello team:
I have issued that when i build the Quickreference.xml.es from the module
in teh trunk is not working as you can see:
http://httpd.apache.org/docs/trunk/es/mod/quickreference.html
but in the 2.4 brunch it is working... and its the same file... i dont get
it..
Any Tip?
thank you in advance.

Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

Re: small patch for httpd-trunk/docs/manual/howto/http2.xml

[Luis Gil de Bernabé]

Nice,
sounds better, but here an English spoken commiter might better check this
out :)
Regards.


Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 29 November 2016 at 17:37, Daniel  wrote:

> Hello,
>
> I'd like to submit a little patch for a sentence in:
> httpd-trunk/docs/manual/howto/http2.xml
>
> The original sentence I'm changing is:
> "There are still request and responses and headers and all that"
>
> and the proposed change is:
> "There are still request,responses, headers and all those typical elements
> from HTTP"
>
> The reasoning behind this starts while trying to translate the sentence to
> Spanish, where it becomes too aparent as chatty, or tasteless, and from my
> standpoint it may also sound too coloquial in english too (although I'm no
> native speaker so that's up to you guys to judge).
>
> I'm attaching the diff file which includes the whole paragrah because it
> has also been adapted for word wrapping.
>
> If I'm being too picky or proposing this incorrectly, please do not
> hesitate to let me know.
>
>
> --
> *Daniel Ferradal*
> IT Specialist
>
> email daniel at ezra-s.net
> linkedin es.linkedin.com/in/danielferradal
>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>

Re: httpd-trunk/docs/manual/howto/http2.xml.es

[Luis Gil de Bernabé]

Thanks :)
I will review it
Have a nice End of Year!

Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 29 December 2016 at 10:44, Daniel  wrote:

> Hello,
>
> I translated trunk's http2.xml from httpd-trunk/docs/manual/howto/ to
> Spanish.
>
> Find the translation attached to this email.
>
> --
> *Daniel Ferradal*
> IT Specialist
>
> email daniel at ezra-s.net
> linkedin es.linkedin.com/in/danielferradal
>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>

Re: httpd-trunk/docs/manual/howto/http2.xml.es

[Luis Gil de Bernabé]

im on it no problem ;)

Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
Twitter : https://twitter.com/luigy_tspg

On 30 December 2016 at 14:28, Daniel <dan...@ezra-s.net> wrote:

>
> Please don't forget there is also directive-dict.xml.es for review, which
> I sent a few days ago too hehe . Thanks for your patience! ;)
>
> And happy new year you too!
>
> 2016-12-30 14:26 GMT+01:00 Luis Gil de Bernabé <
> ljgbpfeif...@googlemail.com>:
>
>> Thanks :)
>> I will review it
>> Have a nice End of Year!
>>
>> Linkedin:   https://linkd.in/Ljjt8L <http://linkd.in/Ljjt8L>
>> Twitter : https://twitter.com/luigy_tspg
>>
>> On 29 December 2016 at 10:44, Daniel <dan...@ezra-s.net> wrote:
>>
>>> Hello,
>>>
>>> I translated trunk's http2.xml from httpd-trunk/docs/manual/howto/ to
>>> Spanish.
>>>
>>> Find the translation attached to this email.
>>>
>>> --
>>> *Daniel Ferradal*
>>> IT Specialist
>>>
>>> email daniel at ezra-s.net
>>> linkedin es.linkedin.com/in/danielferradal
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>>
>>
>>
>
>
> --
> *Daniel Ferradal*
> IT Specialist
>
> email daniel at ezra-s.net
> linkedin es.linkedin.com/in/danielferradal
>

Re: ASF 18th anniversary

[Luis Gil de Bernabé]

For me its coool ☺ and happy Anniversary to all @docs

El 28 mar. 2017 15:56, "Daniel"  escribió:

> sounds like a pretty nice idea.
>
> 2017-03-28 14:52 GMT+02:00 Rich Bowen :
>
>> I intend to add the 18th anniversary logo/link to the sidebar of the
>> docs for the coming few months, unless someone strongly objects. You've
>> been warned.
>>
>> --
>> Rich Bowen - rbo...@rcbowen.com - @rbowen
>> http://apachecon.com/ - @apachecon
>>
>>
>
>
> --
> *Daniel Ferradal*
> IT Specialist
>
> email dferradal at gmail.com
> linkedin es.linkedin.com/in/danielferradal
>

Re: Spanish translation: httpd-trunk/docs/manual/misc/password_encryptions.xml.es

[Luis Gil de Bernabé]

Hello:
As soon as i got a minute i will review it.
Nice work in deed :)

Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 16 March 2017 at 12:04, Daniel  wrote:

> Hello,
>
> Find attached the translation password_encryptions.xml to spanish:
> httpd-trunk/docs/manual/misc/password_encryptions.xml.es
>
>
> --
> *Daniel Ferradal*
> IT Specialist
>
> email dferradal at gmail.com
> linkedin es.linkedin.com/in/danielferradal
>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>

Re: The final result for the discussion about Chinese translations of the error documents

[Luis Gil de Bernabé]

Hello,
would be nice you send us the xml file you have updated too, so we can adsd
it to the repo
correct me if im wrong @httpd people.

Regards.

Luis.


On Sun, 1 Jul 2018 at 11:09, popcorner  wrote:

> Codeingboy and I discussed about the Chinese translation I sent yesterday,
> and did some changes.
> You can see the discussion here https://github.com/popcorner/chect/pull/1
> if you like.
>
> This version is the one that we both agree.
> The new patch file(including the previous modification) is attached in
> this email.
> Thanks for Codeingboy's help.
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org

Re: The final result for the discussion about Chinese translations of the error documents

[Luis Gil de Bernabé]

Than you William,
and Thank you for the chinise translator for the contribution, looking
fordward to seeing other manual page translations from you!

On Sat, 7 Jul 2018 at 00:08 William A Rowe Jr  wrote:

> Patch applied clean (modulo CR's), I've updated httpd/branches/2.4.x for
> this
> next 2.4.34 release based on this update. Again, thanks to you both for the
> efforts, looking forward to seeing other manual page translations from you!
>
>
>
>
>
> On Wed, Jul 4, 2018 at 5:24 AM, popcorner  wrote:
>
>> I just found that the variable CONTENT_LANGUAGE is missing in the
>> translation when I tried to use these translation files in a real httpd
>> server.
>> I added them in the translation files and it seems that these files work
>> well.
>> Please consider using this version.
>> The patch.txt and a zip package for all the modified files are attached
>> in this email.
>>
>> > On Wed, Jul 4, 2018 at 5:04 AM Luis Gil de Bernabé
>>  wrote:
>> > Hello,
>> > would be nice you send us the xml file you have updated too, so we can
>> adsd it to the repo
>> > correct me if im wrong @httpd people.
>> >
>> > Regards.
>> >
>> > Luis.
>> >
>> > >
>> > > On Sun, 1 Jul 2018 at 11:09, popcorner  wrote:
>> > > Codeingboy and I discussed about the Chinese translation I sent
>> yesterday, and did some changes.
>> > > You can see the discussion here
>> https://github.com/popcorner/chect/pull/1 if you like.
>> > >
>> > > This version is the one that we both agree.
>> > > The new patch file(including the previous modification) is attached
>> in this email.
>> > > Thanks for Codeingboy's help.
>>
>>
>> -
>> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: docs-h...@httpd.apache.org
>>
>
> --

Luis J. Gil de Bernabé Pfeiffer.

Re: Change in style/lang/es.xml (Spanish docs)

[Luis Gil de Bernabé]

Thank you for this point, i will take that into account at translation time

Regards

Linkedin:   https://linkd.in/Ljjt8L 
Twitter : https://twitter.com/luigy_tspg

On 15 January 2018 at 17:29, Daniel Ferradal  wrote:

> Hello,
>
> For what I've noticed. All rendered Spanish docs list directives like:
> "AcceptFilter Directiva"
>
> This is incorrect, in Spanish the correct form is:
> "Directive AcceptFilter"
>
> reviewing es.xml it even refers to fr.xml as having this set, so
> French docs already use this. I decided to change the Spanish ones too
> hoping this does not need too much agreement.
>
> The change is this one:
> svn commit: r1821179
>
> URL: http://svn.apache.org/viewvc?rev=1821179=rev
> Log:
> Fixed word 'Directive' placement in the directives list. In Spanish we
> must sort them the same as in French. Correct format is: 'Directiva
> ', not the opposite
>
> Modified:
> httpd/httpd/trunk/docs/manual/style/lang/es.xml
>
> What will this do? Basically every new translation built will show
> Directive lists with the correct wording in Spanish, while all
> versions until now remain the same.
>
> It's not such a big deal, and I hope there aren't any other
> implications I am not aware of.
>
> If I made a mistake, please do tell me and roll-back if necessary.
>
> --
> Daniel Ferradal
> HTTPD Docs. I translate to Spanish.
> #httpd help at Freenode
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
>

Re: [VOTE] Update our documentation building tool chain

[Luis Gil de Bernabé]

I have updated long ago the files from es, but i wasn't sure to commit
them as the FR file Lucien is saying.
So now i'm sure it could be done, i will add them to trunk (es modification
only)

@Christophe JAILLET   im not helpfull here,
but i vote +1 to update our build tool :)
rgd

On Mon, 1 Oct 2018 at 22:20, Christophe JAILLET <
christophe.jail...@wanadoo.fr> wrote:

> Le 29/09/2018 à 15:27, Eric Covener a écrit :
> >> As per Xalan documentation, the JDK or JRE 1.3.x (2000), 1.4.x (2002),
> >> or 5.x (2004) is required.
> >> As per our doc build documentation, we need at least Java 1.2 (1998) to
> >> build the doc.
> >> Java 8 (2014) is LTS and is supported until 2025
> >> Java 9 (2017)
> >> Java 10 (2018)
> >> Java 11 (2018) is apparently LTS
> > They don't mean minimums?
> >
> > Later major JDK's (oracle, IBM) seem to all  forks of xalan as the
> > default transformer, which might explain why there are few
> > contemporary releases.
> >
> > Do we need to bring our own at all?  Sticking with JDK interfaces has
> > some benefits.
>
>
> I've investigate this.
>
> 1.6.5 Ant docs state that we need Xalan or another XSLT engine only if
> we are using a version of Java older than 1.4.
>
> I guess we can safely assume it is the case nowadays.
>
> However, just removing the Xalan stuff from the lib directory does not
> work.
> There are some warnings and errors when building.
> According to google, the warnings are more or less expected and can be
> silently ignored, but the errors break the build process.
>
> First error to trigger is (sory for the mix of English and French):
>   [xslt] : Fatal Error! Erreur lors de la vérification du type de
> l'expression 'filter-expr(funcall(current, []),
> [pred(=(step("attribute", 39), literal-expr(section)))])'. Cause: Erreur
> lors de la vérification du type de l'expression
> 'filter-expr(funcall(current, []), [pred(=(step("attribute", 39),
> literal-expr(section)))])'.
>
> This is apparently related to synopsys.sxl.
>
>
> If I comment:
> 
> in common.xsl, I then get another error:
>
>  docs/manual/build/build.xml:383: Fatal error during transformation
> using /home/tititou36/svn_httpd_trunk/docs/manual/style/manual.en.xsl:
> Erreur lors de la vérification du type de l'expression
> 'com.sun.org.apache.xalan.internal.xsltc.compiler.ForEach@329dbdbf'.
>
> This one looks related to:
>  
> in overrideindex.xsl
>
>
> The lack of useful (at least to me) diagnostic, makes it hard to find
> the root cause of this issues.
>
> Adding -v to the Ant command line doesn't help much either.
>
>
> So, if any one more used to the Xalan implementation provided in the JDK
> could have a look or at least give some pointers, it would be great.
>
> Based on my own tests, and searches, I won't be in any help with this
> approach.
> The drop-in replacement with Saxon gives much less troubles. :)
>
> CJ
>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
>

Re: [VOTE] Update our documentation building tool chain

[Luis Gil de Bernabé]

I vote up for any upgrade.


El jue., 20 feb. 2020 19:28, Tim Bannister 
escribió:

> The cloud native computing foundation (especially Kubernetes) is largely
> using Hugo and it seems to work well.
>
> Tim
>
> On 20 February 2020 18:16:11 Rich Bowen  wrote:
>
> > On 1/9/20 2:14 AM, André Malo wrote:
> >> If you'd ask me, I'd rather kill XML/XSLT entirely, as the promises
> both for
> >> Java and XML/XSLT clearly don't hold anymore. However this also requires
> >> time and effort...
> >
> > Revisiting a thread that somewhat died out ... I would also be very much
> > in favor of moving away from XML/Docbook, and towards something
> > Markdown-based.
> >
> > The current toolchain has served us very well, but given the discussion
> > in the "Building docs ..." thread, maybe the time has come to move to
> > something a little more modern?
>
>
>
>
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
>

Re: Russian translate Getting Started.

[Luis Gil de Bernabé]

On Wed, 15 Apr 2020 at 19:27, Nick Kew  wrote:

>
>
> > On 15 Apr 2020, at 17:12, Rich Bowen  wrote:
> >
> > Typically what we ask is that you find another native speaker to +1 your
> translation. Note that they do *not* need to be someone who is technically
> proficient at Apache httpd - merely that they are proficient in the source
> and target languages.
> >
> > I'll be glad to commit your changes after that.
>
> Ideally it should not be for Aleksey to find someone.  After all, if he
> just
> asks someone he knows, they may be keen to tick boxes but have no
> interest in real review.  Speaking English won't help much with
> understanding our docs for someone non-techie.
>
> It should be for the Apache community right here to find eyes to review
> this contribution.  Failing that, maybe we could use this as-is but with an
> added warning note about inadequate review and an invitation for readers
> to come here with feedback.
>


+1 with the feedback message on the main documentation for the russian!
much for joining the effort Aleksey !

BR

Luis





>
> > That's so much for joining the effort!
>
> Did you mean "Thanks" there?  If so, +1 to that.  Спасибо Алексей.
>
>
> --
> Nick Kew
> -
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
>

Re: [FAQ] ASF advisory regarding http headers verbosity contradicts with one from owasp.org

[Luis Gil de Bernabé]

hello,

This is like arguing if VIM or emacs should be used. (jokes aside) I mean,
some companies will accept that as a vulnerability and will make the effort
to fix it and comply with security standards like OWASP as you mention
@Piotr. But not all time is as great as that.
If you search on any bug bounty program they exclude
meaningless vulnerabilities like cookies with no secure or http options, or
this header that you are mentioning will be no relevant.

But I do agree with you that this simple thing of removing the version or
tampering will "*improve*" your security posture or fool the bad guys, but
as Ruedinger says, if they want to hack you they will end up hacking
you, and possibly not because of a server header but for a human error, you
know.

Although you can have the header version, that's ok, but normally it's
behind something, a WAF, a fancy firewall or whatever.
The question here you have to ask yourself is, does the server have any
critical data?, does the server may disrupt the normal functionality of the
application? (i know this is too much for a simple header but sometimes it
might help securing it). But sometimes it can lead you to the fix.

And maybe you know about the netcraft server survey vendors:(
https://news.netcraft.com/archives/2021/08/25/august-2021-web-server-survey.html
)
[image: image.png]
similar to the data you posted ;) maybe you would like to have a look at
it.

In conclusion, *it depends on the security posture your company* would want
to have, whether they will remove it or not. ( i will do the same, remove
it or tamper it)
On the developers and sysadmin perspective will be just another header ;)

Hope it helps too,
Kind regards,

Luis



On Tue, 21 Sept 2021 at 15:45, Ruediger Pluem  wrote:

>
>
> On 9/21/21 2:40 PM, Piotr Sionkowski wrote:
> > Hi Guys,
> >
> >
> >
> > First of all I would like to thank you for picking up the issue I
> brought.
> >
> >
> >
> > I conducted a quick experiment and checked how apache.org headers look
> like and got:
> >
> >
> >
> > $ curl -I apache.org | grep Server
> >
> > Server: Apache
> >
> >
> >
> > I did also a deeper dive and checked a bigger sample of n=86 webpages of
> ASF sponsors.
> >
> >
> >
> > ===BEGIN OF EXPERIMENT===
> >
> > STEP 1: we grab the list of ASF sponsors
> >
> >
> >
> > $ curl --url https://www.apache.org/foundation/thanks.html -v | grep
> sponsored | cut -f 2 -d\" > sponsors
> >
> >
> >
> > result:
> >
> > https://aws.amazon.com/
> >
> > http://facebook.com/
> >
> > http://google.com/
> >
> > < Removed 80 lines >
> >
> > https://www.sonic.com/
> >
> > http://www.surfnet.nl/
> >
> > https://www.virtru.com/
> >
> >
> >
> > STEP 2: we grab Server headers for results from STEP 1. Any missing are
> replaced with 'SERVER OBSCURED'
> >
> >
> >
> > $ for subject in $(cat sponsors); do echo -n "${subject}: " >> servers;
> curl --connect-timeout 3 -I -k $subject 2> /dev/null |
> > grep Server >> servers || echo 'SERVER OBSCURED' >> servers; done
> >
> >
> >
> > result:
> >
> > https://aws.amazon.com/: Server: Server
> >
> > http://facebook.com/: SERVER OBSCURED
> >
> > http://google.com/: Server: gws
> >
> > < Removed 80 lines >
> >
> > https://www.sonic.com/: Server: nginx/1.12.1
> >
> > http://www.surfnet.nl/: Server: nginx
> >
> > https://www.virtru.com/: Server: cloudflare
> >
> >
> >
> > STEP 3: We organize the data and print histogram-like summary
> >
> >
> >
> > $ cut -f 3 -d' ' servers | sort |uniq -c > histogram
> >
> >
> >
> > result:
> >
> >2 ATS
> >
> >3 AkamaiGHost
> >
> >2 AmazonS3
> >
> >7 Apache
> >
> >1 Apache/2.4.18
> >
> >1 Apache/2.4.48
> >
> >9 Cisco
> >
> >2 GitHub.com
> >
> >2 Kestrel
> >
> >1 LiteSpeed
> >
> >   13 OBSCURED
> >
> >1 PAAS-WEB
> >
> >1 SE-1.15.12
> >
> >2 Server
> >
> >1 Tengine
> >
> >1 Varnish
> >
> >1 awselb/2.0
> >
> >1 bfe/1.0.8.18
> >
> >   15 cloudflare
> >
> >1 globaledge-envoy
> >
> >2 gws
> >
> >1 ias/1.4.2.3_1.17.3
> >
> >   14 nginx
> >
> >1 nginx/1.12.1
> >
> >1 nginx/1.14.0
> >
> > ===END OF EXPERIMENT===
> >
> >
> >
> > Observations from data:
> >
> > Observation 1: 15 out of 86 (17.5%) are not willing to share ANYTHING
> about their servers
> >
> > Observation 2: another 15 are hidden behind cloudflare, summing up to 35%
> >
> > Observation 3: 8/86 (9%) show any version numbers
> >
> > Observation 4: out of 9 servers who claim to be Apache 2 (22%) show
> varsions
> >
> >
> >
> > Conclusions:
> >
> > Only a tiny percentage of this sample is willing to show any version of
> their web server (not confirmed if what they show is what
> > they actually run).
> >
> >
> >
> > In view of above, would ASF consider changing its reccommendation[1]
> from 'Minimal' to 'Product Only'?
>
> Thanks for the data, but in my opinion it actually tells you not much.
> From my experience in a lot of big companies people are
> forced to stick to the owasp recommendations whether they make sense in
>