Re: Need help configuring Apache 2.4 on Windows 10 with PHP

2019-01-27 Thread Ulises Gonzalez Horta

On 2019-01-27 14:15, Barry Kimelman wrote:

Hello,

Thanks for the reply. I have looked at the URL you specified and the
information shown there is not specific enough. It shows config info, 
but

it does not say where to put it and it doe snot adequately explain it.

On Sun, Jan 27, 2019 at 1:06 PM Ulises Gonzalez Horta 


wrote:



Related to where to put it you can put the config in the httpd.conf file 
or in a separated file and in your httpd.conf file you use include $ 
file  to include that file. I haven't work with apache in windows so I 
don't know if you have httpd.conf file or apache2.conf file with your 
main config.

--
Salu2, Ulinx
"En un problema con n ecuaciones
siempre habrá al menos n+1 incógnitas"
Linux user 366775

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



Re: Need help configuring Apache 2.4 on Windows 10 with PHP

2019-01-27 Thread Ulises Gonzalez Horta

On 2019-01-27 13:52, Barry Kimelman wrote:

Hello,

I am running Apache 2.4 on a 64 bit windows 10 system.

For a while I have been running Perl CGI scripts with no problems. Now 
I

want to run PHP CGI scripts.

The last few linbes of my conf/httpd.conf file looks like the following


Include conf/extra/proxy-html.conf


# Secure (SSL/TLS) connections
##
# Note: The following must must be present to support
#   starting without SSL on platforms with no /dev/random 
equivalent

#   but a statically compiled-in mod_ssl.
#

SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
Include conf/extra/httpd-ssl.conf


# PHP FastCGI
#
# Edit conf/extra/httpd-fcgid.conf to match your php configuration
# and uncomment the Include line below.
#
#Include conf/extra/httpd-fcgid.conf

However the file named in the comment on the last line does not exist 
and I
have not been able to find a "sample" of the named file. What do I need 
to
do for the named file in order to be able to run CGI scripts written in 
PHP

?

Thanks.

==

Barry Kimelman
Atlanta, GA, USA


Hi did you check https://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html 
?? Is the php example there good for you??


--
Salu2, Ulinx
"En un problema con n ecuaciones
siempre habrá al menos n+1 incógnitas"
Linux user 366775

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



Re: Translations update

2018-11-28 Thread Ulises Gonzalez Horta

On 2018-11-28 11:04, gustavo.avitab...@unina.it wrote:

Quoting Christopher Schultz :


André,

On 11/26/18 08:35, André Warnier (tomcat) wrote:

On 26.11.2018 13:29, Rémy Maucherat wrote:

On Sat, Nov 24, 2018 at 9:48 AM Ludovic Pénet 
wrote:


Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat a
écrit :

On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas
 wrote:


- French has increased from 18% to 64% coverage



Done (well, close enough, a few tribes/ha remain) !

A single translation remains to be performed.

Jump to https://poeditor.com/join/project/NUTIjDWzrl and be the
one to complete the French translation. ;-)



Ok, you could have finished it, I was busy.

Now we can try to harmonize terms, fixes are then easy to do with
the search feature

Common ones we have right now: - "socket" (usually untranslated
or cleverly omitted): ? - "endpoint" (for websockets, and for the
Tomcat connectors, so possibly two different terms): "point
d'entrée" ?


That sounds like exactly the opposite of "endpoint" to me. Although
I must say that even in English, the vocabulary used in some
reference documents (in particular everything to do with XML-based
protocols, such as SOAP, SAML, OASIS and the like) is sometimes
mysterious and counter-intuitive. What about "cible" here ? Or more
literally, "point final" ?


I disagree.

An "endpoint" is a thing to which clients connect... an "entry point",
as Rémy suggests.


For "socket", "soquet" (like the piece in which you insert a plug,
or a lightbulb) sounds ok to me.


This sounds okay to me, thought I don't know French at all. :)


- "thread" (often it is untranslated elsewhere): "fil
d'exécution" ? - "membership" (that's the clustering object):
"gestionnaire de membres" ?


"Membership" refers to "le fait d'être membre", no ? "adhésion" ?
(like "cluster members" -> "adhérents au cluster" (with the
appropriate French pronounciation for "cleustère") :-)


What would you call a list of people who belong to a certain fancy
club or society? That's the word that should be used, here.


- "dispatch"/"dispatcher" (for the Servlet request dispatcher):
?



dépêcher / dépêcheur ?


And I just saw it is really "connexion" and not "connection".
Oooops, I thought both were ok. I guess it's the same kind of
mistake with English-UK vs English-US, where I usually hate the
UK style (except in HarryP and Discworld, it's part of the charm
I suppose).



Maybe a note : the target audience of most of these messages is not
the members of the Académie or the jury of the Prix Goncourt. Its
is programmers, sysadmins and qualified tomcat/webservers users.
The translations should be helpful to them, to get a first idea of
the issue and be able to search later in the on-line documentation.
Which happens to be only available/up-to-date/searchable in
English, no ?

So I believe that a translation such as "La requête PTHT recue sur
le soquet du connecteur de toile a été dépêchée au conducteur du
groupe d'adhérents" may be stylistically correct, but ultimately
quite counter-productive.

(Sorry for the missing c cédille, can't type it here) (PTHT =
Protocol de Transport Hyper-Texte)


HTTP should always be spelled HTTP and never PTHT, just like UTC is
always spelled UTC, even in English (where the acronym makes no sense
to Englist speakers).

I think maybe you were kidding, but ... just in case :)

- -chris
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


I am Italian, not French, but the issues discussed here are relevant
for Italian too.

I suggest, as a general criterion, that terms that should be known
to a typical reader (like socket, thread, ...) be left untranslated;
otherwise, the reader will face the additional problem of identifying
what the translated term really means.
   Gustavo




I'm not Italian neither French but Spanish, and I agree with you guys. 
I'm trying to follow that philosophy on my translations

Certainly there are some words that cannot/should not be translated

--
Salu2, Ulinx
"En un problema con n ecuaciones
siempre habrá al menos n+1 incógnitas"
Linux user 366775

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