Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: docs@httpd.apache.org
To: docs@httpd.apache.org
From: Rich Bowen <rbowen@rcbowen.com>
Subject: Translations (IRC conversation)
Message-ID: <8b7e6fa1-4042-603b-78e4-54e7a727ce4c@rcbowen.com>
Date: Wed, 19 Oct 2016 09:24:25 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.3.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="mQDH2GjKeuaB0P0GCb7F1sWAAHPtjIcCR"
archived-at: Wed, 19 Oct 2016 13:24:42 -0000

--mQDH2GjKeuaB0P0GCb7F1sWAAHPtjIcCR
Content-Type: multipart/mixed; boundary="jjuO28Gdi5W2MwqlVcxK3QNn2hhhmgoPs";
 protected-headers="v1"
From: Rich Bowen <rbowen@rcbowen.com>
To: docs@httpd.apache.org
Message-ID: <8b7e6fa1-4042-603b-78e4-54e7a727ce4c@rcbowen.com>
Subject: Translations (IRC conversation)

--jjuO28Gdi5W2MwqlVcxK3QNn2hhhmgoPs
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

(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. Discussio=
n?

* 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. :-)


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


--jjuO28Gdi5W2MwqlVcxK3QNn2hhhmgoPs--

--mQDH2GjKeuaB0P0GCb7F1sWAAHPtjIcCR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJYB3QJAAoJEHhwUUeLEqujohoP/0I8XlugOfTOglNX4NekEpRm
miS734B/tKL34lCQ/1Pb8NtLzjwDDn5zjIyYas+f4vrd2T4iwMVyQ5HDOod1zlUa
X2vm/6/zByZ24OClezchQ8NHgjn4JSxKezp9GLHs1YJA+N1L5d25x6lLXo21W+j7
0KU2zsAfZuQRhxL7rxeBKNxfuSI2iAPISx458H5dl2bQlJuaE3b+fU8nQwyzFSDc
qRGJJ5Vo2ti9FcdFJHQBzzmhDSVTwH+yHGo8YoBZHr7JhEwtO0tAa6IuC+Zz8f+q
uqstb5XU1PoXnsXzCZIGv7gTqBgxLWWiZw1XlnoiUy1XaF5O1NIWAP42Z/+0s5L6
rMp+FPUnlZcj3/4dDUpOG5ibsKAqXu3bo6AvE0HTkW1EABSBQ8oWA+lIm8zGthOY
n81egBvKfjo7l0W3H5IAA1CR+jUrieZBX1wgwgqT2dV+8Nh7wK6sveX4XkopPiPH
b/e+lk7vdWKRTr72RqowfbmZGtWBYK7a8d1nSLCkwoZoa59h14z1Cb47MZFcFr6i
CBiMoxbMtNGAV0zc6EwA1OeRe4AWIj98ydskyxi0WiUDWZsCVZS4WDNXwvoNJCJv
3W6KO38TWLlsg5xGKnD6AsFuwVorfa3jZgww2R8uCTQ37u0d1TM14fM15FlW5zYM
W9niq5rNWViAMIhykkfO
=1nln
-----END PGP SIGNATURE-----

--mQDH2GjKeuaB0P0GCb7F1sWAAHPtjIcCR--