Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1886C200BD0 for ; Wed, 30 Nov 2016 13:00:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 17043160B08; Wed, 30 Nov 2016 12:00:01 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E12E6160B19 for ; Wed, 30 Nov 2016 12:59:59 +0100 (CET) Received: (qmail 82319 invoked by uid 500); 30 Nov 2016 11:59:58 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: docs@httpd.apache.org List-Id: Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 82287 invoked by uid 99); 30 Nov 2016 11:59:58 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Nov 2016 11:59:58 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 471DC1A954D for ; Wed, 30 Nov 2016 11:59:58 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.998 X-Spam-Level: X-Spam-Status: No, score=-0.998 tagged_above=-999 required=6.31 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-2.999, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id VuYkJR0c0rGm for ; Wed, 30 Nov 2016 11:59:55 +0000 (UTC) Received: from smtp.r4l.com (smtp.r4l.com [192.99.3.191]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 722D05F4A8 for ; Wed, 30 Nov 2016 11:59:55 +0000 (UTC) Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) by r4lsrv.r4l.com (Postfix) with ESMTPSA id 47EF31EC018B for ; Wed, 30 Nov 2016 06:59:46 -0500 (EST) Received: by mail-wm0-f45.google.com with SMTP id a197so266705565wmd.0 for ; Wed, 30 Nov 2016 03:59:46 -0800 (PST) X-Gm-Message-State: AKaTC02CN4VjGxG9t4s5/EQDy9MwXC15UxamiyJ5HWfhU4VRM97JtYds2rvTMJKVGaiBs6nenaU0KkVGaOxGjQ== X-Received: by 10.28.193.199 with SMTP id r190mr27250484wmf.58.1480507185057; Wed, 30 Nov 2016 03:59:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.149.229 with HTTP; Wed, 30 Nov 2016 03:59:24 -0800 (PST) In-Reply-To: <9ce6afa0f9c746afab55842831843415@DC03PXMBP003.jacksonnational.com> References: <9ce6afa0f9c746afab55842831843415@DC03PXMBP003.jacksonnational.com> From: Daniel Date: Wed, 30 Nov 2016 12:59:24 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: small patch for httpd-trunk/docs/manual/howto/http2.xml To: docs@httpd.apache.org Content-Type: multipart/alternative; boundary=94eb2c12fbbada5ad1054283709d archived-at: Wed, 30 Nov 2016 12:00:01 -0000 --94eb2c12fbbada5ad1054283709d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello guys, Thanks for the awesome feedback! I certainly like your suggestions better than mine. About the punctuation errors, in Spanish, If what I learned hasn't changed, we don't add commas before we use "and" when "and" is used to name the last element of a list. So in English it is different? I didn't know about that, thanks!, and maybe that's why I added "headers and" instead of "headers, and" in my sentence. If I had to choose, I'd use your suggestion: "Requests, responses, headers, and other typical elements still exist from the HTTP specification." Specifying HTTP/1.x or not maybe not that important since the context implies it refers to previous spec, but it is good to use it too nonetheless. About "typical", I think the idea is to refer to those "familiar" elements we all know about HTTP, that still remain in HTTP/2, so maybe we can change to that word "familiar"? Does it sound good like this then?: "Requests, responses, headers, and other familiar elements still exist from the HTTP/1.x specification." Anyways, rather than stress ourselves with one single sentence I think the point mainly is if we should modify sentences that, although perfectly valid, may sound too informal in the documentation, I noticed some more examples along the same document that could take a bit of improvement in formality, or at least translating some parts faithfully to spanish would sound way too informal. When I finish translating the whole thing to Spanish I may ask for all other suggestions to formality in one shot if you guys agree. Thank you very much. 2016-11-29 23:05 GMT+01:00 Houser, Rick : > Native Mid-West U.S. Speaker here=E2=80=A6 > > > > Your change is a significant improvement, but the language still seems a > bit off. Specifically, =E2=80=9Cand all those=E2=80=9D and =E2=80=9Cand = all that=E2=80=9D stand out. Try > one of these, but note that I did not have full context of the sentence: > > > > "There are still requests, responses, headers, and other typical elements > from HTTP." > > "Requests, responses, headers, and other typical elements still exist fro= m > the HTTP specification." > > "Requests, responses, headers, and other typical elements remain from > HTTP." > > > > > > Should it also reference HTTP/1.x directly rather than just the generic > HTTP? > > > > Is =E2=80=9Ctypical=E2=80=9D actually important? In my examples above, t= hat word can > probably be removed for the better. > > > > Also the plurality of the sentence should match; note how I changed > request to requests above. > > > > With lists, the comma placement after the and seems to vary significantly > with region. Here, we typically terminate the term immediately before > =E2=80=9Cand=E2=80=9D with a comma, but not all areas do so. Either is c= orrect, as long as > it=E2=80=99s consistent. > > > > > > Rick Houser > > Web Administration > > > > *From:* Luis Gil de Bernab=C3=A9 [mailto:ljgbpfeiffer@googlemail.com] > *Sent:* Tuesday, November 29, 2016 16:11 > *To:* docs@httpd.apache.org > *Subject:* Re: small patch for httpd-trunk/docs/manual/howto/http2.xml > > > > Nice, > > sounds better, but here an English spoken commiter might better check thi= s > 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 element= s > from HTTP" > > > > The reasoning behind this starts while trying to translate the sentence t= o > Spanish, where it becomes too aparent as chatty, or tasteless, and from m= y > standpoint it may also sound too coloquial in english too (although I'm n= o > 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-unsubscribe@httpd.apache.org > For additional commands, e-mail: docs-help@httpd.apache.org > > > --=20 *Daniel Ferradal* IT Specialist email daniel at ezra-s.net linkedin es.linkedin.com/in/danielferradal --94eb2c12fbbada5ad1054283709d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello guys,

Thanks for the awesome feed= back!

I certainly like your suggestions better tha= n mine.

About the punctuation errors, in Spanish, = If what I learned hasn't changed, we don't add commas before we use= "and" when "and" is used to name the last element of a= list. So in English it is different? I didn't know about that, thanks!= , and maybe that's why I added "headers and" instead of "= ;headers, and" in my sentence.

If I had to ch= oose, I'd use your suggestion:
"Requests, responses, hea= ders, and other typical elements still exist from the HTTP specification.&q= uot;

Specifying HTTP/1.x or not maybe not that imp= ortant since the context implies it refers to previous spec, but it is good= to use it too nonetheless.

About "typical&qu= ot;, I think the idea is to refer to those "familiar" elements we= all know about HTTP, that still remain in HTTP/2, so maybe we can change t= o that word "familiar"? Does it sound good like this then?:
=

"Requests, responses, headers, and other familiar = elements still exist from the HTTP/1.x specification."=C2=A0
=


Anyways, rather than stress ourselves wi= th one single sentence I think the point mainly is if we should modify sent= ences that, although perfectly valid, may sound too informal in the documen= tation, I noticed some more examples along the same document that could tak= e a bit of improvement in formality, or at least translating some parts fai= thfully to spanish would sound way too informal. When I finish translating = the whole thing to Spanish I may ask for all other suggestions to formality= in one shot if you guys agree.

Thank you very= much.


2016-11-29 23:05 GMT+01:00 Houser, Rick <rick.houser@jackson.c= om>:

Native Mid-West= U.S. Speaker here=E2=80=A6

=C2=A0

Your change is a significant improvement, but the language = still seems a bit off.=C2=A0 Specifically, =E2=80=9Cand all those=E2=80=9D = and =E2=80=9Cand all that=E2=80=9D stand out.=C2=A0 Try one of these, but note that I did not have full conte= xt of the sentence:

=C2=A0

"There are still requests, responses, hea= ders, and other typical elements from HTTP."

"Requests, responses, headers, and other = typical elements still exist from the HTTP specification."

"Requests, responses, headers, and other = typical elements remain from HTTP."

=C2=A0

=C2=A0

Should it also reference HTTP/1.x directly rather than just= the generic HTTP?

=C2=A0

Is =E2=80=9Ctypical=E2=80=9D actually important?=C2=A0 In m= y examples above, that word can probably be removed for the better.<= u>

=C2=A0

Also the plurality of the sentence should match; note how I= changed request to requests above.

=C2=A0

With lists, the comma placement after the and seems to vary= significantly with region.=C2=A0 Here, we typically terminate the term imm= ediately before =E2=80=9Cand=E2=80=9D with a comma, but not all areas do so.=C2=A0 = Either is correct, as long as it=E2=80=99s consistent.=

=C2=A0

=C2=A0

Rick Houser

Web Administration

=C2=A0

From: Luis Gil de Bernab=C3=A9 [mailto:ljgbpfeiffer@googlemail.com]
Sent: Tuesday, November 29, 2016 16:11
To: docs@= httpd.apache.org
Subject: Re: small patch for httpd-trunk/docs/manual/howto/http= 2.xml

=C2=A0

Nice,=C2=A0

sounds better, but here an English spoken commiter might = better check this out :)=C2=A0

Regards.

=C2=A0


Linkedin:=C2=A0 =C2=A0https://linkd.in/Ljjt8L

Twitter : =C2=A0 =C2=A0=C2=A0https://twitter.com/luigy_tspg

=C2=A0

On 29 November 2016 at 17:37, Daniel <daniel@ezra-s.net> wrote= :

Hello,

=C2=A0

I'd like to submit a little patch for a sentence= in:

httpd-trunk/docs/manual/howto/http2.xml<= u>

=C2=A0

The original sentence I'm changing is:=

"There are still request and responses and head= ers and all that"

and the proposed change is:
"There are still request,responses, headers and all those typical elem= ents from HTTP"

=C2=A0

The reasoning behind this starts while trying to tra= nslate the sentence to Spanish, where it becomes too aparent as chatty, or = tasteless, and from my standpoint it may also sound too coloquial in englis= h too (although I'm no native speaker so that's up to you guys to judge).

=C2=A0

I'm attaching the diff file which includes the w= hole paragrah because it has also been adapted for word wrapping.=

=C2=A0

If I'm being too picky or proposing this incorre= ctly, please do not hesitate to let me know.


=C2=A0=

-- =

Daniel Ferradal

IT Specialist

=C2=A0

email = =C2=A0 =C2=A0 =C2=A0 =C2=A0 daniel at ezra-s.net

linkedin =C2=A0 =C2=A0=C2=A0es.linkedin.com/in/danielferradal



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

=C2=A0




--
Daniel FerradalIT Specialist

<= /div>
email =C2=A0 =C2=A0 =C2=A0 =C2=A0 daniel at e= zra-s.net
linkedin =C2=A0 =C2=A0=C2=A0es.linke= din.com/in/danielferradal
--94eb2c12fbbada5ad1054283709d--